OVNPM 1.5.2 - Performance Agent for NonStop Server Monitoring Guide

3-20 TCP/IP

The TCP/IP entity type provides TCP/IP statistics about the transport provider, UDP, and subnet traffic.

NOTE:

All providers can be added in the monitoring configuration. However, the TCP/IP domains do not

collect data for the CIPSAM provider.

3-20-1 TCP/IP Instance Configuration

Domain

TCP/IP

Description

The TCPIP entity type provides TCPIP statistics.

Syntax Syntax for Monitoring the TCPIP Transport Provider

tcpip <TransportProviderName>[:<layer>] [,<trendFlag>]

Where:

<transportProviderName> is a TCPIP transport provider like $ztc0.

<layer> is the tcp, udp layer (or protocol). ICMP and IP are not supported yet. If omitted OVNPM

consider TCP layer

Syntax to monitor a subnet:

tcpip <subnetName>[“:subnet”] [,<trendFlag>]

Where,

<subnetName> is the subnet name like $ztc0.#sn1

NOTE: The string “:subnet” can be omitted.

Example

“Tcpip $ztc0:tcp , trend=on” monitors the tcp layer of the transport process

$ztc0.

Tcpip $ztc0.#sn1:subnet , trend=on” monitor the subnet $ztc0.#sn1

NOTE:

Tcpip transport provider monitoring will require an adjustment of a DCPRM parameter ttpMaxNb

(number of Tcpip transport p

rocesses i.e. $ztc(nn). Refer Appendix D: DCPRM File for details. After User adds

TCP transport providers

to the USERCFG file the SV_DCPRM_SET macro needs to be executed to adjust

ttpMaxN

b. Once executed OVNPM will needs to be stopped and restarted.

Importance According to the Tcpip type (Transport, Process, protocol, subnet and route), some metric in TCPIP are not

used. Values of unused metric are set to no-data. This is demonstrated in the following array.

Metrics :tcp :udp :subnet

byte-rcv.kbs/s yes no no

byte-snd.kb/s yes no no

con-closed.nb yes no no

con-estab.nb yes no no

con-in.nb yes no no

con-out.nb yes no no

data-pkg-rcv.nb/S yes no no

data-pkt-snd.nb/s yes no no

pkt-rcv.nb/s yes yes yes

pkt-snd.nb/s yes yes yes