Starting a packet trace in MainView IP


Use the following procedure to start a packet trace.

The packet trace can be started for a specific IP address, source port, destination port, protocol type, and packet length.

A packet trace may also be started by a MainView alarm on any connection views for a specific connection. When the alarm triggers a packet trace is started. It ends when the trace is stopped. This automoated packet trace requires the MainView for Networks solution as well as an AUTOOPERATOR (AO) rule.

Error
Warning

If you are tracing a packet (or a socket), and you cancel the PAS, you might encounter an abend. BMC recommends that you shut down the PAS normally before starting thr traceor stop the trace before you stop the PAS.

You can perform a packet trace by using one of the following methods:

  • Issue the STA line command from the Packet Trace view.
  • Issue the PKT line command from a Connections view.

To start a packet trace

  1. From the EZIP menu, select Packet Tracing from the Diagnostics section, and press Enter.The Packet trace view (PKTTRACE) is displayed (see the following figure):

    Packet trace view

     19JAN2012  05:59:07 ------ MAINVIEW WINDOW INTERFACE (V6.0.00) ----------------
     COMMAND  ===>                                                 SCROLL ===> PAGE
     CURR WIN ===> 1        ALT WIN ===>                                            
     >W1 =PKTTRACE=========(ALL======*=======)19JAN2012==05:58:19====MVIP=====D====3
     Command Stack    Trace      Userid   Nbr   Prot IP               Port  Pkt   Tr
     ------- Name     Status     Started  Recs  Type Address          Nbr   Len   ID
     OK      TCPIP    NOT ACTIVE              0                                     
     OK      TCPIP    STOPPED    MVSNXL1   3579                                     
             TCPIP    STOPPED    MVSNXL1    658
  2. To trace packets, type STA or START or STARTALL (to start all the packet traces), in the Command field, and press Enter.
  3. (optional) You can apply the following filters by changing their field entry:
    • Time type for local or GMT
    • Trace Identifier for an identifier to be associated with the trace
    • Packet Length for length of the packet to be traced
    • Duration for the duration before active trace is stopped (hh:mm:ss)
    • Protocol Type for the protocol type to be traced
    • Port Number for which you can specify up to 4 port numbers to be matched on either destination or source port in all packets.
    • IP Address to specify up to 4 IP Addresses (separate by commas)
  4. Press F3to complete the task
  5. (Optional)To trace encrypted packets, type YES in the IPSec Data field.

    Warning

    Note

    The EZB.TRCSEC.sysname.tcpname.IPSEC resource profile must be authorized.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView for IP 3.5