6. DATA SOURCES › 6.1 Data Sources Overview › 6.1.4 CA NetSpy
6.1.4 CA NetSpy
CA NetSpy is a VTAM (Virtual Telecommunications Access
Method) application that monitors host and network
performance. The CA MICS Network Analyzer Option supports
the z/OS and VM versions of CA NetSpy.
The CA MICS Network Analyzer Option supports the following CA
NetSpy data:
+-----------------------------------------------------------+
| | Offsets |
| | 12 71 72 73 |
| Data Type | ----------- |
| Resource Name | Values: |
|=================================|=========================|
| NCP | |
| NCP Resource | 80 __ 80 02 |
| Line, Controller, Terminal | |
| Remote BSC Link | 40 __ __ 01 |
| Remote BSC Cluster | 20 __ __ 01 |
| Remote BSC Terminal | 10 __ __ 01 |
| Local Cluster | 28 __ __ 01 |
| Local Cluster | 88 __ __ 01 |
| Local SNA | 89 __ __ 01 |
| Local SNA | 29 __ __ 01 |
| Local ? | 18 __ __ 01 |
| Local SNA LU | 19 __ __ 01 |
| NPA Pseudo Link | 43 __ __ 01 |
| NPA Pseudo Dev | 03 __ __ 01 |
| Remote SDLC Link | 41 __ __ 01 |
| Remote SDLC Physical Unit | 21 __ __ 01 |
| Remote SDLC Logical Unit | 11 __ __ 01 |
| Switched SDLC Link | 85 __ __ 01 |
| Switched SDLC Physical Unit | 25 __ __ 01 |
| Switched SDLC Logical Unit | 15 __ __ 01 |
| X.25 Link | 47 __ __ 01 |
| X.25 Physical Unit | 27 __ __ 01 |
| X.25 Logical Unit | 17 __ __ 01 |
| CLA - Link | 49 __ 40 01 |
| CLA - Physical Unit | 29 __ 40 01 |
| NPSI | |
| X.25 Machine Link | 49 04 80 04 |
| X.25 Machine Physical Unit | 29 04 40 04 |
| X.25 Virtual Connection | 29 04 20 04 |
+-----------------------------------------------------------+
continued
continued from prior column
+-----------------------------------------------------------+
| | Offsets |
| | 12 71 72 73 |
| Data Type | ----------- |
| Resource Name | Values: |
|=================================|=========================|
| NTRI | |
| Logical Link | 70 08 80 03 |
| Physical Link | 71 08 40 03 |
| TIC3 (ODLC) | |
| Physical Link | 49 00 40 07 |
| Physical Unit | 29 00 08 07 |
| Frame Relay | |
| Physical Link | 49 02 80 05 |
| Logical Link | 49 02 40 05 |
| Physical Unit | 29 02 20 05 |
| LMI Station | 29 02 10 05 |
| Type A Record (Application) | not applicable |
| Type B Record (VTAM Buffers) | not applicable |
| Type C Record (Accounting) | not applicable |
| Type I Record (TCP Connection) | not applicable |
| Type J Record (TCP/IP Stack) | not applicable |
| Type S Record (Terminal Session)| not applicable |
| Types T and U (Terminal) | not applicable |
| Type X Records | 88 |
| General Alerts: | |
| Application Program | 00 |
| NCP | 04 |
| Line | 08 |
| Cluster | 0C |
| Logical Unit | 10 |
| Virtual Route | 14 |
+-----------------------------------------------------------+
CA NetSpy is divided into three components: the VTAM
interface, the NCP (network control program) interface, and
the TCP/IP interface. The VTAM interface collects response
time and traffic statistics for host applications and their
session partners. The NCP interface collects network
traffic, utilization statistics, and network session
accounting data from the NCP NPA Logical Unit (NCP NPALU) in
front-end processors running NCP or equivalent software. The
TCP/IP interface collects information for stacks, and all the
UDP, IF, and TCP interfaces.
CA NetSpy writes an SMF record, or the VM equivalent, that
has a user-defined SMF record number. (Refer to Section
7.2.1 for information on how to specify the SMF record number
to CA NetSpy and to the CA MICS Network Analyzer Option.)
This SMF record contains data from the CA NetSpy VTAM
interface, NCP interface, network session accounting (NSA)
collection function, network gateway accounting (NGA)
collection function, Network Token Ring Interface (NTRI) data
collection, NCP Packet Switching Interface (NPSI) data
collection, Token Interface Coupler-3 (TIC3), general alert
function, and TCP/IP interface.
For CA NetSpy running under z/OS, it is capable of writing
its NCP, VTAM, and TCP/IP interface data to SMF.
For CA NetSpy running under VM, the SMF equivalent log record
is written to the CMS files named in the LOG1 and LOG2
FILEDEF statements in the startup EXEC. In order to process
this data by CA MICS, you must transport these CMS data sets
to your CA MICS z/OS host. See Section 7.3.2 for details on
the modifications you must make to the DAY056 step of your CA
MICS DAILY update job to process VM CA NetSpy network data.
The following sections describe how to tailor CA NetSpy to
record data to SMF, synchronize interval collection, and
collect network accounting data.
Recording Data to SMF
---------------------
Your administrator specifies the CA NetSpy SMF record number
in the INITPRM member of NETSPY.CNTL. The INITPRM member
also controls which record subtypes CA NetSpy produces. These
initialization parameters take this form:
SMF=record_number SESSION=sesopt TYPEU=uopt
where:
record_number ranges from 128 to 255
sesopt is YES (record subtype S records)
or NO (do not record subtype S records)
uopt is YES (records subtype U records)
or NO (do not record subtype U records)
For TCP/IP data you must code the following:
SNMPHOST ...IF=(Y|N,Y|N),STACK=(Y|N,Y|N),TCP=(Y|N,Y|N),
UDP=(Y|N,Y|N)
The following parameters indicate what type of MIB data is
to be collected and whether or not the collected data is to
be logged. The default is to collect and log all data. The
first parameter within the parentheses is the collection
indicator. Valid values are Y for YES to collect or N for
NO not to collect. The second parameter within the
parentheses is the logging indicator. Valid values are Y
for YES log data or N for NO logging data. The logging
indicator is only valid when the collection indicator is Y.
Valid combinations of these two indicators are (Y,Y),
(Y,N), and (N,N).
IF=(Y|N, Y|N) This produces the interface table data.
Default: IF=(Y,Y), to collect and log
interface table.
STACK=(Y|N, Y|N)
This produces an overview of the stack,
which includes summary information on all
three groups.
Default: STACK=(Y,Y), to collect and log
stack data.
TCP=(Y|N, Y|N) This produces the TCP connection table data.
Default: TCP=(Y,Y), to collect and log TCP
connection table data.
UDP=(Y|N,Y|N) This produces the UDP connection table data.
Default: UDP=(Y,Y), to collect and log UDP
connection.
The TCPIPMON=YES must be coded before the first SNMPHOST
initialization parameter.
To process CA NetSpy data in CA MICS, indicate all of the SMF
record numbers you have chosen for the various CA NetSpy
monitors running on different systems. The default CA NetSpy
record for CA MICS processing is 132 (decimal). If you
choose an SMF record number other than the default, you must
update sharedprefix.MICS.GENLIB(SNTGENIN) with the numbers
you choose. Complete directions on how to perform this
update is provided in Section 7.2.1.
If you are processing data from VM NetSpy, then you are also
responsible for transporting the SMF equivalent data to your
CA MICS z/OS host. Use the NetSpy/VM HOSTID parameter to
stamp each record with an SMF system identifier, so that once
the data is sent to an z/OS host, it can be processed into CA
MICS without further modification. The host identifier must
be specified in the CA NetSpy parameters, or it will default
to the first four characters of the VTAM host name. If more
than one VM system has the same default HOSTID value, those
multiple VM systems will have the same SYSID written to the
SMF data. This could affect how the CA MICS Network Analyzer
Option processes the data, producing unexpected results such
as calculated time elements with negative values or events
that seem to be duplicates but that actually occurred on
different VM systems.
For additional information on the HOSTID parameter, see the
CA NetSpy documentation.
SMF Record Subtypes
-------------------
+-------------------------------------------------------+
| SMF Record | CA NetSpy | Data Descriptions |
| Subtypes | Release(s) | |
+=======================================================+
| S | up through 7.0 | Terminal Session |
| | | Statistics |
|-------------------------------------------------------|
| T/U | up through 7.0 | Terminal Statistics |
| | | |
|-------------------------------------------------------|
| A | up through 7.0 | Application |
| | | Statistics |
|-------------------------------------------------------|
| B | up through 7.0 | VTAM Buffer |
| | | Statistics |
|-------------------------------------------------------|
| C | up through 7.0 | Network Accounting |
| | | Statistics |
|-------------------------------------------------------|
| N | up through 7.0 | NCP Interface |
| | | Statistics |
|-------------------------------------------------------|
| X | up through 7.0 | General Alerts |
| | | Statistics |
|-------------------------------------------------------|
| V | up through 7.0 | Virtual Routes |
| | | Statistics |
+-------------------------------------------------------+
| I | up through 7.0 | TCP/IP Connection |
| | | Statistics |
|-------------------------------------------------------|
| J | up through 7.0 | TCP/IP Stack |
| | | Statistics |
+-------------------------------------------------------+
A special utility is provided with CA NetSpy that converts CA
NetSpy NCP data into CA NetSpy SMF record format, subtype N
to SMF type 38 record format, which is the format that NPM
network subsystem produces. The purpose of this utility is
to provide users who are converting from NPM to CA NetSpy
with a convenient way to produce NPM network reports from CA
NetSpy data.
Use of the above utility is not required to process CA NetSpy
NCP data into CA MICS and it is not recommended because it
requires an extra pass of the CA NetSpy NCP data.
Synchronizing Interval Collection
---------------------------------
Coordinate with your CA NetSpy administrator to synchronize
the collection of CA NetSpy interval data for two important
reasons:
o First, you may want to correlate CA NetSpy data with
information from another source, such as the CA TSO/MON PM
monitor. By synchronizing collection so that CA NetSpy and
CA TSO/MON PM records are written at about the same time,
you will be able to compare and combine information from
the two monitors for a more complete analysis.
o Second, because CA MICS records all information based on
the end timestamp of records it processes, and because
summarization for the DAYS and WEEKS timespans is by HOUR,
it is necessary to ensure that the last record of the hour
is recorded within the hour in which the activity occurred.
If the record is written at or after the hour, the
information in the record will be erroneously associated
with the subsequent hour.
To synchronize production of CA NetSpy data, use the SYNC
statement in the INITPRM member of NETSPY.CNTL. With the
SYNC parameter, you tell CA NetSpy the time after the hour at
which you want logging synchronized. For example, if you
specify a CA NetSpy recording interval (INTERVAL) of 15
minutes and a SYNC parameter of 14:00, then records will be
logged at 14, 29, 44, and 59 minutes after the hour.
You may have to experiment with this value to ensure that
data is being recorded in the correct hour, because CA NetSpy
is not always successful in writing SMF records at precisely
the time you request.
Collecting Additional CA NetSpy Data
---------------------------------
o For information on how to activate CA NetSpy NTRI (Network
Token Ring Interface), NPSI (NCP Packet Switching
Interface), Frame Relay, and TIC3 (Token Ring Interface
Coupler) data collection, refer to the CA NetSpy Network
Performance Administrator Guide.
The following sections discuss features of CA NetSpy:
1 - CA NetSpy VTAM Interface
2 - CA NetSpy NCP Interface
3 - CA NetSpy TCP/IP Interface
4 - CA NetSpy Network Session Accounting
5 - CA NetSpy Network Gateway Accounting
6 - CA NetSpy General Alerts
7 - CA NetSpy-to-CA NetSpy Communication
8 - CA NetSpy Data Considerations
Copyright © 2014 CA.
All rights reserved.
|
|