36.3. UPNPS diagnostics and statistics
Prev Chapter 36. UPNP - Universal Plug and Play Next

36.3. UPNPS diagnostics and statistics

36.3.1. UPNPS diagnostics

This command reports the current situation of the UPNPS resource:

[18:06:40] ABILIS_CPX:d d upnps

RES:UPnPS ---------------------------------------------------------------------
       Universal_Plug_and_Play_Server                                          
       STATE:ACTIVE        SESNUM:5      
       CUR-REQUESTS:0      PEAK-REQUESTS:0      
       - HTTP Channels --------------------------------------------------------
       CH  TCP-State  LocAdd-LocPort        RemAdd-RemPort
       ------------------------------------------------------------------------
       0   LISTENING  000.000.000.000-1900  
       1   LISTENING  000.000.000.000-1900  
       2   LISTENING  000.000.000.000-1900  
       3   LISTENING  000.000.000.000-1900  
       4   LISTENING  000.000.000.000-1900

The meaning:

STATE

The UPNPS driver state:

  • INACTIVE - configuration parameter ACT:NO.

  • ACTIVE - The driver is fully ready to work.

SESNUM

UPNP queries which can be handled simultaneously.

CUR-REQUESTS

Current user queries to the UPNP driver.

PEAK-REQUESTS

The peak of user queries to the UPNP driver.

ID

UPNP server HTTP channel ID.

TCP-State

UPNP server HTTP channel TCP state:

  • CLOSED - Channel is closed (ready state).

  • LISTENING - channel is listening.

  • CALLED - called procedure.

  • CALLING - calling procedure.

  • CONNECTED - channel is connected.

  • CLEARING - clearing state.

  • CLEARED - cleared state.

  • DOWN : channel is down.

LocAdd-LocPort

Local IP Address and Local Port.

RemAdd-RemPort

Remote IP Address and Remote Port.

36.3.2. UPNPS statistics

This command can help to understand what is happening, in case of troubles:

[18:06:40] ABILIS_CPX:d s upnps

RES:UPnPS ---------------------------------------------------------------------
       Universal_Plug_and_Play_Server                                          
       --- Cleared 5 days 00:13:13 ago, on 11/10/2017 at 14:24:04 -------------
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       SSDP-CHR   |          0|          0|SSDP-FRM   |          0|          0|
       SSDP-LOST  |          0|           |SSDP-BADFMT|          0|           |
       SOAP-REQ   |          0|           |SOAP-RSP   |           |          0|
       SOAP-ERR   |          0|           |SOAP-BADFMT|          0|           |
       TCP-CHR    |          0|          0|DENIED-IP  |          0|           |
       ------------------------------------------------------------------------

With reference to the shown interval of time («Cleared 5 days 00:13:13 ago») these counters show the number of:

SSDP-CHRIncoming/outgoing SSDP characters from/to UDP.
SSDP-FRMIncoming/outgoing SSDP packets from/to UDP.
SSDP-LOSTLost incoming SSDP packets: no buffer.
SSDP-BADFMTLost incoming SSDP packets with bad format.
SOAP-REQSOAP client requests.
SOAP-RSPSOAP responses.
SOAP-ERRSOAP errors.
SOAP-BADFMTLost incoming SOAP packets with bad format.
TCP-CHRIncoming/outgoing SSDP characters from/to TCP.
DENIED-IP UPNPS requests received from the clients but not processed because requester (the author of this UPNPS request) is not allowed. The not-allowed requester is a client whose IP address is not present in IPSRC and IPSRCLIST parameters configuration.
Prev Up Next
36.2. UPNPS configuration Home 36.4. How to configure UPNP server