COMMS Configuration Syntax

Network Monitoring on HPE NonStop servers is configured using the COMMS Configuration and allows for the collection of data and reports on X25, conventional TCP/IP, parallel TCP/IP, TCP/IPv6 (in IPv4 mode) and HPE NonStop Cluster I/O Protocols (CIP) subsystems through the NonStopCommunicationLink (COMMLINK) record. This provides the data required to alert on communication infrastructure problems, assistance in determining bottlenecks and help in optimizing resources.

Currently, it is not able to collect data on TCP/IPv6 subsystems in 'INET6' (IPv6) or 'DUAL' (IPv4 and IPv6) modes.

The COMMS Configuration is used to specify what is to be monitored and in how much detail.

SUBSYS COMMS

ADD X25-LINE ({*|<line-name>}[, [NO]CIRCUITS])
[X25-INT (<number-of-minutes>)]
[X25-RESET ({Y|N})]
ADD TCP-SNET ({<tcpip-process>|*}[.{*|<#subnet>}][, [NO]SOCKETS])
[TCP-INT (<number-of-minutes>)]
[TCP-RESET ({Y|N})]
ADD PTCP-SNET ({<monitor-process>[.*]|*[.*]}[.<#subnet>}][, [NO]SOCKETS])
[PTCP-INT (<number>, {minutes|seconds})]
[PTCP-RESET ({Y|N})]
ADD CIPTCP-SNET ({<monitor-process>[.*]|*[.*]}[, [NO]SOCKETS])
[CIPTCP-INT (<number>, {minutes|seconds})]
[CIPTCP-RESET ({Y|N})]
[CLIM-INT (<number>, {minutes|seconds})]
Subnet for Network CLIM is not yet supported

Syntax Elements

ADD X25-LINE ({*|<line-name>}[, [NO]CIRCUITS])

This statement is used to add the X25 line to be monitored. The option of monitoring circuits can be included if required. A separate ADD clause must be included for each line to be monitored with each entry placed on a separate line.

[X25-INT (<number-of-minutes>) ]

(Optional) This statement is used to specify a collection interval for the X25 data. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.

[X25-RESET ({Y|N}) ]

(Optional) This statement is used to specify whether or not the X25 statistics counters will be reset for all configured subsystems before the collector gathers the statistics. The default for this option is Yes (Y) causing statistics to be reset at the beginning of each collection interval.

ADD TCP-SNET ({<tcpip-process>|*}[.{*|<#subnet>}][, [NO]SOCKETS])

The conventional TCP/IP subnet to be monitored. The option of monitoring sockets can be included if required. A separate ADD clause must be included for each IP to be monitored with each entry placed on a separate line.

[TCP-INT (<number-of-minutes>) ]

(Optional) This statement is used to specify a collection interval for the conventional TCP/IP data. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.

[TCP-RESET ({Y|N}) ]

(Optional) This statement is used to specify whether or not the conventional TCP/IP statistics counters will be reset for all configured subsystems before the collector gathers the statistics. The default for this option is Yes (Y) causing statistics to be reset at the beginning of each collection interval.

ADD PTCP-SNET ( {<monitor-process>|* }[.<#subnet>][, [NO]SOCKETS] )

This statement is used to add the parallel TCP/IP or TCP/IPv6 (in IPv4 mode) subnet to be monitored and reported for Commlink data.

Example:

ADD PTCP-SNET (*)

All monitors and subnets

ADD PTCP-SNET (*, SOCKETS)

All monitors, subnets and sockets

ADD PTCP-SNET (*.#SN1)

Subnet SN1 of all monitors

ADD PTCP-SNET ($ZPTM1.#SN1)

Subnet SN1 of monitor $ZPTM1

[PTCP-INT (<number>, {minutes|seconds}) ]

(Optional) This statement is used to specify a collection interval for parallel TCP/IP or TCP/IPv6 (in IPv4 mode) data. If this statement is omitted the default will be 30 minutes. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.

[PTCP-RESET ({Y|N}) ]

(Optional) This statement is used to specify whether or not the parallel TCP/IP or TCP/IPv6 (in IPv4 mode) statistics counters will be reset before the collector gathers the statistics. The default for this option is Yes (Y) causing statistics to be reset at the beginning of each collection interval.

ADD CIPTCP-SNET ( { <monitor-process>[.*] | *[.*] }[, [NO]SOCKETS] )

This statement is used to add the Network CLIM’s TCP/IP to be monitored and reported for COMMLINK record data.

Examples:

ADD CIPTCP-SNET (*)

All monitors

ADD CIPTCP-SNET (*.*)

All monitors only. Subnet not yet supported

ADD CIPTCP-SNET (*, SOCKETS)

All monitors and sockets

ADD CIPTCP-SNET ($ZCM00)

Monitor $ZCM00 only

[CIPTCP-INT (<number>, {minutes|seconds}) ]

(Optional) This statement is used to specify a collection interval for CIP TCP/IP data for the COMMLINK record. If this statement is omitted the default value is 30 minutes. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.

[CIPTCP-RESET ({Y|N}) ]

(Optional) This statement is used to specify whether or not the CIP statistics counters will be reset before the collector gathers the statistics. The default for this option is Yes (Y) causing statistics to be reset at the beginning of each collection interval. This item is only effective if a CIPTCP-SNET statement is also present.

[CLIM-INT (<number>, {minutes|seconds}) ]

(Optional) This statement is used to specify a collection interval for the CLIM data. There is no default value, if this item is not present in the COMMS Configuration then no data for the NSCLIM record will be collected. The collection of data will be spread out across the specified interval. Intervals are not aligned to a wall clock time.

Provide feedback on this article