STPLAN AVL Report

This enttype consists of measurements for LIM and DSM cards. The outputs are separate for the UI reports and combined for the FTP reports. The FTP reports appear after the UI reports for the DSM cards.

Note:

The peg counts forSTPLAN measurements have the possibility of rolling over during periods of highSTPLAN message transmit and receive. On the measurement reports these measurements show up as negative numbers. This indicatesSTPLAN transmit and receive measurements have values greater than four gigabytes of data.

Command Examples

UI
- rept-meas:type=avl:enttype=stplan:loc=xxxx
FTP
- rept-ftp-meas:type=avl:enttype=stplan

Table 3-54 Availability STPLAN Measurements

Event Name	Description	Unit
ENETALNERR	Ethernet Alignment Error - The number of packets not received over the STPLAN interface because of Ethernet alignment errors.	peg count
ENETBUSBSY	Ethernet Bus Busy - The number of transmissions attempted when the STPLAN Ethernet bus was busy.	peg count
ENETCOLERR	Ethernet Collision Error - The number of packets not transmitted by STPLAN because of excessive collisions on the STPLAN Ethernet bus. The FTC Reports will display this register as zero for card types other than ACM cards.	peg count
ENETCRCERR	Ethernet CRC Error - The number of packets not received on the STPLAN Ethernet due to CRC errors.	peg count
ENETOCTRCV	Ethernet Octets Received - The total number of octets received on the STPLAN Ethernet interface.	peg count
ENETOCTXMT	Ethernet Octets Transmitted - The total number of octets transmitted on the STPLAN Ethernet interface.	peg count
ENETOVRERR	Ethernet Receive Buffer Overflow Errors - The number of packets not received by STPLAN because of a receive buffer overflow.	peg count
IPADDRERR	IP Address Error - The total number of inbound IP datagrams discarded on the STPLAN interface due to a bad destination address.	peg count
IPHDRERR	IP Header Errors - The total number of inbound IP datagrams discarded on the STPLAN interface due to header errors. The FTC Reports will display this register as zero for card types other than ACM cards.	peg count
IPPROTERR	IP Protocol Error - The number of inbound IP datagrams discarded by STPLAN due to an error in the packet (invalid protocol). The FTC Reports will display this register as zero for card types other than ACM cards.	peg count
SLANDISC1	STPLAN Discarded 1 - Number of SLAN MSUs discarded by the LIM cards for STPLAN feature disabled and records aging off of the local queue.	peg count
SLANDISC2	STPLAN Discarded 2 - The number of SLAN MSUs discarded by the SLAN cards for network problems and unreachable far end servers. During network outages the SLAN cards will stop TVG/MFC grants or go into flow control. This causes the PDUs to be queued on the LIM cards, so the majority of discards will be pegged on SLANDISC1 under these circumstances.	peg count
SLANDSBLD	STPLAN Disabled – The duration that the STPLAN screening/copy feature was disabled.	msec
SLANSCRND	STPLAN Screened – Number of MSUs that were copied to the STPLAN interface after passing gateway screening.	peg count
SLANXMIT	STPLAN Transmit - The number of MSUs sent to the host destination. The FTC Reports will display this register as zero for card types other than ACM cards.	peg count
SLANXMIT	STPLAN Transmit - The number of MSUs sent to the host destination.	peg count
TCPCONNFLD	TCP Connections Failed - The total number of TCP connections that have failed on the STPLAN interface. MCP/OAMHC Reports will display this register as zero for card types other than ACM cards.	peg count
TCPSEGRCVD	TCP Segment Received - The total number of TCP segments received on the STPLAN interface. MCP/OAMHC Reports will display this register as zero for card types other than ACM cards.	peg count
TCPSEGSENT	TCP Segment Sent - The total number of TCP segments sent on the STPLAN interface. The FTC Reports will display this register as zero for card types other than ACM cards	peg count

UI Example Output:

    e1061001 10-08-16 19:36:15 EST  EAGLE5 42.0.0-63.32.0
    TYPE OF REPORT: AVAILABILITY MEASUREMENTS ON STPLAN
    REPORT PERIOD: LAST
    REPORT INTERVAL:  10-08-16  19:00:00 THROUGH 19:29:59

    STPLAN-AVL MEASUREMENTS: LOC: 1215

    These measurements are from 10-08-16 19:00:00 through 19:29:59.
    SLANDSBLD  =         0 SLANDISC1  =         0 SLANDISC2  =         0
    SLANSCRND  =         0 SLANXMIT   =         0 ENETALNERR =         0
    ENETCRCERR =         0 ENETCOLERR =         0 ENETBUSBSY =         0
    ENETOVRERR =         0 ENETOCTXMT =         0 ENETOCTRCV =         0
    TCPCONNFLD =         0 TCPSEGRCVD =         0 TCPSEGSENT =         0
    TCPSEGXMT2 =         0 TCPRCVERR  =         0 TCPRSTSENT =         0
    IPHDRERR   =         0 IPADDRERR  =         0 IPPROTERR  =         0

;

    e1061001 10-08-16 19:36:17 EST  EAGLE5 42.0.0-63.32.0
    END OF ON-DEMAND STPLAN-AVL MEASUREMENT REPORT
;

FTP Example Output File Name:avl-stplan_19990117_1530.csv

FTP Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS"
"e1061001","EAGLE5 42.0.0-63.32.0","2010-08-16","20:46:45","EST ","AVAILABILITY MEASUREMENTS ON STPLAN","LAST","2010-08-16","20:00:00","20:30:00",2

"STATUS","TYPE","LOC","SLANDSBLD","SLANDISC1","SLANDISC2","SLANSCRND","SLANXMIT",
"ENETALNERR","ENETCRCERR","ENETCOLERR","ENETBUSBSY","ENETOVRERR","ENETOCTXMT",
"ENETOCTRCV","TCPCONNFLD","TCPSEGRCVD","TCPSEGSENT","TCPSEGXMT2","TCPRCVERR",
"TCPRSTSENT","IPHDRERR","IPADDRERR","IPPROTERR"
"K","LIM","1104",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
"K","DSM","1215",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

Assuming each data line will be:

4 char status + 6 char TYPE + 7 char LOC + 21*(6 char data) + 2 = 145 chars

For a report of 100 LIMs and 10 DSMs, the typical file size is:

Table 3-55 Typical File Size: avl-stplan.csv

System header	+	Report header	+	Report data	=	File Size
250	+	284	+	145	=	679 bytes