6. DATA SOURCES › 6.1 Data Sources Overview › 6.1.1 NetView Performance Monitor (NPM)
6.1.1 NetView Performance Monitor (NPM)
Tivoli NetView Performance Monitor (NPM) is an operational
performance tool used to monitor and manage day-to-day
network operations. Its data collection subsystem has the
following collector functions:
o Network Collector Function - records volume,
performance, and reliability data as collected in the
network control program (NCP).
o Session Collector Function - gathers response time and
loads data in the host computer.
o Network Session Accounting - gathers accounting data
(connect time and traffic statistics for terminal
sessions) from the NCP NPALU (Network Performance
Analysis Logical Unit).
o Network Gateway Accounting - gathers accounting data
(connect time and traffic statistics for cross-network
sessions) from the NCP NPALU (Network Performance
Analysis Logical Unit).
The CA MICS Network Analyzer Option supports the following
data, discussed in the Tivoli NetView Performance Monitor
documentation, SMF and NPM Log Records section:
+-----------------------------------------------------------+
| IBM Keyword | |
| Description | Hex Value |
|=================================|=========================|
| NETWORK | |
| NCP Interval | 10 |
| Line Interval | 11 |
| PU Interval | 12 |
| LU Interval | 13 |
| Network Monitor Exception | 18 |
| Network Monitor Resolution | 19 |
| NTRI Logical Link | 70 |
| NTRI Physical Link | 71 |
| X.25 (NPSI, XI) Link Interval | 74 |
| X.25 (NPSI, XI) PU Interval | 75 |
| NPSI VC Interval | 77 |
| Frame Relay Physical Link | 82 |
| Frame Relay Logical Link | 83 |
| Frame Relay Physical Station | 84 |
| Frame Relay (LMI) PU | 85 |
| ODLC LAN Physical Link | A0 |
| ODLC LAN Station PU | A1 |
| SESSION | |
| LU Detail | 20 |
| NSA | |
| NSA Session Start | 50 |
| NSA Session Stop | 51 |
| NSA Interval | 52 |
| NGA Session Start | 60 |
| NGA Session Stop | 61 |
| NGA Interval | 62 |
| VTAM | |
| VTAM Buffer Data | D7 |
| VTAM CSM Data | DC |
| VTAM Global Data | D6 |
+-----------------------------------------------------------+
Using NPM Data from VM Systems
------------------------------
When NPM runs on VM systems, a log record that is equivalent
to SMF type 28 data is written to the CMS files named in the
FNMLOG1 and FNMLOG2 FILEDEF statements in the NPM startup
EXEC. To process NPM VM data in the Analyzer, you must:
o Ensure that your NPM systems programmer is collecting the
data you need to process. See NPM Initialization
Statements and Commands below for more information.
o Transport the CMS files named on the FILEDEF statements to
your CA MICS z/OS host using any data transfer product you
choose.
o Modify the DAY056 step of the CA MICS DAILY operational
job following the instructions in Section 7.3.2 of this
guide.
NPM Initialization Statements and Commands
------------------------------------------
At activation, NPM reads a set of initialization statements
and, if specified, executes a set of initialization commands.
The initialization statements define data collection
intervals, what data can be collected, and to what
destinations the data can be written. The initialization
commands enable you to measure specific resources at specific
intervals and on a daily basis without the need for operator
intervention.
This section covers only those initialization statements and
commands for NPM that directly affect the data input to CA
MICS. Refer to the IBM Tivoli NetView Performance Monitor
documentation for a complete description of NPM
initialization statements and commands.
Sample NPM Initialization Statements
------------------------------------
NPM Initialization Statement: HOSTCOLL=YES indicates that
this NPM will support data collection from this host.
INTERVAL=(225,SEC): The NPM base INTERVAL is 225 seconds.
Seven additional higher intervals, each twice the value of
the previous interval, are derived from this base interval
for network data collection and exception monitoring
commands. The higher intervals that can be derived from a
base interval of 225 seconds include the following:
Interval 2 450 seconds (or 7 1/2 minutes)
3 15 minutes
4 30 minutes
5 1 hour
6 2 hour
7 4 hour
8 8 hour
Each command or panel used to start network collection allows
you to specify the NPM computed interval, as explained in the
example above, designating the frequency of data collection.
Session data collection time intervals use the SESSINT
parameter in conjunction with the NPM base INTERVAL value to
calculate the length of the session data collection interval.
The SESSINT parameter should not be confused with the
intervals computed by NPM for network data collection.
Following the example above, where 225 was the NPM base
interval in seconds, SESSINT=4 specifies that session data is
collected at 15-minute intervals. The SESSINT value of 4 is
not the same as interval 4 for network data collection. NPM
derives this 15-minute session collection interval by
multiplying the value of SESSINT (4) by the base interval
(225).
SYNCH=(3,59): NPM interval 3 (15 minutes) ends at 14, 29,
and 59 minutes after the hour. The session collection
intervals end at the same times. Synchronizing collection
intervals to terminate at least one minute before the hour
ensures that the data falls into the right hour in CA MICS.
For example, data collected for the interval beginning at
8:44 and ending at 8:59 will fall into the hour 8. If the
interval was synchronized to expire at exactly 9:00, then
data collected between 8:45 and 9:00 would fall into the hour
9.
NETWORK=(SMF,VSAM): Network data from START COLLECT and
START MONITOR commands is written to both SMF and to the NPM
REVIEW File. Although multiple destinations are specified in
this example for the NPM network data, CA MICS only processes
the data written to SMF.
SESSION=(SMF,VSAM): Session interval records generated by
SESSCOLL (Session collect) commands are written to both SMF
and the Session Statistics File, a VSAM key-sequenced data
set. Although multiple destinations are specified in this
example for the NPM session data, CA MICS only processes the
data written to SMF.
NSA=(SMF): Network session accounting records generated by
the NCP for LU sessions are written to SMF. To generate
network session accounting records, you must also specify
NPA=YES and SESSACC=YES on the BUILD macro in the NCP source
definition statements.
NPM HOSTCOLL=YES,
INTERVAL=(225,SEC),SESSINT=4,SYNCH=(3,59),
LOG=SMF,NETWORK=(SMF),
SESSION=(SMF),NSA=(SMF)
SESSCOLL Initialization Statement: BVAL=(1,3,5,10):
Default boundary values (BVAL) for the distribution groups
for logical unit session transit times have been set to 1, 3,
5, and 10 seconds. For example, if operator (total) response
time is 3 seconds, then the counter for distribution group 2
(3 seconds) is incremented.
HOST=900, NET=900, OPER=900: The HOST, NET, and OPER
operands specify 900 seconds as the maximum session transit
time thresholds for host, network, and total response events.
In the example below, host, network, and total response times
greater than 900 seconds are discarded to prevent these
excessive response times from skewing average response time
and other calculated response time values.
SESSCOLL BVAL=(1,3,5,10),
HOST=900,
NET=900,
OPERATOR=900
Sample Network Initialization Command
-------------------------------------
NPM initialization commands execute at NPM activation.
Through the use of the DAILY and CLOCK parameters, you can
also define the initialization commands to start and stop
each day, even though NPM is kept active on a continuous
basis. In the example below, NPM collects data on all lines
attached to NCP01 from 6 a.m. until 10 p.m. Collection
interval 3 is 15 minutes because the base interval is defined
as 225 seconds in the initialization statements above. The
network collection records are written to the sequential log,
which is defined as SMF in the initialization statements.
NETCOLL NCP=NCP01,OPTIONS=START,RESOURCE=ALLNAMES,
CLOCK=(06,22),DAILY=YES
Sample Session Initialization Command
-------------------------------------
In the example below, NPM collects session statistics on any
logical unit in session with NPM. The session collection
interval, 15 minutes, is defined above in the initialization
statements. The data for sessions is started dynamically for
sessions that are currently inactive.
SESSCOLL APPL=NPM,BVAL=(1,3,5,10),DYNAMIC=YES,
HOST=900,NET=900,OPERATOR=900
The following sections discuss features of NPM:
1 - NPM Network Collector Function
2 - NPM Session Collector Function
3 - NPM Network Session Accounting
4 - NPM Network Gateway Accounting
Copyright © 2014 CA.
All rights reserved.
|
|