| Oracle® Communications Measurements Reference Release 46.6 E93320 Revision 1 |
|
 Previous |
 Next |
The per card SCTP layer measurements and reports are shown below.
Command Examples
UI: rept-meas:type=comp:enttype=sctpcard:loc=1204
FTP: rept-ftp-meas:type=comp:enttype=sctpcard
Measurement Events
Table 3-29 Component SCTPCARD Measurements
| Event Name | Description | Unit |
|---|---|---|
| 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). No register will be pegged if a message intended for an association is received and that association is in the CLOSED state. |
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 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 |
| 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 yet 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. (See UNASCTPK register.) |
peg count |
| SCPKTRER |
SCTP Packets Received With Checksum ErrorThe 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:
|
status |
| UNASCTPK |
Unassociated (Out-of-the-Blue) SCTP PacketsThe 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 Output Examples
stdcfg2b 07-12-31 01:00:04 EST UNKNOWN 47
TYPE OF REPORT: COMPONENT MEASUREMENTS ON SCTPCARD
REPORT PERIOD: LAST
REPORT INTERVAL: 07-12-31 00:30:00 THRU 00:59:59
SCTPCARD-COMP MEASUREMENTS: LOC: 1204
These measurements are from 07-12-31, 00:30:00 through 00: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, ASOCABTD = 0, ASOCSHTD = 0
FTP Output Examples
Table 3-30 COMP SCTPCARD Column Header
| Field Name | Description |
|---|---|
| LOC | Location |
FTP Example Output File Name: comp-sctpcard_20071115_1200.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:11:37","EST","COMPONENT MEASUREMENTS ON SCTPCARD","LAST",”2007-12-31”,"11:45:00","12:00:00",3<cr><lf> <cr><lf> "STATUS","LOC","DATCHKSN","RTXCHNKS","DATCHKRC","SCPKTSNT","SCPKTRCV","SCPKTRER", "UNASCTPK","SCOCTSNT","SCOCTRCV","CNTLCHKS","ORDCHKSN","CNTLCHKR","ORDCHKRC", "ASOCABTD","ASOCSHTD"<cr><lf> "K","1101",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<cr><lf> "K","1103",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 + 15*(6 char data) + 2 = 103 chars
For a report of 80 cards, the typical file size is:
Table 3-31 Typical File Size: comp-sctpcard.csv
| System header | + | Report header | + | Report data | = | File Size |
|---|---|---|---|---|---|---|
| 250 |
+ |
160 |
+ |
8240 |
= |
8650 bytes |
