search cancel

Smarttrace incorrectly reporting padded packets

book

Article ID: 134541

calendar_today

Updated On:

Products

NetMaster Network Management for TCP/IP

Issue/Introduction

Smarttrace seems to be incorrectly reporting padded packets and misinterpreting the packets as a result. 

After export of the trace out into wireshark the issue does not show.

Re-importing that  trace back in to Netmaster then reports the length correctly.


EXAMPLE:

--------------------------------------------------------------------------------,

PKT  Packet # ........ 00005           Direction .......... Recv

     Date ............ 14-FEB-2019     Time ............... 14:22:37.256790

     Link Name ....... OSA32P4_B220


IP   Source Addr ..... 190.59.32.180   Destination Addr ... 10.68.45.58

     IP Version ...... 4               Header Length ...... 20

     Differentiated Services  x'00'    Total Length ....... 52

     Differentiated Services Codepoint: CS0 Default (0)

     Explicit Congestion Notification: B'00' Non ECN-Capable Transport, Non-ECT

     Identification    x'1A39'         Flags .............. DontFragment B'010'

     Frag Offset ..... 0               Time To Live ....... 121

     Protocol ........ TCP             Header Checksum .... x'FC1B'

     *WARNING* Padded packet


          +----------- IP Header -----------+ +--- EBCDIC ---+ +---- ASCII ---+

    +0000 45000034 1A394000 7906FC1B 0A3B9EA0         `        E  4 [email protected] y    ;

    +0010 0A4F3845                             |                O8E


TCP  Src Port ........ 436             Dest Port .... 31332

     Seq Number ...... 1640683154      Ack Number ... 63596253

,Command ===>,

     Data Offset ..... 32              Flags ........ ACK

     Window .......... 513             Checksum ..... x'477E' (Incorrect)

     Urgent Pointer    0


     TCP Option                        Value

     ----------                        -----

     No Operation

     No Operation

     Time Stamp Value                  x'03A62878'

                Echo Reply             x'BAEB2823'


          +---------- TCP Header -----------+ +--- EBCDIC ---+ +---- ASCII ---+

    +0000 01BB8DE2 61CAD692 03CA66DD 80100201    S/ Ok             a     f

    +0010 477E0000 0101080A 03A62878 BAEB2823  =       w       G~        (x  (#


Record 1

     Protocol ........ APPLICATION_DATA  ( x'17' )

     Version ......... SSL 3.0         Length ....... 0


          +-------- Record 1 Header --------+ +--- EBCDIC ---+ +---- ASCII ---+

    +0000 1703


-------------------------------------------------------------------------------

Cause

Incorrect packet data supplied by IBM TCPIP stack

Environment

Release : 12.2

Component : CA NetMaster Network Management for TCP/IP

Resolution

To correct the packet data: 

IBM APAR PH10517: TRACE NMI INTERFACE RETURNING EXTRA PACKET DATA with PTF UI63028.


To ensure correct formatting of data received by Netmaster:

Netmaster 12.2 PTF SO07505