Starting Traces
Packet Tracing
You can start a Packet Trace for a specific IP address, source port, destination port, protocol type, and packet length.
You can also start a Packet Trace by usingAlarm Managementon 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 theBMC AMI Ops for Networkssolution and aBMC AMI Ops AutomationRule.
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
From the EZIP menu, select Packet Tracing from the Diagnostics section, and press Enter.The Packet Trace view (PKTTRACE) is displayed:
02NOV2022 12:28:15 --------------------------------------------- BMC AMI Ops WINDOW INTERFACE (V7.0.00) -------------------------------------------------
COMMAND ===> SCROLL ===>
CURR WIN ===> 1 ALT WIN ===>
>W1 =PKTTRACE==========TCPIP====*========02NOV2022==12:28:15====MVIP=====D====6===========================================================================
Command Stack Trace Userid Nbr Prot IP Port Payload Log Trace Local/ Start Date Start Time Stop Date Stop Time Auto
------- Name Status Started Recs Type Address Nbr Length Hdr ID GMT mm/dd/yy hh:mm:ss.xxxx mm/dd/yy hh:mm:ss.xxxx Start
TCPIP ACTIVE ROHMCB3 279 23 NO LOCAL 11/02/22 12:27:23.5222 YES
TCPIP ACTIVE ROHMCB3 0 172.21.41.5 NO LOCAL 11/02/22 12:28:04.5619 NO
TCPIP NOT ACTIVE 0 NO LOCAL NO
TCPIP STOP/LIMIT ROHMCB3 101 NO LOCAL 11/02/22 12:27:35.3041 11/02/22 12:27:49.2578 NO
TCPIP STOP/SHUTD ROHMCB3 0 1.2.3.4/8 NO LOCAL 11/01/22 07:06:47.3900 11/01/22 07:12:59.8583 NO
TCPIP STOP/SHUTD ROHMCB3 0 1.2.3.4/32 NO LOCAL 11/01/22 07:13:20.8167- To trace packets, type STA, PKT, or STARTALL (to start all the packet traces) in the Command field and press Enter.
(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 associate 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 after which the active trace is stopped (hh:mm:ss)
Start Time
Specifies the time when the packet trace should start
Auto Start
Specifies whether the packet trace should start automatically each time the PAS is started
Specify one of the following options:
- Yes—Start the packet trace when the PAS starts.
- YesClr—Clear the packet trace entries of the selected trace.
- (default) No—Packet trace does not start automatically when the PAS starts.
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
(BMC.AMIOPS.SPE2301) You can specify multiple ports when you are also specifying an IP address.
IP Addr/Host Name
Specifies up to four IP addresses or hostnames
You can use a wildcard for any of the octets in an IPv4 address, except for the first octet.
Interface name
Specifies the name of the network interface
Discard Code
Specifies the Break up
Wrap Trace
Specifies whether the trace wraps when the end of the trace table is reached.
The default value is the contents of the Pkttrace Wrap field on MVIPCNFD view.
- Press F3 to complete the task.
- (Optional) To trace encrypted packets, type YES in the IPSec Data field.
Data Tracing
You can start a Data Trace 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
From the EZIP menu, select Data Tracing from the Diagnostics section, and press Enter.The Data Trace view (DATTRACE) is displayed:
06NOV2020 ------------------------------------------------- BMC AMI Ops WINDOW INTERFACE (V7.0.00) -----------------------------------------------------------
CURR WIN ===> 1 ALT WIN ===>
>W1 =DATTRACE==========TCPIP====*========06NOV2020==05:27:22====MVIP=====D====6================================================================================
Command Stack Trace Userid Nbr IP Port Data Trace Local/ Start Date Start Time Stop Date Stop Time Time Limit User
------- Name Status Started Recs Address Nbr Len ID GMT mm/dd/yy hh:mm:ss.xxxx mm/dd/yy hh:mm:ss.xxxx hh:mm:ss StartTime
TCPIP ACTIVE ROHMCB3 354 23 128 TELNET LOCAL 11/06/20 05:25:02.6389
TCPIP ACTIVE ROHMCB3 243 LOCAL 11/06/20 05:25:18.7144
TCPIP NOT ACTIVE 0 LOCAL
TCPIP STOP/TIME ROHMCB3 191 172.28.21.73 LOCAL 11/06/20 05:26:51.5357 11/06/20 05:27:21.5355 00:00:30
TCPIP STOPPED MVSYDD 834 LOCAL 11/05/20 07:23:11.9653 11/05/20 07:23:16.5387
TCPIP STOPPED ROHMCB3 163 23 TELNET LOCAL 11/06/20 05:24:21.6620 11/06/20 05:25:37.5725- To start Data Tracing, type STA, DAT or STARTALL (to start all the Data Traces) in the Command field, and press Enter.
(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
- Press F3 to complete the task.
- (Optional) To trace encrypted packets, type YES in the ATTLS Data field.
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 collect.
To start an OSA Trace
From the EZIP menu, select OSA Tracing from the Diagnostics section, and press Enter.The OSA Trace view (OSATRACE) is displayed:
06NOV2020 ------------------------------------------------- BMC AMI Ops WINDOW INTERFACE (V7.0.00) -----------------------------------------------------------
CURR WIN ===> 1 ALT WIN ===>
>W1 =OSATRACE==========TCPIP====*========06NOV2020==05:28:18====MVIP=====D====3================================================================================
Command Stack Trace Userid Nbr Port IP Port Trace Local/ Start Date Start Time Stop Date Stop Time User MAC
------- Name Status Started Recs Name Address Nbr ID GMT mm/dd/yy hh:mm:ss.xxxx mm/dd/yy hh:mm:ss.xxxx StartTime Address
TCPIP ACTIVE ROHMCB3 84 GIGPF7 23 LOCAL 11/06/20 05:28:08.0419
TCPIP NOT ACTIVE 0 LOCAL
TCPIP STOP/LIMIT MVSYDD 100 GIGPF7 23 LOCAL 11/05/20 07:24:13.8726- To trace frames (packets), type STA in the Command field, and press Enter.
Insert the port name.
The port name specifies which OSA port needs tracing.(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
- Press F3 to complete the task.
Socket Tracing
You can start a Socket Trace 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. You can view the The Socket Trace through the display command. Only one Socket Trace can be active per stack at a time.
Use the following procedure to start a Socket Trace:
To start a Socket Trace
From the EZIP menu select Socket Tracing from the Diagnostics section, and press Enter.The Socket Tracing view (SKTTRACE) is displayed:
26OCT2009 09:12:43 ------ BMC AMI Ops WINDOWS INTERFACE (Vv.r.mm) --------------
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 LOCALTo trace all packets, type
STA, SKT or START in the Command field, and press Enter.
Press F3 to complete the task.
Message TACI9309I confirms that the trace has been activated.
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.
For more information, see Customizing after installation.