UDP Trace Definitions
The following fields may require explanation when you create a UDP trace definition:
cnnmiht
The following fields may require explanation when you create a UDP trace definition:
Base Criteria
TCP/IP Stack:
Limits the trace to the specified stack. Not selecting a stack creates a separate trace for each active stack that matches the criteria for this definition.
Interface:
(Applies only if you specify TCP/IP Stack) The logical name for the physical link or adapter that the TCP/IP stack uses to route an IP packet.
Local Host and
Foreign Host
:Local Host
– The IP host address of the local TCP/IP stack, in one of these formats:IPv4:
- Host name
- Dotted decimal notation
- Network notation: an address mask or a prefix length, for example, 192.168/255.128 or 192.168/9
- Generic IP address notation, for example, 192.*
IPv6:
- Host name
- Address notation (for details, see RFC, IP Version 6 Addressing Architecture)
- Network notation, for example, 2001:DB8::/32
- Generic IP address notation, for example, 2001:*
Foreign Host
– The IP host address of the foreign (remote) TCP/IP stack. This address is typically not associated with a local TCP/IP stack. An exception is when an IP packet uses a LOOPBACK interface or a secondary interface from the same local stack. Use one of these formats:IPv4:
- The IPv4 dotted decimal notation
- An IPv4 network notation, which can be an address mask or a prefix length, for example, 192.168/255.128 or 192.168/9
- A generic IP address notation, for example, 192.*
- A host name that is resolved to an IPv4 dotted decimal notation
IPv6:
- The IPv6 address notation, as described in the RFC, IP Version 6 Addressing Architecture
- An IPv6 network notation, for example, 2001:DB8::/32
- A generic IP address notation, for example, 2001:*
- A host name that is resolved to an IPv6 address notation
Local Port and
Foreign Port:
One or more of the following values, separated by commas:
- A whole number from 1 to 65535
- A range of ports, for example, 1000-2000
Special Address
One of the following special types of addresses:
- LOOPBACK: 127.0.0.1 to 127.255.255.255
- MULTICAST: 224.0.0.0 to 239.255.255.255
- BROADCAST (IPv4 Only): limited broadcast (255.255.255.255) or directed broadcast
If you select the Special Address field, do not specify a value in the Local Host and Foreign Host fields.
Advanced Criteria
Packet Direction
Specifies whether to test for inbound or outbound packets:
- In – Inbound packets
- Out – Outbound packets
- Omit - Skips the test
The
direction
is the directional flow of an IP packet relative to the TCP/IP stack. An inbound packet typically has a local host address as its destination. An outbound packet typically has a foreign host address as its destination. One exception occurs: an outbound packet has a local address for its destination when the packet uses a LOOPBACK interface or uses a secondary interface from the same stack. Checksum
Tests the value of the checksum field.
- Yes - Contains a non-zero value
- No - Carries all zeroes
- Omit - Skips this test
Data
Express
ionCombines all expressions into one expression using Boolean operators.
UDP Data Length
The length in bytes of the data after the UDP Header.
Select an operator and specify a value between 0 and 65507.
Operator
The relational operator for comparing packet data with test data. The Like operator is not valid for Hex, IPv4, or IPv6.
Data
The test data to compare to the packet data.
For the LIKE operator, specify at least one of these wildcard characters: asterisk * (matches zero or any number of characters) or question mark ? (matches any character).
Format
Character format of the test data. Default: EBCDIC.
Hex format requires the test data to end on a byte boundary: For example, 12AED6 is valid, while 12AED is not.
If you specify the length for the = or != operators, specify half the display length of the Hex data. For example, 12AED6 has a length of three.
Start Position
The first position in the packet data to begin the comparison.
Default:
1Max:
128Length
Length of the packet data to compare to the test data.
For a LIKE operator, this field is required; the minimum value is the length of the LIKE data pattern.
For the = and != operators, it is optional but when specified, must match the length of the test data.
The length includes the starting position.
Max:
32 and
cannot exceed the range of comparison of 128 bytes. For example, a starting position of 120 and a length of 30 is invalid.Stop Criteria
Packet Direction
Specifies whether to test for inbound or outbound packets:
- In – Inbound packets
- Out – Outbound packets
- Omit - Skips the test
The
direction
is the directional flow of an IP packet relative to the TCP/IP stack. An inbound packet typically has a local host address as its destination. An outbound packet typically has a foreign host address as its destination. One exception occurs: an outbound packet has a local address for its destination when the packet uses a LOOPBACK interface or uses a secondary interface from the same stack. Checksum
Tests the value of the checksum field.
- Yes - Contains a non-zero value
- No - Carries all zeroes
- Omit - Skips this test
Data
Express
ionCombines all expressions into one expression using Boolean operators.
Default:
Combine all expressions using OR operators.UDP Data Length
The length in bytes of the data after the UDP Header.
Select an operator and specify a value between 0 and 65507.
Operator
The relational operator for comparing packet data with test data. The Like operator is not valid for Hex, IPv4, or IPv6.
Data
The test data to compare to the packet data.
For the LIKE operator, specify at least one of these wildcard characters: asterisk * (matches zero or any number of characters) or question mark ? (matches any character).
Format
Character format of the test data. Default: EBCDIC.
Hex format requires the test data to end on a byte boundary: For example, 12AED6 is valid, while 12AED is not.
If you specify the length for the = or != operators, specify half the display length of the Hex data. For example, 12AED6 has a length of three.
Start Position
The first position in the packet data to begin the comparison.
Default:
1Max:
128Length
Length of the packet data to compare to the test data.
For a LIKE operator, this field is required; the minimum value is the length of the LIKE data pattern.
For the = and != operators, it is optional but when specified, must match the length of the test data.
The length includes the starting position.
Max: 32
and
cannot exceed the range of comparison of 128 bytes. For example, a starting position of 120 and a length of 30 is invalid.Tracing Options
Trace Limit
Limits the number of packets kept for a trace.
Values:
10 through the value of the PAMMTTSIZE Packet Analyzer parameter in SOLVE SSI
.Default:
250 If you increase this value, increase the size of the IPFILE. Also, expand the trace database by increasing the value of the PTRCDBSIZE Packet Analyzer parameter in the SOLVE SSI parameter member and restarting
SOLVE SSI
.Trace Expiry
The amount of time (hhh:mm) to store a trace in memory before discarding it.
Range:
0:01 through the value of the PAMFZKPTIME Packet Analyzer parameter in SOLVE SSI
.Stop at Trace Limit:
Selected - Ends the trace when the number of packets collected reaches the number in the Trace Limit option.
Cleared - Continues collection after the limit is reached and discards the oldest packets to free space for new ones.
Packets After Stop
The extra packets to collect before the trace is stopped. After the stop condition is met, the trace continues until the number of packets that you specify in Packets After Stop is reached. The valid range is 0-999 but must be less than the Trace Limit value.
This field applies only when you specify one or more stop criteria for the trace definition.
Example
You specify the following values:
- Trace Limit=100
- Packets After Stop=50
The finished trace file contains between 51 and 100 depending on when you hit the stop condition.
- If you hit the stop condition on packet 1, the trace continues to collect until packet 51 arrives.
- If you hit the stop condition on packet 50, the trace continues to collect until packet 100 arrives.
- If you hit the stop condition on packet 1000 (you did not select Stop at Limit), the trace continue to collect until packet 1050 arrives. However, because the trace limit is 100, you see only packets 950 to 1050.