SCTPCARD MTCD Report

Command Examples

UI:rept-meas:type=mtcd:enttype=sctpcard:loc=1201
FTP:rept-ftp-meas:type=mtcd:enttype=sctpcard

Measurement Events

Table 3-90 lists the SCTPCARD events and their descriptions.

Table 3-90 Daily Maintenance (MTCD) and Day-to-Hour Maintenance (MTCDTH) SCTPCARD Measurements

Event Name	Description	Unit
ACTVESTB	SCTP Association Active Establishments - The number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the COOKIEECHOED state (COOKIE-ECHOED --> ESTABLISHED). In this case the upper layer (i.e., the local M2PA) was the initiator of the association establishment between the SCTP peers.	peg count
ASOCABTD	SCTP Aborted Associations - The number of times that SCTP associations have made a direct transition to the CLOSED state from any state using the primitive “Abort” (AnyState --Abort--> CLOSED), conveying an ungraceful termination of the association.	peg count
ASOCSHTD	SCTP Association Shutdowns - The number of times that SCTP associations have made a direct transition to the CLOSED state from either the SHUTDOWN-SENT state or the SHUTDOWN-ACK-SENT state, conveying graceful termination of the association.	peg count
CNTLCHKR	SCTP Control Chunks Received - The number of SCTP control chunks received from the remote peer (excluding duplicates).	peg count
CNTLCHKS	SCTP Control Chunks Sent - The number of SCTP control chunks sent to the remote peer (excluding retransmissions), including chunks for which an association has not yet been formed.	peg count
DATCHKRC	Number of SCTP DATA chunks received from the remote SCTP peer (excluding duplicates and discards).	peg count
DATCHKSN	Number of SCTP DATA chunks sent to the remote SCTP peer (excluding retransmissions).	peg count
ORDCHKRC	SCTP Ordered Data Chunks Received - The number of SCTP ordered data chunks received from the remote peer (excluding duplicates).	peg count
ORDCHKSN	SCTP Ordered Data Chunks Sent - The number of SCTP ordered data chunks sent to the remote peer (excluding retransmissions).	peg count
PASVESTB	SCTP Association Passive Establishments - The number of times that SCTP associations have made a direct transition to the ESTABLISHED state from the CLOSED state (CLOSED --> ESTABLISHED), indicating that the remote peers initiated association establishment.	peg count
RTXCHNKS	SCTP Association Retransmitted Chunks - The number of SCTP data chunks retransmitted to the remote SCTP peer. When T3-rtx expires, the DATA chunks that triggered the T3 timer will be re-sent according with the retransmissions rules. Every DATA chunk that was included in the SCTP packet that triggered the T3-rtx timer must be added to the value of this counter.	peg count
SCOCTRCV	SCTP Packet Octets Received - The number of octets comprising valid SCTP packets received from the remote peer, including packets for which an association has not yet been formed.	octets
SCOCTSNT	SCTP Packet Octets Sent - The total number of octets comprising SCTP packets submitted to the IP layer for transmittal to the remote peer, including packets for which an association has not been formed.	octets
SCPKTRCV	SCTP Packets Received - The total number of SCTP packets received from the remote peer that had a valid checksum. Duplicates are included. SCPKTRCV register excludes the pegging of SCTP Packets received when no instance exists on the card for any of the associations, i.e., the association parameter "OPEN" has value "NO" for all the associations configured on the card. Also, excludes pegging of set up messages (INIT and COOKIE-ECHO) that are part of association establishment procedure.	peg count
SCPKTRER	SCTP Packets Received With Checksum Error - The number of SCTP packets received from remote peers with an invalid checksum	peg count
SCPKTSNT	SCTP Packets Sent - The total number of SCTP packets sent to the remote peer, i.e., submitted by the local SCTP instance to the IP layer for transmission. Retransmissions are included. SCPKTSNT register excludes initial SCTP association set-up messages (INIT-ACK and COOKIE-ACK). For M2PA association INIT packet is never pegged.	peg count
STATUS	Indication of Data Validity: K indicates good data I indicates incomplete interval N indicates data not current	status
UNASCTPK	Unassociated (Out-of-the-Blue) SCTP Packets - The number of “out-of-the-blue” SCTP packets received by the host, i.e., SCTP packets correctly formed with the correct checksum value, but for which the receiver (local SCTP) was not able to identify the association to which the packet belongs. UNASCTPK register includes the pegging of SCTP Packets received when no instance exists on the card for any of the associations, i.e., the association parameter "OPEN" has value "NO" for all the associations configured on the card (See SCPKTRCV register).	peg count

UI Reports

UI Example Output:

    stdcfg2b 07-12-31 EST  UNKNOWN 38.0.0-XX.XX.0
    TYPE OF REPORT: DAILY MAINTENANCE MEASUREMENTS ON SCTPCARD
    REPORT PERIOD: LAST
    REPORT INTERVAL:  07-12-31  00:00:00 THRU 23:59:59

    SCTPCARD-MTCD MEASUREMENTS: LOC: 1201

    These measurements are from 07-12-31, 00:00:00 through 23:59:59.
    DATCHKSN   =         0, RTXCHNKS   =         0, DATCHKRC   =         0,
    SCPKTSNT   =        20, SCPKTRCV   =        20, SCPKTRER   =         0,
    UNASCTPK   =         0, SCOCTSNT   =         0, SCOCTRCV   =         0,
    CNTLCHKS   =       400, ORDCHKSN   =       400, CNTLCHKR   =         0,
    ORDCHKRC   =         0, ACTVESTB   =         0, PASVESTB   =         0,
    ASOCABTD   =         0, ASOCSHTD   =         0

;

FTP Reports

FTP Example Output File Name: mtcd-sctpcard_20071115_2400.csv

FTP Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND",
"NUMENTIDS"<cr><lf>
"tekelecstp",”38.0.0-XX.XX.0”,”2007-12-31”,"12:12:10","EST",
"DAILY MAINTENANCE MEASUREMENTS ON SCTPCARD","LAST",”2007-12-30”,
"00:00:00","24:00:00",3<cr><lf>
<cr><lf>
"STATUS","LOC","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCPKTRER",
"UNASCTPK","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC","ACTVESTB",
"PASVESTB","ASOCABTD","ASOCSHTD"<cr><lf>
"K","1101",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>
"K","1102",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>
"K","1103",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>

Assuming each data line will be:

4 char status + 7 char location + 17*(6 char data) + 2 = 115 chars

For a report of 80 cards, typical file size is:

Table 3-91 Typical File Size: mtcd-sctpcard.csv

System header		Report header		Report data	=	File Size
250	+	185	+	9200	=	9635 bytes