Tracing for MainView for IP


This topic describes all of the tracing capabilities for MainView for IP.

Starting Traces for MainView for IP

This section describes how to start a Trace in MainView for IP.

Packet Tracing

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 MainView Alarm Manager on any connection views for a specific connection. When the alarm triggers a packet trace is started. When the alarm ends, the Packet Trace is stopped. This automated Packet Trace requires the MainView for Networks solution and a MainView AutoOPERATOR Rule.

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:

    Packet trace view

    packet_trace.png 

  2. To trace Packets, type STA, PKT, 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:

    Filter

    Description

    Time type

    Specifies the local time or GMT

    Trace Identifier

    Specifies an identifier to be associated with the trace

    Packet Length

    Specifies the length of the packet to be traced

    Packet Limit

    Specifies the number of packets to trace before stopping trace

    Duration 

    Specifies the duration before active trace is stopped (hh:mm:ss)

    Start Time

    Specifies the time when the packet trace will be started

    Protocol Type

    Specifies the protocol type to be traced

    Port Number

    Specifies up to 4 port numbers to be matched on either the destination or source port in all packets

    IP Address

    Specifies  up to four IP addresses (separate by commas)

    Interface name

    Specifies the name of the network interface

    Discard Code

    Specifies the Break up

  4. Press F3 to complete the task.
  5. (optional) To trace encrypted packets, type YES in the IPSec Data field.

The EZB.TRCSEC.SysName.TcpName.IPSEC resource profile must be authorized.

Data Tracing

The Data Trace can be started for a specific IP address, source port, destination port, protocol type, and packet length. You can perform a Data Trace by using one of the following methods:

  • Issue the STA line command from the DATTRACE view.
  • Issue the DAT line command from a Connections view.

To start a Data Trace

  1. From the EZIP menu, select Data Tracing from the Diagnostics section, and press Enter.The Data Trace view (DATTRACE) is displayed:

    Data Trace view

    data_trace.PNG

  2. To start Data Tracing, type STA, DAT or STARTALL (to start all the Data Traces) in the Command field, and press Enter.
  3. (optional) You can apply the following filters by changing their field entry:  

    Filter

    Description

    Time type

    Specifies the local or GMT

    Trace Identifier

    Specifies the identifier to be associated with the trace

    Data Length 

    Specifies the length of data to be traced

    ATTLS Data 

    Specifies the Trace encrypted ATTLS data

    Start Time

    Specifies the time when the packet trace will be started

    Protocol Type

    Specifies the protocol type to be traced

    Port Number

    Specifies up to 4 port numbers to be matched on either destination or source port in all packets.

    IP Address

    Specifies up to four IP addresses (separate by commas 

  4. Press F3 to complete the task.
  5. (Optional) To trace encrypted packets, type YES in the ATTLS Data field.


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

OSA Tracing

OSA Tracing allows you to trace inbound and outbound frames for an OSA-Express2 or later in QDIO mode. You can filter the OSA Trace by specifying parameters such as IP Address, IP Port, or frame type, and how much data to be collected.

To start an OSA Trace

  1. From the EZIP menu, select OSA Tracing from the Diagnostics section, and press Enter.The OSA Trace view (OSATRACE) is displayed:

    OSA Trace view

    OSATRACE.png

  2. To trace frames (packets), type STA in the Command field, and press Enter
  3. Insert the port name.
    The port name specifies which OSA port needs tracing. 

    This is the same port name that is defined on the VTAM TRLE statement PORTNAME keyword. This is a required parameter.

  4. (optional) You can apply the following filters by changing their field entry:

    Filter

    Description

    Time type

    Specifies the local or GMT

    Trace Identifier

    Specifies the identifier to be associated with the trace

    Data Length

    Specifies the length of the packet to be traced

    Duration 

    Specifies the duration before active trace is stopped (hh:mm:ss)

    Start Time

    Specifies the time when the OSA trace will be started

    Interface name

    Specifies the name of the network interface

    Port Name 

    Specifies the Port Name of the OSA card – required field

    Port Number

    Specifies up to 4 port numbers to be matched on either destination or source port in all packets.

    Protocol Type

    Specifies the protocol type to be traced

    MAC Address 

    Specifies the 12 byte hexadecimal MAC Address

    Ethernet Type 

    Specifies the Ethernet Frame Type

    VLANID 

    Specifies the VLAN Identifier Value

    IP Address

    Specifies up to four IP addresses (separate by commas)

    Discard Code

    Specifies the IP packet discard reason code

  5. Press F3 to complete the task.

Socket Tracing

The Socket Trace can be started for a specific MVS job name, source port, destination port, and destination IP address. The START Socket Trace command initiates a Socket Trace with the specified filters
(for example, job name, and so on.). The Socket Trace can be viewed through the display command. Only one socket trace can be active per stack at a time.

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 or stop the Trace.

Use the following procedure to start a Socket Trace.

To start a Socket Trace

  1. From the EZIP menu select Socket Tracing from the Diagnostics section, and press Enter.The Socket Tracing view (SKTTRACE) is displayed. 

    Socket Tracing view

    26OCT2009  09:12:43 ------ MAINVIEW WINDOW INTERFACE (V6.0.00) ----------------
     COMMAND  ===>                                                 SCROLL ===> PAGE
     CURR WIN ===> 1        ALT WIN ===>                                           
     >W1 =SKTTRACE==========TCPIP====*========26OCT2009==09:12:43====MVIP=====D====1
     Command Trace      Userid   Nbr   Job      Dest             Source Dest  Local/
     ------- Status     Started  Recs  Name     IPAddr           Port   Port  GMT  
             NOT ACTIVE              0                                        LOCAL

  2. To trace all packets, type STASKT or START in the Command field, and press Enter.

    Tip

    You can also type IP address, source port, and destination port filters in this window to limit the parameter of the Trace.

    Note

    A Socket Trace can be started only for a non-active trace.


  3. Press F3 to complete the task.

    Message TACI9309I confirms that the trace has been activated.

  4. Press Enter to return to the SKTTRACE view.ACTIVE is displayed in the Trace Status field.

    Other status types include:

    • ACTIVE to indicate that the socket trace is currently active and tracing.
    • STOPPED to indicate that the socket trace has been stopped.
    • NOT ACTIVE to indicate that the socket trace is not currently active.

    Note

    If the status type is NOT ACTIVE, press Enter to refresh the panel.

For more information, see the MainView Customization Reference.

This section includes the following topics:

 

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