Netstat DEvlinks/-d report
Displays information about interfaces that are defined to the TCP/IP stack.
TSO syntax
Modifier
- PNETID=pnetid
- Displays information about interfaces for the specified physical network ID (pnetid). If an asterisk (*) is specified for the PNETID value, all interfaces with a PNETID value are displayed. If the value NONE is specified for the PNETID value, all interfaces without a PNETID are displayed. This modifier is mutually exclusive with the SMC modifier.
- SMC
- Displays only Shared Memory Communications (SMC) information.
- For Shared Memory Communications over Remote Direct Memory Access (SMC-R), the information is about "RoCE Express®" interfaces and their associated SMC-R link groups and SMC-R links.
- For Shared Memory Communications - Direct Memory Access (SMC-D), the information is about Internal Shared Memory (ISM) interfaces and their associated SMC-D links, and unassociated SMC-Dv2 links.
This modifier is mutually exclusive with the PNETID modifier.
Tip: If the INTFName/-K filter is specified with the SMC modifier, the SMC-R link group information is not displayed.
Target
Provide the report for a specific TCP/IP address space by using TCp tcpname. See The Netstat command target for more information about the TCp parameter.
Output
The default output option displays the output on the user's terminal. For other options, see The TSO NETSTAT command syntax or Netstat command output.
Filter
z/OS UNIX syntax
Modifier
- PNETID=pnetid
- Displays information about interfaces for the specified physical network ID (pnetid). If an asterisk (*) is specified for the PNETID value, all interfaces with a PNETID value are displayed. If the value NONE is specified for the PNETID value, all interfaces without a PNETID are displayed. This modifier is mutually exclusive with the SMC modifier.
- SMC
- Provide only Shared Memory Communications (SMC) information.
- For Shared Memory Communications over Remote Direct Memory Access (SMC-R), the information is about "RoCE Express" interfaces and their associated SMC-R link groups and SMC-R links.
- For Shared Memory Communications - Direct Memory Access (SMC-D), the information is about Internal Shared Memory (ISM) interfaces and their associated SMC-D links, and unassociated SMC-Dv2 links.
This modifier is mutually exclusive with the PNETID modifier.
Tip: If the INTFName/-K filter is specified with the SMC modifier, the SMC-R link group information is not displayed.
Target
Provide the report for a specific TCP/IP address space by using -p tcpname. See The Netstat command target for more information about the TCp parameter.
Output
The default output option displays the output to z/OS® UNIX shell stdout. For other options, see The z/OS UNIX netstat command syntax or Netstat command output.
Filter
Filter description
- INTFName/-K intfname
- Filter the output of the DEvlinks/-d report using the specified interface name intfname. You can enter one filter value at a time and the specified
value can be up to 16 characters in length. The INTFName/-K filter value intfname can be one of the following values:
- The network interface name that was displayed in the LnkName/LinkName or INTFName field in the report (this option selects one interface).
- The interface name of an OSAENTA trace interface, which is EZANTAportname, where the portname value is the name that is specified on the PORTNAME keyword in the TRLE for the OSA-Express port that is being traced (this option selects one interface).
- The port name of an OSA-Express feature in QDIO mode, where the port name is the name that is specified on the PORTNAME keyword in the TRLE (this option selects all interfaces that are associated with the OSA-Express port, including an OSAENTA trace interface).
- The name of a HiperSockets TRLE. This option selects all interfaces that are associated with the HiperSockets TRLE.
Restriction:- The INTFName/-K filter value does not support wildcard characters.
- The INTFName/-K filter value does not display information for a device that does not have a link defined.
- The INTFName/-K filter is not supported for the report if the PNETID modifier is specified.
- SMCID/-U smcid
- Filter the output of the DEvlinks/-d report by using the specified Shared Memory Communications
over Remote Direct Memory Access (SMC-R) link, SMC-R link group, or Shared Memory Communications - Direct Memory Access
(SMC-D) link identifier
smcid. You can enter one filter value at a time.
- If the filter value is an SMC-R link ID, then the report shows details about that SMC-R link and information about the SMC-R link group to which that link belongs.
- If the filter value is an SMC-R link group ID, then the report shows details about all SMC-R links in the link group and information about the SMC-R link group.
- If the filter value is an SMC-D link ID, then the report shows details about that SMC-D link.
- If the filter value is an asterisk (*), then the report provides the same information that the SMC modifier provides.
Rule: If you specify the SMCID/-U filter on the command, the report is generated as if the SMC modifier was also specified. The report includes detailed information about the SMC-R link or SMC-D link that smcid defines, regardless of whether the SMC modifier was explicitly coded. Using the SMCID/-U filter with the filter value asterisk (*) is equivalent to using the SMC modifier. The SMCID/-U filter is not supported for the report if the PNETID modifier is specified.
Command syntax examples
From TSO environment
NETSTAT DEVLINKS
Displays the information about devices and defined interfaces or links in the default
TCP/IP address space
NETSTAT DEVLINKS TCP TCPCS6
Displays the information about devices and defined interfaces or links in the TCPCS6
TCP/IP address space.
NETSTAT DEVLINKS SMC
Displays additional SMC-D information about ISM interfaces, and SMC-R information about
RNIC interfaces.
NETSTAT DEVLINKS PNETID NETID1
Displays the information about interfaces with a PNETID value of NETID1.
NETSTAT DEVLINKS TCP TCPCS8 (INTFNAME OSAQDIOLINK
Display the information for the OSAQDIOLINK in the TCPCS8 TCP/IP adress space.
From UNIX shell environment
netstat -d
netstat -d -p tcpcs6
netstat -d SMC
netstat -d PNETID NETID1
netstat -d -p tcpcs8 -K OSAQDIOLINK
Report examples
The following examples are generated by using TSO NETSTAT command. Using the z/OS UNIX netstat command displays the data in the same format as the TSO NETSTAT command.
Not IPv6 enabled (SHORT format)
NETSTAT DEVLINKS MVS TCP/IP NETSTAT CS V2R4 TCPIP Name: TCPCS 14:23:39
DevName: LOOPBACK DevType: LOOPBACK
DevStatus: Ready
LnkName: LOOPBACK LnkType: LOOPBACK LnkStatus: Ready
ActMtu: 65535
Routing Parameters:
MTU Size: n/a Metric: 00
DestAddr: 0.0.0.0 SubnetMask: 0.0.0.0
Multicast Specific:
Multicast Capability: No
Link Statistics:
BytesIn = 24943
Inbound Packets = 100
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 24943
Outbound Packets = 100
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
DevName: LCS1 DevType: LCS DevNum: 0D00
DevStatus: Ready
LnkName: TR1 LnkType: TR LnkStatus: Ready
NetNum: 0 QueSize: 0
MacAddrOrder: Non-Canonical SrBridgingCapability: Yes
IpBroadcastCapability: Yes ArpBroadcastType: All Rings
MacAddress: 08005A0D97A2
ActMtu: 1492
SecClass: 8 MonSysplex: Yes
Routing Parameters:
MTU Size: 02000 Metric: 100
DestAddr: 0.0.0.0 SubnetMask: 255.255.255.128
Packet Trace Setting:
Protocol: * TrRecCnt: 00000006 PckLength: FULL
Discard : NONE
SrcPort: * DestPort: * PortNum: *
IpAddr: * SubNet: *
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Include
SrcAddr: 9.1.1.1
9.1.1.2
9.1.1.3
224.9.9.3 0000000001 Include
SrcAddr: 9.1.1.1
224.9.9.4 0000000001 Exclude
SrcAddr: 9.2.2.1
9.2.2.2
225.9.9.4 0000000003 Exclude
SrcAddr: None
Link Statistics:
BytesIn = 9130
Inbound Packets = 2
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 60392
Outbound Packets = 11
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
DevName: OSAQDIO4 DevType: MPCIPA
DevStatus: Ready CfgRouter: Non ActRouter: Non
LnkName: OSAQDIOLINK LnkType: IPAQENET LnkStatus: Ready
Speed: 0000000100
IpBroadcastCapability: No
VMACAddr: 000629DC21BC VMACOrigin: Cfg VMACRouter: All
ArpOffload: Yes ArpOffloadInfo: Yes
ActMtu: 1492
VLANid: 1260 VLANpriority: Enabled
DynVLANRegCfg: Yes DynVLANRegCap: No
ReadStorage: GLOBAL (8064K) InbPerf: Balanced
ReadStorage: GLOBAL (8064K)
InbPerf: Balanced
ChecksumOffload: Yes SegmentationOffload: Yes
SecClass: 8 MonSysplex: Yes
Routing Parameters:
MTU Size: n/a Metric: 00
DestAddr: 0.0.0.0 SubnetMask: 255.255.255.192
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Exclude
SrcAddr: None
Link Statistics:
BytesIn = 11476
Inbound Packets = 10
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 6707
Outbound Packets = 10
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
DevName: OSATRL90 DevType: ATM
DevStatus: Not Active
LnkName: OSA90LINK1 LnkType: ATM LnkStatus: Not Active
ActMtu: Unknown
SecClass: 8 MonSysplex: Yes
Routing Parameters:
MTU Size: n/a Metric: 00
DestAddr: 0.0.0.0 SubnetMask: 255.0.0.0
ATM Specific:
ATM portName: OSA90
ATM PVC Name: STEPH PVC Status: Not Active
ATM LIS Name: LIS1
SubnetValue: 9.67.1.0 SubnetMask: 255.255.255.0
DefaultMTU: 0000009180 InactvTimeOut: 0000000300
MinHoldTime: 0000000060 MaxCalls: 0000001000
CachEntryAge: 0000000900 ATMArpReTry: 0000000002
ATMArpTimeOut: 0000000003 PeakCellRate: 0000000000
NumOfSVCs: 0000000000 BearerClass: C
ATMARPSV Name: ARPSV1
VcType: PVC ATMaddrType: NSAP
ATMaddr:
IpAddr: 0.0.0.0
Multicast Specific:
Multicast Capability: No
Link Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
DevName: CLAW2 DevType: CLAW DevNum: 0D10
DevStatus: Ready CfgPacking: Packed ActPacking: Packed
LnkName: CLAW2LINK LnkType: CLAW LnkStatus: Ready
ActMtu: 2600
SecClass: 8 MonSysplex: No
Routing Parameters:
MTU Size: n/a Metric: 00
DestAddr: 0.0.0.0 SubnetMask: 255.255.255.0
Multicast Specific:
Multicast Capability: No
Link Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
DevName: IUTIQDIO DevType: MPCIPA
DevStatus: Ready
LnkName: IQDIOLNK0A3D0001 LnkType: IPAQIDIO LnkStatus: Ready
IpBroadcastCapability: No
CfgRouter: Non ActRouter: Non
ArpOffload: Yes ArpOffloadInfo: No
ActMtu: 8192
ReadStorage: GLOBAL (2048K)
SecClass: 255
IQDMultiWrite: Enabled
Routing Parameters:
MTU Size: 8192 Metric: 00
DestAddr: 0.0.0.0 SubnetMask: 255.255.0.0
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Exclude
SrcAddr: None
Link Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
IntfName: OSAQDIOINTF IntfType: IPAQENET IntfStatus: Ready
PortName: OSAQDIO2 Datapath: 0E2A DatapathStatus: Ready
CHPIDType: OSD SMCR: Yes
PNetID: NETWORK3 SMCD : Yes
TRLE: QDIO101
Speed: 0000000100
IpBroadcastCapability: No
VMACAddr: 020629DC21BD VMACOrigin: Cfg VMACRouter: All
SrcVipaIntf: VIPAV4
CfgRouter: Non ActRouter: Non
ArpOffload: Yes ArpOffloadInfo: Yes
CfgMtu: 1492 ActMtu: 1492
IpAddr: 100.1.1.1/24
VLANid: 1261 VLANpriority: Enabled
DynVLANRegCfg: Yes DynVLANRegCap: No
ReadStorage: GLOBAL (8064K) InbPerf: Balanced
ReadStorage: GLOBAL (8064K)
InbPerf: Dynamic
WorkloadQueueing: Yes
ChecksumOffload: Yes SegmentationOffload: Yes
SecClass: 9 MonSysplex: Yes
Isolate: Yes OptLatencyMode: Yes
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 12834
Inbound Packets = 16
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 5132
Outbound Packets = 10
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
Associated IQD Converged interface: EZAIQCE0 IQC Status: Ready
BytesIn = 8415345
Inbound Packets = 5835
BytesOut = 8414715
Outbound Packets = 5890
Associated RNIC interface: EZARIUT10005
Associated RNIC interface: EZARIUT10006
Associated ISM interface: EZAISM02
Unassociated ISM interfaces: EZAISMU3 EZAISMU4
IntfName: EZAIQCE0 IntfType: IPAQIQDC IntfStatus: Ready
Datapath: 0E0F DatapathStatus: Ready
CHPIDType: IQD CHPID: E0
PNetID: ZOSNET
TRLE: IUTIQCE0
ReadStorage: MAX (2048K)
IQDMultiWrite: Enabled
Multicast Specific:
Multicast Capability: No
Interface Statistics:
BytesIn = 8415633
Inbound Packets = 5838
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 8415387
Outbound Packets = 5897
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
IntfName: IQDINTF1 IntfType: IPAQIDIO IntfStatus: Ready
TRLE: IUTIQ4QD Datapath: 0E2A DatapathStatus: Ready
CHPID: D1
PNetID: PHYSICALNETWORK2 SMCD: Yes
IpBroadcastCapability: No
SrcVipaIntf: VIPAV4
ArpOffload: Yes ArpOffloadInfo: No
CfgMtu: 8192 ActMtu: 8192
IpAddr: 100.1.1.1/24
VLANid: 1261
ReadStorage: GLOBAL (2048K)
SecClass: 255
IQDMultiWrite: Enabled
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
Associated ISM interface: EZAISM01
Unassociated ISM interfaces: EZAISMU2 EZAISMU3
IntfName: VDEV1 IntfType: VIPA IntfStatus: Ready
IpAddr: 100.1.1.1/24
Multicast Specific:
Multicast Capability: No
IntfName: OSXC9INT1 IntfType: IPAQENET IntfStatus: Ready
PortName: IUTXP0C9 Datapath: 0E56 DatapathStatus: Ready
CHPIDType: OSX CHPID: C9
PNetID: IEDN
Speed: 0000001000
IpBroadcastCapability: No
VMACAddr: 420001AA0E56 VMACOrigin: OSA VMACRouter: All
CfgRouter: Non ActRouter: Non
ArpOffload: Yes ArpOffloadInfo: No
CfgMtu: None ActMtu: 8992
IpAddr: 172.16.0.1/16
VLANid: 401 VLANpriority: Disabled
DynVLANRegCfg: No DynVLANRegCap: Yes
ReadStorage: GLOBAL (512K)
InbPerf: Dynamic
WorkloadQueueing: No
ChecksumOffload: No SegmentationOffload: No
SecClass: 255 MonSysplex: No
Isolate: No OptLatencyMode: No
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
Associated IQDX interface: EZAIQXC9 IQDX Status: Ready
BytesIn = 0
Inbound Packets = 0
BytesOut = 0
Outbound Packets = 0
IntfName: EZAIQXC9 IntfType: IPAQIQDX IntfStatus: Ready
Datapath: 0E0E DatapathStatus: Ready
VMACAddr: 820001AA0E0E
ReadStorage: MAX (2048K)
IQDMultiWrite: Disabled
Multicast Specific:
Multicast Capability: No
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
IntfName: EZARIUT10005 IntfType: RNIC IntfStatus: Ready
PFID: 0005 PortNum: 1 TRLE: IUT10005
PNetID: NETWORK3
Speed: 0000010000 Gen: RoCE Express2
VMACAddr: 02000012F030
GIDAddr: fe80::200:ff:fe12:f030
Interface Statistics:
BytesIn = 18994
Inbound Operations = 146
BytesOut = 19139
Outbound Operations = 811
SMC Links = 2
TCP Connections = 1
Intf Receive Buffer Inuse = 64K
IntfName: EZARIUT10006 IntfType: RNIC IntfStatus: Ready
PFID: 0006 PortNum: 1 TRLE: IUT10006
PNetID: NETWORK3
Speed: 0000010000 Gen: RoCE Express2
VMACAddr: 02000012EF50
GIDAddr: fe80::200:ff:fe12:ef50
Interface Statistics:
BytesIn = 226
Inbound Operations = 4
BytesOut = 29
Outbound Operations = 4
SMC Links = 2
TCP Connections = 1
Intf Receive Buffer Inuse = 64K
IntfName: EZAISM01 IntfType: ISM IntfStatus: Ready
PFID: 0061 TRLE: IUT00061 PFIDStatues: Ready
PNetID: PHYSICALNETWORK2
GIDAddr: 8002000900090061
Interface Statistics:
BytesIn = 0
Inbound Operations = 0
BytesOut = 0
Outbound Operations = 0
SMC Links = 0
TCP Connections = 0
Intf Receive Buffer Inuse = 0K
Device Interrupts = 0
IPv4 LAN Group Summary
LanGroup: 001
Name Status ArpOwner VipaOwner
------- ------ -------- ---------
OSXC9INT1 Active OSXC9INT1 Yes
TR1 Active TR1 No
LanGroup: 002
Name Status ArpOwner VipaOwner
------- ------ -------- ---------
OSAQDIOLINK Active OSAQDIOLINK Yes
OSAQDIOINTF Active OSAQDIOINTF No
Netstat DEvlinks/-d PNETID *
MVS TCP/IP NETSTAT CS V2R4 TCPIP Name: TCPCS1 12:17:36
PNetID: PHYSICALNETWORK2
IntfName: IQDIOLNK0A3D0001 IntfType: IPAQIDIO
IntfName: EZAISM01 IntfType: ISM Associated: Yes
PNetID: NETID1
IntfName: QDIO4SHRL IntfType: IPAQENET
IntfName: EZAISM02 IntfType: ISM Associated: Yes
IntfName: EZARIUT1A003 IntfType: RNIC Associated: Yes
IntfName: EZARIUT1A004 IntfType: RNIC Associated: Yes
IntfName: EZAIQCE0 IntfType: IPAQIQDC Associated: Yes
Netstat DEvlinks/-d PNETID NETID1
MVS TCP/IP NETSTAT CS V2R4 TCPIP Name: TCPCS1 12:29:32
IntfName: QDIO4SHRL IntfType: IPAQENET
TRLE: QDIO001 CHPID: C7 PChid: 01C7 CHPIDType: OSD
PortName: QDIO4SHR SMCR: Yes
Datapath: 0E42 VLANid: None SMCD: Yes
VMACAddr: 420002AA0E2A
IntfName: EZAISM02 IntfType: ISM Associated: Yes
TRLE: IUT00051 PFID: 0051 VChid: 2300
GIDAddr: 8002000100010051
IntfName: EZARIUT1A004 IntfType: RNIC Associated: Yes
TRLE: IUT1A004 PFID: A004 PChid: 0120 PortNum: 1
VMACAddr: D4C1C301A004
GIDAddr: fe80::d4c1:c301:a004
IntfName: EZARIUT1A003 IntfType: RNIC Associated: Yes
TRLE: IUT1A003 PFID: A003 PChid: 0118 PortNum: 1
VMACAddr: D4C1C301A003
GIDAddr: fe80::d4c1:c301:a003
IntfName: EZAIQCE0 IntfType: IPAQIQDC Associated: Yes
TRLE: IUTIQCE0 CHPID: E0 VChid: 010C
Datapath: 0E0F
IPv6 enabled or request for LONG format
NETSTAT DEVLINKS
MVS TCP/IP NETSTAT CS V2R4 TCPIP Name: TCPCS 14:23:39
DevName: LOOPBACK DevType: LOOPBACK
DevStatus: Ready
LnkName: LOOPBACK LnkType: LOOPBACK LnkStatus: Ready
ActMtu: 65535
Routing Parameters:
MTU Size: n/a Metric: 00
DestAddr: 0.0.0.0 SubnetMask: 0.0.0.0
Multicast Specific:
Multicast Capability: No
Link Statistics:
BytesIn = 7665
Inbound Packets = 100
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 7665
Outbound Packets = 100
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
IntfName: LOOPBACK6 IntfType: LOOPBACK6 IntfStatus: Ready
ActMtu: 65535
Multicast Specific:
Multicast Capability: No
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
DevName: LCS1 DevType: LCS DevNum: 0D00
DevStatus: Ready
LnkName: TR1 LnkType: TR LnkStatus: Ready
NetNum: 0 QueSize: 0
MacAddrOrder: Non-Canonical SrBridgingCapability: Yes
IpBroadcastCapability: Yes ArpBroadcastType: All Rings
MacAddress: 08005A0D97A2
ActMtu: 1492
SecClass: 8 MonSysplex: Yes
Routing Parameters:
MTU Size: 02000 Metric: 100
DestAddr: 0.0.0.0 SubnetMask: 255.255.255.128
Packet Trace Setting:
Protocol: * TrRecCnt: 00000006 PckLength: FULL
Discard : NONE
SrcPort: * DestPort: * PortNum: *
IpAddr: * SubNet: *
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.9.9.1 0000000002 Include
SrcAddr: 9.1.1.1
9.1.1.2
9.1.1.3
224.9.9.3 0000000001 Include
SrcAddr: 9.1.1.1
224.9.9.4 0000000001 Exclude
SrcAddr: 9.2.2.1
9.2.2.2
225.9.9.4 0000000003 Exclude
SrcAddr: None
Link Statistics:
BytesIn = 9130
Inbound Packets = 2
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 60392
Outbound Packets = 11
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
DevName: OSAQDIO4 DevType: MPCIPA
DevStatus: Ready
LnkName: OSAQDIOLINK LnkType: IPAQENET LnkStatus: Ready
Speed: 0000000100
IpBroadcastCapability: No
VMACAddr: 000629DC21BC VMACOrigin: Cfg VMACRouter: All
CfgRouter: Non ActRouter: Non
ArpOffload: Yes ArpOffloadInfo: Yes
ActMtu: 1492
VLANid: 1260 VLANpriority: Enabled
DynVLANRegCfg: Yes DynVLANRegCap: No
ReadStorage: GLOBAL (8064K) InbPerf: Balanced
ReadStorage: GLOBAL (8064K)
InbPerf: Balanced
ChecksumOffload: Yes SegmentationOffload: Yes
SecClass: 8 MonSysplex: Yes
Routing Parameters:
MTU Size: n/a Metric: 00
DestAddr: 0.0.0.0 SubnetMask: 255.255.255.192
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Exclude
SrcAddr: None
Link Statistics:
BytesIn = 11476
Inbound Packets = 10
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 6707
Outbound Packets = 10
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
IntfName: OSAQDIO46 IntfType: IPAQENET6 IntfStatus: Ready
PortName: OSAQDIO4 Datapath: 0E2B DatapathStatus: Ready
CHPIDType: OSD SMCR: Yes
PNetID: NETWORK3 SMCD : Yes
TRLE: QDIO101
QueSize: 0 Speed: 0000000100
VMACAddr: 000629DC21BC VMACOrigin: Cfg VMACRouter: All
SrcVipaIntf: VIPAV6
DupAddrDet: 1
CfgRouter: Pri ActRouter: Pri
RtrHopLimit: 5
CfgMtu: 4096 ActMtu: 1492
VLANid: 1261 VLANpriority: Enabled
DynVLANRegCfg: Yes DynVLANRegCap: No
IntfID: 0000:0000:0000:0001
ReadStorage: GLOBAL (8064K)
InbPerf: Balanced
ChecksumOffload: Yes SegmentationOffload: Yes
SecClass: 8 MonSysplex: Yes
Isolate: Yes OptLatencyMode: Yes
TempPrefix: 2001:0db8:3454:a3cf::/64
2001:0db8:58cd::/48
Packet Trace Setting:
Protocol: * TrRecCnt: 00000000 PckLength: FULL
SrcPort: * DestPort: *
IpAddr/PrefixLen: 9::44/128
Multicast Specific:
Multicast Capability: Yes
Group: ff02::1:ff15:5
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: 2e00::11
2e00::22
Group: ff02::1:ffdc:217c
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff00:2
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 12655
Inbound Packets = 12
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 4590
Outbound Packets = 11
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
Associated IQD Converged interface: EZ6IQCE0 IQC Status: Ready
BytesIn = 8538421
Inbound Packets = 5949
BytesOut = 8536271
Outbound Packets = 5937
Associated RNIC interface: EZARIUT10005
Associated RNIC interface: EZARIUT10006
IntfName: EZ6IQCE0 IntfType: IPAQIQDC6 IntfStatus: Ready
Datapath: 0E19 DatapathStatus: Ready
CHPIDType: IQD CHPID: E0
PNetID: ZOSNET
TRLE: IUTIC6E0
ReadStorage: MAX (2048K)
IQDMultiWrite: Enabled
Multicast Specific:
Multicast Capability: ND only
Group: ff02::1:ff02:1
RefCnt: 0000000002 SrcFltMd: Exclude
SrcAddr: None
Group: ff01::1
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff01:1
RefCnt: 0000000012 SrcFltMd: Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 8538421
Inbound Packets = 5951
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 8536637
Outbound Packets = 5940
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
IntfName: V6SAMEH IntfType: MPCPTP6 IntfStatus: Not Active
TRLE: IUTSAMEH DevStatus: Not Active
SrcVipaIntf: VIPAV6
ActMtu: Unknown
IntfID: 0000:0000:0000:0001
SecClass: 8
Multicast Specific:
Multicast Capability: No
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
IntfName: VIPAV6 IntfType: VIPA6 IntfStatus: Ready
Packet Trace Setting:
Protocol: * TrRecCnt: 00000000 PckLength: FULL
SrcPort: * DestPort: * PortNum: *
IpAddr: * SubNet: *
Multicast Specific:
Multicast Capability: No
IntfName: SZQIDIO6 IntfType: IPAQIDIO6 IntfStatus: Not Active
TRLE: IUTIQDD1 Datapath: 0E3A DatapathStatus: Not Active
CHPID: D1
PNetID: PHYSICALNETWORK2 SMCD: Yes
ActMtu: Unknown
VLANid: 3
SecClass: 044 MonSysplex: No
Multicast Specific:
Multicast Capability: Unknown
Group: ff02::1:ff00:2
RefCnt: 0000000002 SrcFltMd: Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Associated ISM interface: EZAISM01
IntfName: OSAQDIOINTF IntfType: IPAQENET IntfStatus: Ready
PortName: OSAQDIO2 Datapath: 0E2A DatapathStatus: Ready
CHPIDType: OSD SMCR: Yes
PNetID: ZOSNET SMCD: Yes
Speed: 0000000100
IpBroadcastCapability: No
VMACAddr: 020629DC21BD VMACOrigin: Cfg VMACRouter: All
SrcVipaIntf: VIPAV4
CfgRouter: Non ActRouter: Non
ArpOffload: Yes ArpOffloadInfo: Yes
CfgMtu: 1492 ActMtu: 1492
IpAddr: 100.1.1.1/24
VLANid: 1261 VLANpriority: Enabled
DynVLANRegCfg: Yes DynVLANRegCap: No
ReadStorage: GLOBAL (8064K)
InbPerf: Balanced
ChecksumOffload: Yes SegmentationOffload: Yes
SecClass: 9 MonSysplex: Yes
Isolate: Yes
Multicast Specific:
Multicast Capability: Yes
Group RefCnt SrcFltMd
----- ------ --------
224.0.0.1 0000000001 Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 12834
Inbound Packets = 16
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 5132
Outbound Packets = 10
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
SMCR Capability: V1
Associated RNIC interface: EZARIUT10005
Associated RNIC interface: EZARIUT10006
Associated ISM interface: EZAISM02
IntfName: OSXC9INT2 IntfType: IPAQENET6 IntfStatus: Ready
PortName: IUTXP0C9 Datapath: 0E56 DatapathStatus: Ready
CHPIDType: OSX CHPID: C9
PNetID: IEDN
QueSize: 0 Speed: 0000001000
VMACAddr: 620001AA0E56 VMACOrigin: OSA VMACRouter: All
DupAddrDet: 1
CfgMtu: None ActMtu: 9000
VLANid: 602 VLANpriority: Disabled
DynVLANRegCfg: No DynVLANRegCap: Yes
ReadStorage: GLOBAL (512K)
InbPerf: Dynamic
WorkloadQueueing: No
ChecksumOffload: No SegmentationOffload: No
SecClass: 255 MonSysplex: No
Isolate: No OptLatencyMode: No
TempPrefix: All
Multicast Specific:
Multicast Capability: Yes
Group: ff02::1:ffaa:e56
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff01::1
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff01:1
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff00:2
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff00:1
RefCnt: 0000000002 SrcFltMd: Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 688
Outbound Packets = 7
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
Associated IQDX interface: EZ6IQXC9 IQDX Status: Ready
BytesIn = 0
Inbound Packets = 0
BytesOut = 0
Outbound Packets = 0
IntfName: EZ6IQXC9 IntfType: IPAQIQDX6 IntfStatus: Ready
Datapath: 0E0E DatapathStatus: Ready
VMACAddr: 820001AA0E0E
ReadStorage: MAX (2048K)
IQDMultiWrite: Disabled
Multicast Specific:
Multicast Capability: ND only
Group: ff02::1:ffaa:e56
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff01:1
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff00:2
RefCnt: 0000000001 SrcFltMd: Exclude
SrcAddr: None
Group: ff02::1:ff00:1
RefCnt: 0000000002 SrcFltMd: Exclude
SrcAddr: None
Interface Statistics:
BytesIn = 0
Inbound Packets = 0
Inbound Packets In Error = 0
Inbound Packets Discarded = 0
Inbound Packets With No Protocol = 0
BytesOut = 0
Outbound Packets = 0
Outbound Packets In Error = 0
Outbound Packets Discarded = 0
IntfName: EZARIUT10005 IntfType: RNIC IntfStatus: Ready
PFID: 0005 PortNum: 1 TRLE: IUT10005 PFIDStatus: Ready
PNetID: NETWORK3
Speed: 0000010000
VMACAddr: 02000012F030
GIDAddr: fe80::200:ff:fe12:f030
Interface Statistics:
BytesIn = 18994
Inbound Operations = 146
BytesOut = 19139
Outbound Operations = 811
SMC Links = 2
TCP Connections = 1
Intf Receive Buffer Inuse = 64K
IntfName: EZARIUT10006 IntfType: RNIC IntfStatus: Ready
PFID: 0006 PortNum: 1 TRLE: IUT10006 PFIDStatus: Ready
PNetID: NETWORK3
Speed: 0000010000
VMACAddr: 02000012EF50
GIDAddr: fe80::200:ff:fe12:ef50
Interface Statistics:
BytesIn = 226
Inbound Operations = 4
BytesOut = 29
Outbound Operations = 4
SMC Links = 2
TCP Connections = 1
Intf Receive Buffer Inuse = 64K
IntfName: EZAISM01 IntfType: ISM IntfStatus: Ready
PFID: 0061 TRLE: IUT00061 PFIDStatues: Ready
PNetID: PHYSICALNETWORK2
GIDAddr: 8002000900090061
Interface Statistics:
BytesIn = 0
Inbound Operations = 0
BytesOut = 0
Outbound Operations = 0
SMC Links = 0
TCP Connections = 0
Intf Receive Buffer Inuse = 0K
Device Interrupts = 0
IPv4 LAN Group Summary
LanGroup: 001
Name Status ArpOwner VipaOwner
------- ------ -------- ---------
TR1 Active TR1 No
LanGroup: 002
Name Status ArpOwner VipaOwner
------- ------ -------- ---------
OSAQDIOLINK Active OSAQDIOLINK Yes
OSAQDIOINTF Active OSAQDIOINTF No
IPv6 LAN Group Summary
LanGroup: 004
Name Status NDOwner VipaOwner
-------- ------ -------- ---------
OSAQDIO46 Active OSAQDIO46 Yes
NETSTAT DEVLINKS SMC
MVS TCP/IP NETSTAT CS V2R4 TCPIP Name: TCPIP1 12:04:57
IntfName: EZAISM01 IntfType: ISM IntfStatus: Ready
PFID: 0061 TRLE: IUT00061 PFIDStatus: Ready
PNetID: PHYSICALNETWORK2
GIDAddr: 8002000900090061
Interface Statistics:
BytesIn = 52
Inbound Operations = 6
BytesOut = 2169
Outbound Operations = 10
SMC Links = 1
TCP Connections = 1
Intf Receive Buffer Inuse = 64K
Device Interrupts = 6
SMCD Link Information:
LocalSMCLinkId: 00000000 RemoteSMCLinkId: 00000000
SMCDVersion: 2
SMCEID: IBM-SYSZ-ISMSEID00000000F3588561
VLANid: None
LocalGID: 8001001100110071
RemoteGID: 8001001200120072
RemoteHostType: Z/OS
RemoteHostName: PRDLPAR1
SMCLinkBytesIn: 52
SMCLinkInOperations: 6
SMCLinkBytesOut: 2169
SMCLinkOutOperations: 10
TCP Connections: 1
Link Receive Buffer Inuse: 64K
IntfName: EZAISM01 IntfType: ISM IntfStatus: Ready
PFID: 0061 TRLE: IUT00061 PFIDStatues: Ready
PNetID: PHYSICALNETWORK2
GIDAddr: 8002000900090061
Interface Statistics:
BytesIn = 0
Inbound Operations = 0
BytesOut = 0
Outbound Operations = 0
SMC Links = 0
TCP Connections = 0
Intf Receive Buffer Inuse = 0K
Device Interrupts = 0
SMCD Link Information:
LocalSMCLinkId: 00000000 RemoteSMCLinkId: 00000000
VLANid: None
LocalGID: 8003000900090061
RemoteGID: 0000000000000000
SMCLinkBytesIn: 0
SMCLinkInOperations: 0
SMCLinkBytesOut: 0
SMCLinkOutOperations: 0
TCP Connections: 0
Link Receive Buffer Inuse: 0K
IntfName: EZARIUT10005 IntfType: RNIC IntfStatus: Ready
PFID: 0005 PortNum: 1 TRLE: IUT10005
PNetID: NETWORK3
VMACAddr: 02000012F030
GIDAddr: fe80::200:ff:fe12:f030
Interface Statistics:
BytesIn = 18994
Inbound Operations = 146
BytesOut = 19139
Outbound Operations = 811
SMC Links = 2
TCP Connections = 1
Intf Receive Buffer Inuse = 64K
SMCR Link Information:
LocalSMCLinkId: FB710601 RemoteSMCLinkId: 72420601
SMCLinkGroupId: FB710600 VLANid: 100 MTU: 1024
LocalGID: fe80::200:ff:fe12:f030
LocalMACAddr: 02000012F030 LocalQP: 00004B
RemoteGID: fe80::200:1ff:fe12:f030
RemoteMACAddr: 02000112F030 RemoteQP: 00004A
SMCLinkBytesIn: 498
SMCLinkInOperations: 12
SMCLinkBytesOut: 294
SMCLinkOutOperations: 13
TCP Connections: 0
Link Receive Buffer Inuse: 0K
64K Buffer Inuse: 0K
SMCR Link Information:
LocalSMCLinkId: FB710701 RemoteSMCLinkId: 72420701
SMCLinkGroupId: FB710700 VLANid: 100 MTU: 4096
LocalGID: fe80::200:ff:fe12:f030
LocalMACAddr: 02000012F030 LocalQP: 00004C
RemoteGID: fe80::200:1ff:fe12:f030
RemoteMACAddr: 02000112F030 RemoteQP: 00004D
SMCLinkBytesIn: 293
SMCLinkInOperations: 8
SMCLinkBytesOut: 490
SMCLinkOutOperations: 15
TCP Connections: 1
Link Receive Buffer Inuse: 64K
64K Buffer Inuse: 64K
IntfName: EZARIUT10006 IntfType: RNIC IntfStatus: Ready
PFID: 0006 PortNum: 1 TRLE: IUT10006
PNetID: NETWORK3
VMACAddr: 02000012EF50
GIDAddr: fe80::200:ff:fe12:ef50
Interface Statistics:
BytesIn = 226
Inbound Operations = 4
BytesOut = 29
Outbound Operations = 4
SMC Links = 2
TCP Connections = 1
Intf Receive Buffer Inuse = 64K
SMCR Link Information:
LocalSMCLinkId: FB710602 RemoteSMCLinkId: 72420602
SMCLinkGroupId: FB710600 VLANid: 100 MTU: 2048
LocalGID: fe80::200:ff:fe12:ef50
LocalMACAddr: 02000012EF50 LocalQP: 00004A
RemoteGID: fe80::200:1ff:fe12:ef50
RemoteMACAddr: 02000112EF50 RemoteQP: 00004B
SMCLinkBytesIn: 226
SMCLinkInOperations: 5
SMCLinkBytesOut: 29
SMCLinkOutOperations: 4
TCP Connections: 1
Link Receive Buffer Inuse: 64K
64K Buffer Inuse: 64K
SMCR Link Information:
LocalSMCLinkId: FB710702 RemoteSMCLinkId: 72420702
SMCLinkGroupId: FB710700 VLANid: 100 MTU: 1024
LocalGID: fe80::200:ff:fe12:ef50
LocalMACAddr: 02000012EF50 LocalQP: 00004D
RemoteGID: fe80::200:1ff:fe12:ef50
RemoteMACAddr: 02000112EF50 RemoteQP: 00004C
SMCLinkBytesIn: 0
SMCLinkInOperations: 0
SMCLinkBytesOut: 0
SMCLinkOutOperations: 0
TCP Connections: 0
Link Receive Buffer Inuse: 0K
64K Buffer Inuse: 0K
SMCR Link Group Information:
SMCLinkGroupId: FB710600 PNetID: NETWORK3
Redundancy: Full
Link Group Receive Buffer Total: 3M
64K Buffer Total: 1M
LocalSMCLinkId RemoteSMCLinkId
-------------- ---------------
FB710601 72420601
FB710602 72420602
SMCLinkGroupId: FB710700 PNetID: NETWORK3
Redundancy: Full
Link Group Receive Buffer Total: 3M
64K Buffer Total: 1M
LocalSMCLinkId RemoteSMCLinkId
-------------- ---------------
FB710701 72420701
FB710702 72420702
Netstat DEvlinks/-d PNETID *
MVS TCP/IP NETSTAT CS V2R4 TCPIP Name: TCPCS1 12:17:36
PNetID: PHYSICALNETWORK2
IntfName: IQDIOLNK0A3D0001 IntfType: IPAQIDIO
IntfName: IQDIOINTF6 IntfType: IPAQIDIO6
IntfName: EZAISM01 IntfType: ISM Associated: Yes
PNetID: NETID1
IntfName: QDIO4SHRL IntfType: IPAQENET
IntfName: QDIO6SHR IntfType: IPAQENET6
IntfName: EZAISM02 IntfType: ISM Associated: Yes
IntfName: EZARIUT1A003 IntfType: RNIC Associated: Yes
IntfName: EZARIUT1A004 IntfType: RNIC Associated: Yes
IntfName: EZAIQCE0 IntfType: IPAQIQDC Associated: Yes
IntfName: EZ6IQCE0 IntfType: IPAQIQDC6 Associated: Yes
PNetID: PHYSICALNETWORK2
IntfName: IQDIOLNK0A3D0001 IntfType: IPAQIDIO
IntfName: IQDIOINTF6 IntfType: IPAQIDIO6
IntfName: EZAISM01 IntfType: ISM Associated: Yes
PNetID: NETID1
IntfName: QDIO4SHRL IntfType: IPAQENET
IntfName: QDIO6SHR IntfType: IPAQENET6
IntfName: EZAISM02 IntfType: ISM Associated: Yes
IntfName: EZARIUT1A003 IntfType: RNIC Associated: Yes
IntfName: EZARIUT1A004 IntfType: RNIC Associated: Yes
Netstat DEvlinks/-d PNETID PHYSICALNETWORK2
MVS TCP/IP NETSTAT CS V2R4 TCPIP Name: TCPCS1 12:31:45
IntfName: IQDIOLNK0A3D0001 IntfType: IPAQIDIO
TRLE: IUTIQDIO CHPID: FE VChid: 0000
Datapath: 0E02 SMCD: Yes
VMACAddr: 420002AA0E2A
IntfName: IQDIOINTF6 IntfType: IPAQIDIO6
TRLE: IUTIQDIO CHPID: FE VChid: 0000
Datapath: 0E02 SMCD: Yes
VMACAddr: 620001AA0E2B
IntfName: EZAISM01 IntfType: ISM Associated: Yes
TRLE: IUT00061 PFID: 0061 VChid: 7700
GIDAddr: 8002000900090061
IntfName: EZAIQCE0 IntfType: IPAQIQDC Associated: Yes
TRLE: IUTIQCE0 CHPID: E0 VChid: 010C
Datapath: 0E0F
IntfName: EZ6IQCE0 IntfType: IPAQIQDC6 Associated: Yes
TRLE: IUTIC6E0 CHPID: E0 VChid: 010C
Datapath: 0E19
Example output for an OSAENTA interface:
OSA-Express Network Traffic Analyzer Information:
OSA PortName: QDIO4101 OSA DevStatus: Ready
OSA IntfName: EZANTAQDIO4101 OSA IntfStatus: Ready
OSA Speed: 1000 OSA Authorization: Logical Partition
OSAENTA Cumulative Trace Statistics:
DataMegs: 0 Frames: 8
DataBytes: 760 FramesDiscarded: 4
FramesLost: 0
OSAENTA Active Trace Statistics:
DataMegs: 0 Frames: 8
DataBytes: 760 FramesDiscarded: 4
FramesLost: 0 TimeActive: 8
OSAENTA Trace Settings: Status: On
DataMegsLimit: 1024 FramesLimit: 2147483647
Abbrev: 224 TimeLimit: 10080
Discard: ALL
OSAENTA Trace Filters: Nofilter: ALL
DeviceID: *
Mac: *
VLANid: *
ETHType: *
IPAddr: *
Protocol: *
PortNum: *
Report field descriptions
- DevName
- The device name that is configured on the DEVICE statement.
- DevType
- The device type that is configured on the DEVICE statement.
- DevNum
- The device number that is configured on the DEVICE statement. This field is significant only for device types CTC, CLAW, LCS, and CDLC.
- DevStatus
- The device status. You can use this field if you are having activation problems with the device or interface. Table 1 describes the possible status values:
Device status | Description |
---|---|
Starting | A START of the device has been issued by the operator, and TCP/IP has sent an Activation request to the Data Link Control (DLC) layer. |
Sent SETUP | DLC has acknowledged the TCP/IP Activation request, and TCP/IP has requested DLC to perform the initial I/O sequence with the device. |
Enabling | DLC has acknowledged the TCP/IP Activation request, and TCP/IP has requested DLC to allow data connections to be established for the device. |
Connecting | DLC has accepted the Initial I/O Sequence request. |
Connecting2 | The control connection for a CLAW device has been established, and the second connection (on which IP traffic is carried) is being established. |
Negotiating | The initial I/O sequence with the device is complete, and TCP/IP is performing additional link-layer initialization. |
Ready | The initialization sequence with the device is complete. The device is now ready. |
Deactivating | DLC has performed the first stage of an orderly device deactivation. |
Not active | The device is not active. (The device has never been started, or has been stopped after having been started.) |
- Configured router status (CfgRouter)
- The router attribute (PRIROUTER/SECROUTER/NONROUTER) that is specified on the DEVICE or INTERFACE statement. This field is significant only for MPCIPA devices and for IPAQENET and IPAQENET6 interfaces. This field is not displayed if virtual MAC (VMAC) has been configured.
- Actual router status (ActRouter)
- The router attribute in effect for the device or interface. It matches the configured router status unless the configured value conflicted with the configured value of another stack that is sharing the adapter. This field is significant only for MPCIPA devices and for IPAQENET and IPAQENET6 interfaces. The router attribute is determined when the device or interface starts. This field is not displayed if virtual MAC (VMAC) has been configured.
- Virtual MAC address (VMACAddr)
- The virtual local hardware address for this link or interface.
This field is significant for the following types of devices:
- An IPAQENET link or interface, or an IPAQENET6 interface, where a virtual MAC address was configured by specifying the VMAC parameter. The value n/a is displayed if VMAC was configured but a virtual MAC address was not configured.
- An RNIC interface that is created when an IPAQENET or IPAQENET6 interface specified SMCR. The VMAC address is provided by VTAM®, and is not configured on the INTERFACE profile statement. VMACAddr is displayed for active RNIC interfaces only.
- Virtual MAC origin (VMACOrigin)
- Displays whether the virtual MAC address (VMACAddr) was configured on the LINK or INTERFACE statement, or was generated by OSA-Express. This field is significant only for IPAQENET links or interfaces and for IPAQENET6 interfaces for which virtual MAC (VMAC) has been configured. The following list shows the possible values:
- Cfg
- The virtual MAC address is configured on the LINK statement or on the INTERFACE statement.
- OSA
- The virtual MAC address has been generated by OSA-Express.
- Virtual MAC router status (VMACRouter)
- Displays the virtual MAC router attribute that was specified on
the LINK or INTERFACE statement using the ROUTEALL or ROUTELCL keywords.
This field is significant only for IPAQENET links or interfaces and
for IPAQENET6 interfaces for which virtual MAC (VMAC) has been configured.
See OSA Routing information in the z/OS Communications Server: IP Configuration Guide for more information about Virtual MAC router
attributes. The following list shows the possible values:
- All
- Corresponds to the ROUTEALL keyword. Indicates that all IP traffic destined to the Virtual MAC is forwarded by the OSA-Express device to the TCP/IP stack
- Local
- Corresponds to the ROUTELCL keyword. Indicates that only traffic destined to the Virtual MAC whose destination IP address is registered with the OSA-Express device by this TCP/IP stack is forwarded by the OSA-Express device.
- Configured packing status (CfgPacking)
- This field is the packing attribute (Packed/None) specified on the DEVICE statement. This field is significant only for CLAW devices.
- Actual packing status (ActPacking)
- This field indicates the packing attribute in effect for the device. It will match the configured packing status unless packing was requested and the device does not support packing. This field is significant only for a CLAW device and is determined when the device starts.
- LnkName/IntfName
- This field is the link name or the interface name of the particular device or interface being displayed. If the device or interface is configured, this field is the link name configured in the LINK statement or the interface name configured in the INTERFACE statement. If the link name or interface name is dynamically generated by the TCP/IP stack, this field is the dynamically generated link name or interface name.
- LnkType/IntfType
- This field is the link type or the interface type of the particular device or interface being displayed. If the device or interface is configured, this field is the link type configured in the LINK statement or the interface type configured in the INTERFACE statement. If the link type or interface type is dynamically generated by the TCP/IP stack, this field is the dynamically generated link type or interface type. .
- LnkStatus/IntfStatus
- This field is the link or interface status. The following list describes the possible link or interface status values:
Link/Interface status | Description |
---|---|
Ready | A START of the device/interface has been issued by the operator, and TCP/IP has been sent an Activation request to the Data Link Control (DLC) layer. |
Not Active | The link or interface is not active. There is
no command to start a link; link activation is normally performed
during START device processing. Interface activation is performed
during START interface processing. A link or interface is marked Not
Active when:
|
DAD Pend | Duplicate Address Detection (DAD) for the link-local address is in progress on the IPv6 interface. |
- PortName
- The name of the OSA-Express port. This is the value that was specified on the PORTNAME parameter on the INTERFACE statement. This field is significant only for IPAQENET and IPAQENET6 interfaces.
- Datapath
- The subchannel address that is associated with the TRLE definition. This value is one of the
addresses that was specified on the DATAPATH parameter on the TRLE definition and is the subchannel
address that VTAM assigned to this interface. If VTAM has not yet assigned a subchannel address to this interface,
then this field contains the value
Unknown
. This field is significant only for IPAQENET, IPAQIDIO, IPAQENET6, IPAQIDIO6, IPAQIQDC, and IPAQIQDC6 interfaces. - DatapathStatus
- The datapath status. This field is significant only for IPAQENET, IPAQIDIO, IPAQENET6, IPAQIDIO6, IPAQIQDC, and IPAQIQDC6 interfaces. This field contains information that is useful if the interface is not activating correctly. See Table 1 for possible status values.
- CHPIDType
- The CHPID type that is associated with this interface. This value was specified on the CHPIDTYPE
parameter on the INTERFACE statement (or was generated by the stack) for OSA-Express QDIO interfaces. This field is
significant only for IPAQENET, IPAQENET6, IPAQIQDC, and IPAQIQDC6 interfaces. The possible
values and meanings are:
- IQD
- A CHPID with connectivity to an internal HiperSockets network
- OSD
- A CHPID with connectivity to the external data network
- OSX
- A CHPID with connectivity to the intra ensemble data network
- OSM
- A CHPID with connectivity to the intra node management network
- IPAddr
- The IP address and optional number of bits (leftmost significant bits), which identifies the subnet mask of the interface. This value was specified on the IPADDR parameter on the INTERFACE statement. This field is significant for IPAQENET interfaces only. If the interface is defined with the TEMPIP keyword, the IP address is 0.0.0.0.
- CHPID
- The CHPID value that is associated with this interface. For HiperSockets, this value was specified on the CHPID parameter on the INTERFACE statement for predefined HiperSockets interfaces or is the value obtained from VTAM for HiperSockets interfaces that are created by dynamic XCF definitions. For OSA-Express QDIO interfaces that are configured with CHPIDTYPE OSX, this value was specified on the CHPID parameter. For IPAQIQDC or IPAQIQDC6 interfaces, this value was defined in HCD and learned by VTAM during dynamic IQDC TRLE generation. This field is significant only for IPAQIDIO, IPAQIDIO6, IPAQENET, IPAQENET6, IPAQIQDC, or IPAQIQDC6 interfaces.
- SMCR
- Indicates whether this interface can be used for new TCP connections for Shared Memory
Communications over Remote Direct Memory Access (SMC-R) for external data network communications. This value was
specified on the SMCR or NOSMCR parameter on the INTERFACE statement for OSA-Express QDIO interfaces. This field is significant only for IPAQENET and IPAQENET6
interfaces. The possible values and meanings are:
- YES
- Indicates that this interface can be used for new TCP connections to communicate with other
stacks on the external data network by using SMC-R.
For an inactive interface, Yes means the interface is configured for SMC-R. An interface is configured for SMC-R when the SMCR parameter was specified on the INTERFACE statement or is in effect by default.
For an active interface, Yes means the interface is enabled for SMC-R. An interface is enabled for SMCR when the following conditions are true:- The SMCR parameter was specified on the INTERFACE statement or is in effect by default.
- The TCP/IP stack is enabled for SMC-R. A TCP/IP stack is enabled for SMC-R when the SMCR parameter was specified on the GLOBALCONFIG statement.
- A physical network ID value was configured in HCD for this interface.
- NO
- Indicates that this interface cannot be used for new TCP connections to communicate with other stacks on the external data network by using SMC-R. The NOSMCR parameter was specified on the INTERFACE statement.
- SMCD
- Indicates whether this interface can be used for new TCP connections
for Shared Memory Communications - Direct Memory Access (SMC-D). This value was specified on the SMCD or NOSMCD parameter on the INTERFACE statement for OSA-Express QDIO or HiperSockets interfaces. This field is significant only for IPAQENET, IPAQIDIO, IPAQENET6, and IPAQIDIO6 interfaces. The possible values and meanings are:
- YES
- Indicates that this interface can be used for new TCP connections to communicate with other
stacks by using SMC-D.
For an inactive interface, Yes means the interface is configured for SMC-D. An interface is configured for SMC-D when the SMCD parameter was specified on the INTERFACE statement or is in effect by default.
For an active interface, Yes means the interface is enabled for SMC-D. An interface is enabled for SMC-D when the following conditions are true:- The SMCD parameter was specified on the INTERFACE statement or is in effect by default.
- The TCP/IP stack is enabled for SMC-D. A TCP/IP stack is enabled for SMC-D when the SMCD parameter was specified on the GLOBALCONFIG statement.
- A physical network ID value was configured in HCD for this interface.
- NO
- Indicates that this interface cannot be used for new TCP connections to communicate with other stacks by using SMC-D. The NOSMCD parameter was specified on the INTERFACE statement.
- PFID
- The Peripheral Component Interconnect Express (PCIe) function ID (PFID) value that defines a "RoCE Express" feature or
an internal shared memory (ISM) device.
- For a "RoCE Express" feature, this value is specified on the SMCR PFID parameter of the GLOBALCONFIG TCP/IP profile statement. This field is significant only for RNIC interfaces that are created when an IPAQENET or IPAQENET6 interface specifies SMCR or takes SMCR as the default setting.
- For an ISM device, this value is learned dynamically during ISM device activation and is provided by VTAM to the TCP/IP stack. This field is significant only for ISM interfaces that are created when an IPAQENET, IPAQIDIO, IPAQENET6, or IPAQIDIO6 interface specifies SMCD or takes SMCD as the default setting.
- PortNum
- Specifies the port number that is used for the associated PFID.
- When PFID represents an IBM® 10 GbE RoCE Express feature, the PortNum value is specified with the PFID value on the SMCR parameter of the GLOBALCONFIG statement in the TCP/IP profile.
- When PFID represents a RoCE Express2 feature, the PortNum value is the port number configured for the PFID in the Hardware Configuration Definition (HCD). The port number is learned by VTAM during activation of the PFID and might be different from the value coded for PORTNUM for this PFID on the GLOBALCONFIG SMCR statement.
- PNetID
- The physical network ID value that is configured in HCD for an interface. This field is
significant only for IPAQIDIO or IPAQENET interfaces defined by using the
INTERFACE statement, IPAQIDIO6 interfaces, IPAQENET6 interfaces, IPAQIQDC interfaces, IPAQIQDC6 interfaces, and active RNIC and ISM interfaces.
Interface Value Active OSD interfaces - If a physical network ID is configured in HCD for the OSD interface, the configured value is displayed.
- If no physical network ID is configured in HCD for the OSD interface, the value*None* is displayed.
Active OSX interfaces The reserved value IEDN is used. Active HiperSockets interfaces - If a physical network ID is configured in HCD for the HiperSockets interface, the configured value is displayed.
- If no physical network ID is configured in HCD for the HiperSockets interface, the value*None* is displayed.
Active ISM interfaces - If a physical network ID is configured in HCD for the ISM interface, the configured value is displayed.
-
If no physical network ID is configured in HCD for the ISM interface, the value *None* is displayed.
Active RNIC interfaces The value that is configured in HCD for the RNIC interface is displayed. If no value is configured in HCD, activation of the RNIC interface fails. - TRLE
- The name of the TRLE that is associated with this interface. This field is significant only for
MPCPTP6, IPAQIDIO, IPAQIDIO6, IPAQENET, IPAQENET6, IPAQIQDC,
IPAQIQDC6, ISM and RNIC interfaces.
- For MPCPTP6 interfaces
- This value was specified on the TRLE parameter of the INTERFACE statement for predefined MPC interfaces or is the value obtained from VTAM for MPC interfaces that are created by dynamic XCF definitions.
- For IPAQIDIO or IPAQIDIO6 interfaces
- This value is obtained from VTAM for IPAQIDIO, IPAQIDIO6, IPAQENET, or IPAQENET6 interfaces that INTERFACE definitions create. This value is displayed for active interfaces only.
- For IPAQENET and IPAQENET6 interfaces
- This value is the name of the TRLE that was statically defined to be used for this interface.
- For IPAQIQDC and IPAQIQDC6 interfaces
- This value is obtained from VTAM for IQDC interfaces that are created dynamically during activation of IPAQENET or IPAQENET6 interfaces when AUTOIQDC is specified. This value is displayed for active interfaces only.
- For ISM interfaces
- This value is obtained from VTAM for ISM interfaces that are created dynamically during activation of IPAQENET, IPAQIDIO, IPAQENET6, or IPAQIDIO6 interfaces that specify SMCD or take SMCD as the default setting when SMC-D is enabled. This value is displayed only when the PFIDStatus value of the interface is Starting or Ready.
- For RNIC interfaces
- This value is obtained from VTAM for RNIC interfaces that are created for PFIDs configured on the GLOBALCONFIG statement when SMC-R is enabled. This value is displayed only when the PFIDStatus value of the interface is Starting or Ready.
- PFIDStatus
- This field is the RNIC or
ISM interface PFID status. The following list describes
several status values:
PFID status Description Ready The initialization sequence with the PFID is complete. The PFID is ready. Not Active The PFID is not active. The PFID has never been started, or has been stopped after having been started. Starting A START command of the PFID has been issued, and TCP/IP has sent an Activation request to the Data Link Control (DLC) layer. Deactivating DLC has performed the first stage of an orderly PFID deactivation. - GidAddr
- The group identifier (GID)
value that is associated with the RNIC or ISM interface.
- When SMC-R is enabled, this value is obtained from VTAM for RNIC interfaces that are created for PFIDs configured on the GLOBALCONFIG statement when SMC-R is enabled. This value is displayed for active RNIC interfaces only.
- When SMC-D is enabled, this value is obtained from VTAM for ISM interfaces that are created for SMC-D processing. This value is displayed for active ISM interfaces only.
- NetNum
- The adapter number that was specified on the LINK statement. This field is significant only for CTC and LCS links.
- QueSize
- The queue size represents the number of outbound packets for this link or interface that are queued and waiting for ARP or neighbor resolution. This field is significant only for links on ATM and LCS devices and for IPAQENET6 interfaces.
- Speed
- Indicates the interface speed (in million bits per second) that is reported by the device. This field is significant only for IPAQENET links or interfaces, ATM and IPAQTR links, IPAQENET6 interfaces, and RNIC interfaces, and only if the link or interface is active.
- Gen
- Indicates the generation level for the "RoCE Express" feature, and is significant only if the interface is active. Possible values
are:
- RoCE Express
- The feature is an IBM 10 GbE RoCE Express feature.
- RoCE Express2
- The feature is a RoCE Express2 feature.
- MAC address order (MacAddrOrder)
- Indicates the canonical option (CANON/NONCANON) that is specified on the LINK statement. This field is significant only for token-ring links.
- SrBridgingCapability
- Indicates whether the link supports source route bridging. This field is significant only for token-ring links.
- IpBroadcastCapability
- Indicates whether the link is broadcast capable. This field is significant only for links on LCS and MPCIPA devices and IPAQENET interfaces.
- ArpBroadcastType
- Indicates the ARP broadcast option (ALLRINGSBCAST/LOCALBCAST) that is specified on the LINK statement. This field is significant only for token-ring links.
- ArpOffload
- Indicates whether ARP processing is being offloaded to the adapter. This field is significant only for active links that support ARP offload.
- ArpOffloadInfo
- Indicates whether the adapter reports ARP offload data to TCP/IP. If so, then the ARP cache data can be displayed with the Netstat ARP/-R report even though the ARP function is being offloaded. This field is significant only for active links that support ARP offload.
- Routing Parameters
- This section displays routing information for IPv4 links that
are defined with the DEVICE and LINK profile statements.
- MTU Size
- This value is determined in one of the following ways:
- If you are using OMPROUTE and the link is defined to OMPROUTE, the value might have been specified on the MTU parameter on the OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE statement for the link. If one of these OMPROUTE statements was specified for the link but the MTU parameter was not specified, OMPROUTE sets the MTU Size value to 576.
- If you are using OMPROUTE, the link is not defined to OMPROUTE, and OMPROUTE is not configured to ignore undefined links, OMPROUTE sets the MTU Size value to 576.
- If you are not using OMPROUTE (or if the link is not defined to OMPROUTE), OMPROUTE is configured to ignore undefined links, and a BSDROUTINGPARMS profile statement was specified for the link, then the MTU Size value is configured using the BSDROUTINGPARMS profile statement MTU parameter.
- If none of the previously described methods provides an MTU Size value
or if the MTU Size parameter does not apply to this link, then the
value
n/a
is displayed.
- Metric
- The routing metric that is associated with the link. This value
is determined in one of the following ways:
- If you use OMPROUTE and the link is defined to OMPROUTE using the OSPF_INTERFACE statement, then the Metric value is configured using the Cost0 parameter on the OSPF_INTERFACE statement. If the Cost0 parameter is not specified, then OMPROUTE sets the value to 1.
- If you use OMPROUTE and the link is defined to OMPROUTE using the RIP_INTERFACE statement, then the Metric value is configured using the In_Metric parameter on the RIP_INTERFACE statement. If the In_Metric parameter is not specified, then OMPROUTE sets the value to 1.
- If you use OMPROUTE and the link is defined to OMPROUTE using the INTERFACE statement or if the link is not defined to OMPROUTE and OMPROUTE is not configured to ignore undefined links, then OMPROUTE sets the Metric value to 0.
- If you are not using OMPROUTE (or if the link is not defined to
OMPROUTE) and OMPROUTE is configured to ignore undefined links, the
Metric value is configured in one of the following ways:
- For dynamic XCF links, the Metric value is configured using the cost_metric value of the DYNAMICXCF parameter on the IPCONFIG profile statement.
- If a BSDROUTINGPARMS profile statement was specified for the link, the Metric value is configured using the cost_metric parameter of BSDROUTINGPARMS profile statement.
- If none of the previously described methods provided a Metric value, the stack sets the value to 0
- DestAddr
- The destination address applies to point-to-point links only and
is the IP Address of the other side of the point-to-point link. This
value is determined in one of the following ways:
- If you are using OMPROUTE and the link is defined to OMPROUTE, then the value is configured using the Destination_Addr parameter on the OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE statement. If the Destination_Addr parameter is not specified, then OMPROUTE sets the value to 0.
- If you are using OMPROUTE but the link is not defined to OMPROUTE and OMPROUTE is not configured to ignore undefined links, then OMPROUTE sets the value to 0.
- If you are not using OMPROUTE (or if the link is not defined to OMPROUTE), OMPROUTE is configured to ignore undefined links, and a BSDROUTINGPARMS profile statement was specified for the link, then the value is configured using the dest_addr parameter for this statement.
- If none of these methods has provided a destination address value,
then the stack sets a default value in one of the following ways:
- For links other than point-to-point links, the value is set to 0.
- For point-to-point links, the value is set as follows:
- If routes are defined over the link, then the stack sets the value using the gateway address of an indirect route or the destination address of a direct host route.
- If no routes are defined over the link, then the value is set to 0.
- SubnetMask
- The subnet mask that is associated with the link. This value
is determined in one of the following ways:
- If you are using OMPROUTE and the link is defined to OMPROUTE, then the value is configured using the Subnet_Mask parameter on the OSPF_INTERFACE, RIP_INTERFACE, or INTERFACE statement.
- If you are using OMPROUTE, the link is not defined to OMPROUTE, and OMPROUTE is not configured to ignore undefined links, then OMPROUTE assigns a value based on the IP address that is assigned to the link.
- If you are not using OMPROUTE (or if the link is not defined to
OMPROUTE) and OMPROUTE is configured to ignore undefined links, then
the value is assigned in one of the following ways:
- For dynamic XCF links, the value is configured using the subnet_mask or num_mask_bits value of the DYNAMICXCF parameter on the IPCONFIG profile statement.
- For dynamic VIPA links, the value is configured using the address_mask parameter on the VIPADEFINE, VIPABACKUP, or the VIPARANGE profile statement.
- If a BSDROUTINGPARMS profile statement was specified for the link, the value is configured using the subnet_mask parameter for the BSDROUTINGPARMS profile statement.
- If none of the previously described methods provides a subnet mask value, then the stack assigns a value based on the IP address that is assigned to the link.
- Packet trace settings
- Use the PKTTRACE statement to control the packet tracing facility in TCP/IP. You can use this
statement to select IP packets as candidates for tracing and subsequent analysis. An IP packet must
meet all of the conditions specified on the statement for it to be traced.
- Protocol
- The protocol number from the PROT keyword of the PKTTRACE command or * if not specified.
- TrRecCnt
- The number of packets traced for this PKTTRACE command.
- PckLength
- The value of the ABBREV keyword of the PKTTRACE command or FULL to capture the entire packet.
- SrcPort
- The port number from the SRCPORT parameter of the PKTTRACE command or profile statement. If an asterisk (*) is displayed, then either a port number was not specified for the SRCPORT parameter, or the PORTNUM parameter was also specified. If both the SrcPort and PortNum fields contain a value *, then the IP packets are not being filtered by the source port.
- DestPort
- The port number from the DESTPORT parameter of the PKTTRACE command or profile statement. If an asterisk (*) is displayed, then either a port number was not specified for the DESTPORT parameter, or the PORTNUM parameter was also specified. If both the DestPort and PortNum fields contain an asterisk (*), then the IP packets are not being filtered by destination port.
- PortNum
- The port number from the PORTNUM parameter of the PKTTRACE command or profile statement. If an asterisk (*) is displayed, then either a port number was not specified for the PORTNUM parameter, or the DESTPORT or SRCPORT parameters were also specified. If the PortNum, SrcPort, and DestPort fields all contain an asterisk (*), then the IP packets are not being filtered by port.
- Discard
- The value specified for the PKTTRACE DISCARD parameter. A numerical value is a discard reason code. The value NONE, which is the default, indicates that only packets that were delivered are being traced. The value ALL indicates that only discarded IP packets are being traced. The value asterisk (*) indicates that discarded IP packets and delivered IP packets are being traced.
- IpAddr
- The IP address from the IPADDR keyword of the PKTTRACE command or asterisk (*) if not specified.
- SubNet
- The IP subnet mask from the SUBNET keyword of the PKTTRACE command or asterisk (*) if not specified.
- ATM Specific
- This section contains information about ATM links:
- ATM PortName
- The PORTNAME value specified on the DEVICE statement.
For an ATM link configured as a Permanent Virtual Circuit (PVC), the following additional fields are displayed:
- ATM PVC Name
- The name of the PVC specified on the ATMPVC statement.
- PVC Status
- This field can have the following values:
ATM PVC status Description Not Active The PVC is not active. There is no command to start a PVC; PVC activation is normally attempted during START device processing. A PVC is marked Not Active when: - The device has not yet been started.
- The remote side of the PVC is not active.
- A failure has been encountered during the PVC activation phase. (Such a failure produces an error message to the operator.)
Ready The initialization sequence for the PVC is complete. The PVC is now ready for use.
For an ATM link configured as a Switched Virtual Circuit (SVC), the following additional fields are displayed:
- ATM LIS Name
- The name of the ATM Logical IP Subnet (LIS) specified on the ATMLIS statement.
- SubnetValue
- The subnet_value specified on the ATMLIS statement.
- SubnetMask
- The subnet_mask specified on the ATMLIS statement.
- DefaultMTU
- The DFLTMTU value specified on the ATMLIS statement.
- InactvTimeOut
- The INACTVTO value specified on the ATMLIS statement.
- MinHoldTime
- The MINHOLD value specified on the ATMLIS statement.
- MaxCalls
- The maximum number of SVCs that can be active for this ATMLIS.
- CachEntryAge
- The CEAGE value specified on the ATMLIS statement.
- ATMArpReTry
- The ARPRETRIES value specified on the ATMLIS statement.
- ATMArpTimeOut
- The ARPTO value specified on the ATMLIS statement.
- PeakCellRate
- The PEAKCR value specified on the ATMLIS statement.
- NumOfSVCs
- The number of currently active SVCs for this ATMLIS.
- BearerClass
- The BEARERCLASS value specified on the ATMLIS statement.
For an ATM SVC link that is configured with an ATM ARP server, the following additional fields are displayed:
- ATMARPSV Name
- The name of the ATM ARP server specified on the ATMARPSV statement.
- VcType
- Indicates whether the ATM ARP server connection is a PVC or an SVC. This value comes from the ATMARPSV statement.
- ATMaddrType
- The ATM address type specified on the ATMARPSV statement. The only supported value is NSAP.
- ATMaddr
- The ATM address of the ATM ARP server. If the connection to the ATM ARP server is an SVC, then this is the physical_addr value specified on the ATMARPSV statement. For a PVC connection to the ATM ARP server, this is the remote ATM address learned by TCP/IP when the PVC was activated.
- IpAddr
- The IP address of the ATM ARP server. If the connection to the ATM ARP server is an SVC, then this is the ip_addr value specified on the ATMARPSV statement. For a PVC connection to the ATM ARP server, this is the remote IP address learned by TCP/IP when the PVC was activated.
- Multicast Specific
- This section displays multicast information for the link or interface.
- Multicast Capability
- Indicates whether the link or interface is multicast capable.
- For point-to-point interfaces, the value of this field is always Yes.
- For LCS and MPCIPA links and IPAQENET, IPAQENET6, IPAQIDIO, and IPAQIDIO6 interfaces, the multicast capability is known only after the link or interface is active. If the link or interface is not active, the multicast capability value is Unknown.
- For IPAQIQDX6 interfaces, the value of this field is always ND only, the interface is multicast capable but multicast processing is used only for neighbor discovery.
If the link or interface is multicast capable then the following additional fields are displayed for each multicast group for which the link or interface is receiving data. There is no limit to the number of multicast groups for which a link or interface can receive data. For IPAQIQDX6 interfaces, the multicast groups indicate only neighbor discovery processing.
- Group
- The multicast group address for which this link or interface is receiving data.
- RefCnt
- The number of applications that are receiving data for this multicast group.
- SrcFltMd
- The source filter mode indicates the type of multicast source IP address filtering that has
been configured at the interface. Source IP address filtering can be done by either an IGMPv3 or
MLDv2-capable multicast router on a per interface basis or by the host on a per socket basis. The
host provides its source filter mode and source IP address filter list for each multicast group that
an application has joined on the interface with any IGMPv3 and MLDv2-capable multicast routers that
are connected to the interface. This permits IGMPv3-capable and MLDv2-capable multicast routers to
send only multicast packets that have been requested by at least one host on the subnet to which the
interface is connected. If the multicast packets are not filtered by an IGMPv3-capable or
MLDv2-capable multicast router (for example the router does not support IGMPv3 or MLDv2), or if
there are multiple hosts on the local area network that have either a different source filter mode
or a different source IP address filter list for a given multicast group, the host uses the source
IP address filter information to ensure that each application receives only packets that it has
requested.
The value is either Include or Exclude. A source filter applies only to incoming multicast data. The source filter applies to all the IP addresses in the SrcAddr fields for the associated multicast group address and the link or the interface. The source filter mode and the corresponding source filter IP addresses are configured by applications for their UDP or RAW sockets that have joined the multicast group for this interface. See the information about Designing multicast programs in the z/OS Communications Server: IP Sockets Application Programming Interface Guide and Reference for details about how applications configure these values for a socket.
- Include
- Indicates that the interface or link receives only multicast datagrams that have a source IP address that matches an IP address indicated in the SrcAddr field.
- Exclude
- Indicates either that the source filter function is not active or that the interface or link receives only multicast datagrams that have a source IP address that does not match an IP address indicated in the SrcAddr field. If the source filter function is not active or if the source filter function is active but no SrcAddr value is set, the SrcAddr field contains the value None.
- SrcAddr
- Source address information for the socket.
- ipaddr
- The source IP address that is used in conjunction with the SrcFltMd value to determine which incoming multicast datagrams are received by the interface.
- None
- This value is displayed only when the source filter function is not configured for the interface or when the source filter mode is Exclude but there was no intersection of excluded source IP addresses among the sockets for the same multicast group address and interface.
- Source VIPA interface (SrcVipaIntf)
- The name of the VIPA that is used for this interface if source VIPA is in effect. This is the value that was specified on the SOURCEVIPAINTERFACE parameter on the INTERFACE statement. This field is significant only for IPAQENET, IPAQENET6, IPAQIDIO6, and MPCPTP6 interfaces.
- Duplicate address detection (DupAddrDet)
- The DUPADDRDET value specified on the INTERFACE statement. This field is significant only for IPAQENET6 interfaces.
- Interface ID (IntfID)
- The INTFID value specified on the INTERFACE statement. This field is significant only for IPAQENET6, IPAQIDIO6, and MPCPTP6 interfaces.
- MAC address (MacAddress)
- The local hardware address for this link or interface. This field is significant only for links on LCS devices and for IPAQENET6 interfaces. This field is displayed only if the link or interface is active and if virtual MAC (VMAC) is not configured.
- Router Hop Limit (RtrHopLimit)
- The value that is placed in the Hop Count field of the IP header for outgoing IP packets. This value was obtained from a received router advertisement and is significant only for IPAQENET6 interfaces. This field is displayed only when a nonzero hop limit value was received in a router advertisement over this interface and IGNOREROUTERHOPLIMIT is not configured on the IPCONFIG6 profile statement.
- CfgMtu
- The MTU value that was configured on the INTERFACE statement (or
None
if an MTU value was not configured). This field is significant only for IPAQENET, IPAQENET6, or IPAQIDIO interfaces.
- ActMtu
- The largest MTU that is supported by an active link or interface. If the link or interface is inactive, then this field displays Unknown. This field is significant for all links and interfaces except virtual ones.
- VLANid
- This field is significant only for IPAQENET links or interfaces,
IPAQIDIO links, or IPAQENET6 and IPAQIDIO6 interfaces. This field
indicates whether a virtual LAN ID was configured on the VLANID parameter
on the LINK or INTERFACE profile statement. The following values can
be displayed in this field:
- None
- This value indicates that the VLANID parameter was not specified on the LINK or INTERFACE profile statement for the interface. For an IPAQIDIO link or IPAQIDIO6 interface that is dynamically generated as part of dynamic XCF HiperSockets processing, this value indicates that the IQDVLANID parameter was not specified on the GLOBALCONFIG profile statement.
- n/a
- This value indicates that the VLANID parameter was specified on the LINK or INTERFACE profile statement, but the interface does not support VLAN IDs.
- vlanid
- If an OSA-Express device is active and supports virtual LAN IDs, this field indicates that all IP packets through this OSA-Express link or interface from this stack are being tagged with this VLAN ID. For an active HiperSockets link or interface that supports virtual LAN IDs, this field indicates that all IP packets through this HiperSockets link or interface from this stack are associated with this VLAN ID.
- VLANpriority
- This field is significant only for active IPAQENET links or interfaces or IPAQENET6 interfaces.
This field indicates whether all IP packets through this OSA-Express link or interface from this stack are being tagged with a VLAN priority. The possible
values are:
- Enabled
- Indicates that all IP packets through this OSA-Express link or interface are being tagged with a VLAN priority. See z/OS Communications Server: IP Configuration Reference for information about the SetSubnetPrioTosMask statement and details about how to configure VLAN priorities.
- Disabled
- Indicates that the OSA-Express link or interface
supports VLAN priority, but currently no VLAN priority values are defined. If the VLANid field
displays
None
orn/a
, all IP packets through this OSA-Express link or interface are not VLAN tagged. All other values indicate that all IP packets are VLAN tagged, but only with VLAN IDs, not with VLAN priority.
- Unknown
- Indicates that the VLAN priority tagging support for the OSA-Express is unknown because the link or interface is not yet active.
- DynVLANRegCfg
- This field is significant only for IPAQENET links or interfaces and IPAQENET6 interfaces. This
field is displayed only under the following conditions:
- The link or interface is not yet active and a VLAN ID was specified.
- The link or interface is active, a VLAN ID value was specified, and the OSA-Express feature has accepted the VLAN ID value.
This field indicates whether dynamic VLAN ID registration was configured on the LINK or INTERFACE statement. The possible values are:- Yes
- Indicates that the DYNVLANREG parameter was specified on the LINK or INTERFACE statement.
- No
- Indicates that the NODYNVLANREG parameter was specified on the LINK or INTERFACE statement or is in effect by default.
- DynVLANRegCap
-
This field indicates whether the OSA-Express feature that is represented by the LINK or INTERFACE statement is capable of supporting dynamic VLAN ID registration.
This field is significant only for IPAQENET links or interfaces and IPAQENET6 interfaces. This field is displayed only under the following conditions:- The link or interface is not yet active and a VLAN ID was specified.
- The link or interface is active, a VLAN ID value was specified, and the OSA-Express feature has accepted the VLAN ID value.
The possible values are:- Yes
- Indicates that the OSA-Express feature is capable of supporting dynamic VLAN ID registration.
- No
- Indicates that the OSA-Express feature is not capable of supporting dynamic VLAN ID registration.
- Unknown
- Indicates that the dynamic VLAN ID registration capability of the OSA-Express feature is unknown because the link or interface is not yet active.
- ChecksumOffload
- This field is significant only for active IPAQENET and IPAQENET6
links or interfaces. This field indicates whether the checksum offload
support is in effect and is displayed only when the link or interface
is active. The possible values are:
- Yes
- Indicates that the checksum offload function is enabled on the adapter for this interface.
- No
- Indicates that the checksum offload function is not enabled on the adapter for this interface.
- Unsupported
- Indicates that the checksum offload function is not supported on the adapter for this interface.
- SegmentationOffload
- This field is significant only for active IPAQENET and IPAQENET6
links or interfaces. This field indicates whether the TCP segmentation
offload support is in effect and is displayed only when the link or
interface is active. Possible values are:
- Yes
- Indicates that the segmentation offload function is enabled on the adapter for this interface.
- No
- Indicates that the segmentation offload function is not enabled on the adapter for this interface.
- Unsupported
- Indicates that the segmentation offload function is not supported on the adapter for this interface.
- SecClass
- This field identifies the security class value for IP filtering.
This field applies to all IPv4 and IPv6 interfaces except virtual
and loopback, but the value is in effect only if the IPSec function
is active for the applicable IP version. You can use the Netstat CONFIG/-f command
to determine whether IPSec is active. Valid security class values
are in the range 1 - 255. The displayed value was defined by one of
the following methods:
- By the SECCLASS parameter on the LINK or INTERFACE profile statement
- For dynamic XCF interfaces, by the DYNAMICXCF SECCLASS subparameter on the IPCONFIG or IPCONFIG6 profile statement
- For OSM interfaces, by the TCP/IP stack's automatic configuration of the interface, or by the IPSECURITY OSMSECCLASS subparameter on the IPCONFIG6 profile statement
- MonSysplex
- Indicates whether the status of this link or interface is being
monitored by Sysplex Autonomics. This field is significant for all
IPv4 links or interfaces except virtual, loopback, and all dynamically
configured links, and for all IPv6 interfaces except virtual, loopback,
and all dynamically configured interfaces.
- Yes
- Indicates that the status of this link or interface is being monitored by Sysplex Autonomics. It is configured by specifying the MONSYSPLEX keyword on the LINK or INTERFACE profile statement and specifying the MONINTERFACE keyword for the SYSPLEXMONITOR parameter on the GLOBALCONFIG profile statement. If DYNROUTE keyword is also coded on the GLOBALCONFIG SYSPLEXMONITOR profile statement, then the presence of dynamic routes over this link or interface is also monitored.
- Configured
- Indicates that this link or interface was configured to be monitored by Sysplex Autonomics. It was configured by specifying the MONSYSPLEX keyword on the LINK or INTERFACE profile statement, but the link or interface is not currently being monitored because the MONINTERFACE keyword was not specified on the SYSPLEXMONITOR parameter on the GLOBALCONFIG profile statement.
- No
- Indicates that the status of this link or interface is not being monitored by Sysplex Autonomics because the MONSYSPLEX keyword was not specified on the LINK or INTERFACE profile statement.
- Isolate
- This field is significant only for IPAQENET interfaces (defined using the INTERFACE statement) and for IPAQENET6 interfaces. This field ndicates whether the OSA-Express device is prevented from routing packets directly to another stack that is sharing the OSA-Express connection. For more details, see OSA-Express connection isolation information in z/OS Communications Server: IP Configuration Guide.
- No
- Indicates that this interface is eligible for OSA-Express direct routing. Therefore, the OSA-Express device can route packets directly to another stack that is sharing the OSA-Express connection (as long as the interface from the other stack is also eligible for direct routing).
- Yes
- Indicates that this interface is not eligible for OSA-Express direct routing. Therefore, the OSA-Express device cannot routing packets directly to another stack that is sharing the OSA-Express connection.
- OptLatencyMode
- This field is significant only for IPAQENET interfaces (defined using the INTERFACE statement) and for IPAQENET6 interfaces. The field indicates whether optimized latency mode (OLM) was configured for this OSA-Express interface. For more information about optimized latency mode, see optimized latency mode information
in z/OS Communications Server: IP Configuration Guide. Possible values are:
- No
- Indicates that the OSA-Express interface is not configured with optimized latency mode.
- Yes
- Indicates that the OSA-Express interface is configured with optimized latency mode. Optimized latency mode optimizes interrupt processing for both inbound and outbound data.
- Disabled
- Indicates that the OSA-Express interface was configured with optimized latency mode, but the function could not be enabled when the interface was activated. The most likely reason is that the OSA-Express interface does not support this function.
- IQDMultiWrite
- This field is significant only for active HiperSockets devices or interfaces.
This field indicates whether the HiperSockets multiple
write facility is currently being used for the device or interface.
To configure the stack to use the HiperSockets multiple write facility,
specify the IQDMULTIWRITE parameter on the GLOBALCONFIG profile statement.
The possible values are:
- Enabled
- Indicates that the HiperSockets multiple write facility is currently being used for the device or interface.
- Enabled (ZIIP)
- Indicates that the HiperSockets multiple write facility is currently being used for the device or interface. Additionally, CPU cycles that are associated with the HiperSockets multiple write facility are to be displaced to an available zIIP.
- Disabled
- Indicates that the HiperSockets multiple write facility is not currently being used for the device or interface.
- Unsupported
- Indicates that theIBM Z®® environment does not support the HiperSockets multiple write facility.
- ReadStorage
- This field is significant only for active IPAQENET and IPAQIDIO links or interfaces, IPAQTR links, and for IPAQIDIO6 and IPAQENET6 interfaces. This field indicates the amount of storage (in kilobytes) that is being used for read processing.
- InbPerf
- This field is significant only for IPAQENET links or interfaces,
IPAQTR links, and IPAQENET6 interfaces. This field indicates how frequently
the adapter interrupts the host. This field indicates how the processing
of inbound traffic is performed. If the interface is not active, then
this field shows the configured value. If the interface is active,
then this field shows the value that is in effect. The possible values
are:
- Balanced
- Indicates that the adapter is to use a static interrupt-timing value that strikes a balance between MinCPU and MinLatency.
- Dynamic
- This setting is significant only for IPAQENET links, and IPAQENET
and IPAQENET6 interfaces. It indicates that the stack and the adapter
are to dynamically update the frequency with which the adapter interrupts
the host for inbound traffic.
- WorkloadQueueing
- This field is displayed only for IPAQENET and IPAQENET6 interfaces.
It indicates whether QDIO inbound workload queueing is enabled. Possible
values are:
- Yes
- QDIO inbound workload queueing is in effect. The QDIO interface is defined using the INTERFACE statement with INBPERF DYNAMIC WORKLOADQ specified.
- No
- QDIO inbound workload queueing is not in effect. The QDIO interface is defined using the INTERFACE statement with INBPERF DYNAMIC or INBPERF DYNAMIC NOWORKLOADQ specified.
- Unsupported
- QDIO inbound workload queueing was requested on the INTERFACE statement but the OSA-Express interface does not support it. QDIO inbound workload queueing is supported on OSA-Express3 or later features on an IBM System z10 GA3 or later CPC.
- MinCPU
- Indicates that the adapter is to use a static interrupt-timing value that minimizes host interrupts, and therefore minimizes host CPU consumption.
- MinLatency
- Indicates that the adapter is to use a static interrupt-timing value that minimizes latency delay by more aggressively presenting received packets to the host.
- TempPrefix
- This field is significant only for IPAQENET6 interfaces with stateless
address autoconfiguration enabled. One or more TempPrefix fields are
displayed. Together the TempPrefix fields indicate the set of prefixes
for which temporary IPv6 addresses can be generated, if temporary
addresses are enabled on the IPCONFIG6 statement. The set of prefixes
is specified on the TEMPPREFIX parameter on the INTERFACE statement.
The possible values displayed are:
- All
- IPv6 temporary addresses are generated for all prefixes that are learned from a router advertisement over this interface. This is the default.
- Disabled
- Autoconfiguration of temporary addresses for the interface is disabled because duplicate addresses were detected. Temporary addresses are not generated for this interface.
- None
- Temporary addresses are not generated for this interface.
- IPv6 prefix/prefix length
- IPv6 temporary addresses are generated for all prefixes that are learned from a router advertisement over this interface and that are included in one of the prefixes in this prefix list.
- Link/Interface Statistics
- This section is significant for all links and interfaces except virtual ones. The following
statistical information is displayed:
- BytesIn
- Number of bytes received over an interface.
- Inbound Packets
- The number of unicast inbound packets received over an interface. This value applies to all links and interfaces except for RNIC and ISM interfaces.
- Inbound Packets In Error
- Number of inbound packets discarded because of an error validating the packet. This value applies to all links and interfaces except for RNIC and ISM interfaces.
- Inbound Packets Discarded
- Number of inbound packets discarded because of an out-of-storage condition. This value applies to all links and interfaces except for RNIC and ISM interfaces.
- Inbound Packets With No Protocol
- Number of inbound packets discarded because of an unknown protocol type. This value applies to all links and interfaces except for RNIC and ISM interfaces.
- BytesOut
- Number of bytes transmitted over an interface.
- Outbound Packets
- The number of unicast outbound packets transmitted over an interface. This value applies to all links and interfaces except for RNIC and ISM interfaces.
- Outbound Packets In Error
- Number of outbound packets discarded because of errors other than an out-of-storage condition. This value applies to all links and interfaces except for RNIC and ISM interfaces.
- Outbound Packets Discarded
- Number of outbound packets discarded because of an out-of-storage condition. This value applies to all links and interfaces except for RNIC and ISM interfaces.
- Inbound Operations
-
- For RNIC interfaces, this is the number of Remote Direct Memory Access (RDMA) inbound operations processed across this interface.
- For ISM interfaces, this is the number of Internal Shared Memory inbound operations processed across this interface.
- Outbound Operations
-
- For RNIC interfaces, this is the number of RDMA outbound operations processed across this interface.
- For ISM interfaces, this is the number of Internal Shared Memory outbound operations processed across this interface.
- SMC Links
-
- For RNIC interfaces, this is the current number of SMC-R links between this stack and other stacks across this interface.
- For ISM interfaces, this is the current number of SMC-D links between this stack and other stacks across this interface.
- TCP Connections
-
- For RNIC interfaces, this is the number of TCP connections across all the SMC-R links that are associated with this interface. One or more TCP connections can use the same SMC-R link.
- For ISM interfaces, this is the current number of TCP connections across all the SMC-D links that are associated with this interface. One or more TCP connections can use the same SMC-D link.
- Intf Receive Buffer Inuse
-
- For RNIC interfaces, this is the amount of RMB storage in use by the TCP connections that are using SMC-R links associated with this interface.
- For ISM interfaces, this is the amount of DMB storage in use by the TCP connections that are using SMC-D links associated with this interface.
- Device Interrupts
- The number of real program controlled interrupts (PCI's) that the VTAM device interrupt exit fields for the ISM device. A real PCI is a dispatch of
the device interrupt exit as a result of a call from the system interrupt handler.Rule: This value is reset to 0 each time when the interface is deactivated.
- IPv4 LAN Group Summary
- The IPv4 LAN group summary lists links or interfaces that are takeover candidates for each other. The stack creates a LAN group when it detects redundant connectivity to a LAN. For each link or interface in the LAN group, this summary displays which link or interface owns ARP responsibility for that link or interface. The summary also displays which link or interface owns the ARP responsibility in the LAN group for any VIPAs.
- IPv6 LAN Group Summary
- The IPv6 LAN group summary lists interfaces that are takeover
candidates for each other. The stack creates a LAN group when it detects
redundant connectivity to a LAN. For each interface in the LAN group,
this summary displays which interface owns neighbor discovery (ND)
address resolution responsibility for that interface. The summary
also displays which interface owns the ND Address Resolution responsibility
in the LAN group for any VIPAs.
- LanGroup
- Identifies the LAN group. This identifier is assigned by the stack and represents a group of interfaces on the same LAN. This identifier is not a VLAN ID.
- Name
- The link name configured on the LINK statement or the interface name configured on the INTERFACE statement.
- Status
- The link or interface status. Valid values are Active or Not Active.
- ArpOwner
- The link or interface name that owns ARP responsibility for this link or interface in the LAN group. An active link or interface owns its ARP responsibility.
- NDOwner
- The interface name that owns neighbor discovery (ND) responsibility for this interface in the LAN group. An active interface owns its ND responsibility.
- VipaOwner
- Indicates whether the link or interface owns the ARP or ND responsibility for the VIPAs in the LAN group.
- Associated IQDC Interface
- The name of the HiperSockets Converged Interface (IQDC) that is associated with this OSD
interface. This section is significant for OSD interfaces that use an IQDC interface. The following
information is displayed:
- IQDC Status
- The status of the IQDC interface. See the description of the LnkStatus/IntfStatus field for the possible interface status values.
- BytesIn
- The number of bytes that have been received over the associated IQDC interface.
- Inbound Packets
- The number of unicast inbound packets that have been received over the associated IQDC interface.
- BytesOut
- The number of bytes that have been transmitted over the associated IQDC interface.
- Outbound Packets
- The number of unicast outbound packets that have been transmitted over the associated IQDC interface.
- Associated IQDX Interface
- The name of the Internal Queued Direct I/O extensions function
(IQDX) interface that is associated with this OSX interface. This
section is significant for OSX interfaces that use an IQDX interface
for intraensemble data network (IEDN) connectivity. The following
information is displayed:
- IQDX Status
- The status of the IQDX interface. See the description of the LnkStatus/IntfStatus field for the possible interface status values.
- BytesIn
- The number of bytes that have been received over the associated IQDX interface.
- Inbound Packets
- The number of unicast inbound packets that have been received over the associated IQDX interface.
- BytesOut
- The number of bytes that have been transmitted over the associated IQDX interface.
- Outbound Packets
- The number of unicast outbound packets that have been transmitted over the associated IQDX interface.
- Associated RNIC Interface
- The dynamic interface name that is generated for "RoCE Express" interface that this stack uses for SMC-R communications. This field is significant only for active IPAQENET and IPAQENET6 interfaces that specify SMCR or take SMCR as the default value.
- Associated ISM Interface
-
A dynamic interface name that is generated for ISM interface that this stack uses for SMC-D communications. This ISM interface is associated using a matching PNETID with OSA or HiperSockets interfaces. This field is significant only for active IPAQENET, IPAQIDIO, IPAQENET6, and IPAQIDIO6 interfaces that specify SMCD or take SMCD as the default value. Associated ISM Interfaces can be used in either SMC-Dv1 or SMC-Dv2 communications.
- Unassociated ISM Interfaces
- The dynamic interface names that are generated for ISM interfaces that do not have a PNetID defined to them. Unassociated ISM Interfaces can only be used for SMC-Dv2 communications. This field is significant only for active IPAQENET, IPAQIDIO, IPAQENET6, and IPAQIDIO6 interfaces that specify SMCD or take SMCD as the default value.
- SMCR Link Information | SMCD Link Information
- The SMCR link information for a RNIC interface or the SMCD link information for an
ISM interface. This section is displayed for each RNIC and ISM interface only when the SMC modifier or the SMCID/-U filter is specified. The
following fields and statistics are displayed.Guidelines:
- An SMC-R link is uniquely identified by the combination of the VLAN number, local GID, local VMAC address, local QP number, remote GID, remote VMAC address, and remote QP number.
- An SMC-D link is uniquely identified by the combination of local GID, remote GID, and VLAN number.
- SMCDVersion
- The SMC-D Version in use for this link.
- SMCEID
- The Enterprise ID that was used to establish the SMC-D link. This is only displayed for SMC-Dv2 links.
- LocalSMCLinkId
- The SMC-R or SMC-D link identifier that this TCP/IP stack dynamically creates to represent the link.
- RemoteSMCLinkId
- The SMC-R or SMC-D link identifier that the remote peer uses to represent the link. The value is provided to this TCP/IP stack during link activation.
- SMCLinkGroupId
- The group identifier that this TCP/IP stack dynamically creates to represent the SMC-R link group that includes this individual link. This value applies to RNIC interfaces only.
- VLANid
- The virtual LAN ID for this SMC-R or SMC-D link. The value None is displayed if a virtual LAN ID has not been configured.
- MTU
- The negotiated MTU size that is used for this SMC-R link. This value applies to RNIC interfaces only.
- LocalGid
- The local GID value that is associated with this SMC-R or SMC-D link. This is the same information that is displayed in the GidAddr field.
- LocalMACAddr
- The local virtual MAC address that is associated with this SMC-R link. This value applies to RNIC interfaces only.
- LocalQP
- The local queue pair (QP) value that is associated with this SMC-R link. This value applies to RNIC interfaces only.
- RemoteGid
- The peer GID value that is associated with this SMC-R or SMC-D link.
- RemoteHostName
- The host name is optionally exchanged during SMC-Dv2 link setup time. The value being displayed is the value assigned by the SMC-D peer. For z/OS endpoints, this value is always sent to the partner using the configured hostname from the TCPIP.DATA configuration file.
- RemoteHostType
- The host operating system type is optionally exchanged during SMC-Dv2
link setup time. The value displayed is the value assigned by the SMC-D peer. The following are
valid values:
- AIX
- LINUX
- z/OS
For cases where the operating system type is unavailable or contains an unknown or unexpected operating system type, this field displays as *NA*, UNKNOWN, or OTHER.
- RemoteMACAddr
- The peer virtual MAC address that is associated with this SMC-R link. This value applies to RNIC interfaces only.
- RemoteQP
- The peer QP value that is associated with this SMC-R link. This value applies to RNIC interfaces only.
- SMCLinkBytesIn
- Number of inbound data bytes transferred across this SMC-R or SMC-D link.
- SMCLinkInOperations
- Number of ISM inbound operations processed across this SMC-D link, or number of Remote Direct Memory Access (RDMA) inbound operations processed across this SMC-R link.
- SMCLinkBytesOut
- Number of outbound data bytes transferred across this SMC-R or SMC-D link.
- SMCLinkOutOperations
- Number of RDMA outbound operations processed across this SMC-R link, or number of ISM outbound operations processed across this SMC-D link.
- TCP Connections
- Number of TCP connections across this SMC-R or SMC-D link.
- Link Receive Buffer Inuse
- Amount of memory
buffer storage in use by the active TCP connections that are associated with this SMC-R or SMC-D
link.
- 32K Buffer Inuse
- Amount of 32K memory buffer storage in use by the active TCP connections that are associated with this SMC-R link. This field only applies to SMC-R links.
- 64K Buffer Inuse
- Amount of 64K memory buffer storage in use by the active TCP connections that are associated with this SMC-R or SMC-D link.
- 128K Buffer Inuse
- Amount of 128K memory buffer storage in use by the active TCP connections that are associated with this SMC-R or SMC-D link.
- 256K Buffer Inuse
- Amount of 256K memory buffer storage in use by the active TCP connections that are associated with this SMC-R or SMC-D link.
- Other Buffer Inuse
- For memory buffer storage that is allocated as buffers larger than 256K, the amount of these other buffers that are in use by the active TCP connections that are associated with this SMC-R or SMC-D link. If no buffers larger than 256K are allocated, this information is not displayed.
- The LOOPBACK device and link are displayed. The LOOPBACK6 interface is displayed if the stack is enabled for IPv6.
- The byte counts for number of bytes received and number of bytes transmitted are always 0 for VIPA links and interfaces.
- If an MTU was configured on the INTERFACE statement, then the actual MTU is the minimum of the configured MTU and the physical MTU value supported by the interface.
- No link-related information, packet trace settings, or BSD parameters are displayed for a device that has no link defined.
- The packet trace setting is displayed only when it is defined and set to ON.
- ATM specific information is displayed only for ATM devices that have links defined.
- OSA-Express Network Traffic Analyzer Information
- This section displays all currently defined OSA interfaces that
are dynamically created by VARY TCPIP,,OSAENTA commands or OSAENTA
PROFILE statements.
- OSA PortName
- The port name value of the OSA that is currently defined for performing the OSA-Express network traffic analyzer (OSAENTA) function. This value was specified on the PORTNAME parameter of a VARY TCPIP,,OSAENTA command or on an OSAENTA PROFILE statement. The following information is specific to this PortName value.
- OSA DevStatus
- The device status. The following list shows the possible values:
- Starting
- An OSAENTA ON command or statement has been processed and TCP/IP has sent an activation request to the data link control (DLC) layer.
- Sent SETUP
- DLC has acknowledged the TCP/IP activation request and TCP/IP has requested that DLC perform the initial I/O sequence with the device.
- Enabling
- DLC has acknowledged the TCP/IP activation request and TCP/IP has requested that DLC allow data connections to be established for the device.
- Connecting
- DLC has accepted the initial I/O sequence request.
- Negotiating
- The initial I/O sequence with the device is complete and TCP/IP is performing additional link-layer initialization.
- Ready
- The initialization sequence with the device is complete. The device is now ready.
- Deactivating
- DLC has performed the first stage of an orderly device deactivation.
- Not Active
- The device is not active. (The device has never been started or has been stopped after having been started.)
- OSA IntfName
- The name of the interface that is dynamically created to communicate with the OSA Express2 adapter.
- OSA IntfStatus
- The trace collection interface status. The following list shows
the possible values:
- Ready
- The OSA interface used for OSAENTA is accepting all trace requests from the host.
- Not Active
- The OSA interface that is used for OSAENTA is not active. Either trace collection is disabled or else an error occurred during activation of the OSA interface that is to be used for trace collection. Such an error condition generates an error message on the operator console.
- OSA Speed
- The speed reported by the interface (in millions of bits per second).
- OSA Authorization
- The value of the OSA HMC authorization parameter. Possible values
are Disabled, Logical Partition, PORT, CHPID, or UNKNOWN. The value
is set to UNKNOWN until the first OSAENTA ON command has completed.
- Disabled
- The OSA does not allow the NTA function to trace any frames for the OSA.
- Logical Partition
- The OSA allows the NTA function to trace frames only for the current logical partition.
- PORT
- The OSA allows the NTA function to trace frames for all stacks that share this OSA port.
- CHPID
- The OSA allows the NTA function to trace frames for all stacks that share the OSA.
- UNKNOWN
- The NTA trace interface has not been activated.
- OSAENTA Cumulative Trace Statistics
- Statistics accumulated for all frames that have been traced since
the OSAENTA interface was first activated. These values are not reset
by the OSAENTA ON command or statement.
- DataMegs
- The number of bytes of trace data (in megabytes) that have been received.
- Frames
- The total number of frames that have been traced.
- DataBytes
- The number of bytes of trace data that have been received.
- FramesDiscarded
- The number of frames that were traced but that the OSA device was not able to either forward to a host image or deliver outbound. These packets are available for formatting in the CTRACE SYSTCPOT component, but have not been delivered to any user.
- FramesLost
- The number of frames that could not be recorded by TCP/IP in the SYSTCPOT buffers.
- OSAENTA Active Trace Statistics
- Statistics that have accumulated since the OSAENTA ON command
or statement was last issued.
- DataMegs
- The number of bytes of trace data (in megabytes) that have been collected.
- Frames
- The total number of frames that have been collected.
- DataBytes
- The number of bytes of trace data that have been collected.
- FramesDiscarded
- The number of frames that were collected but that the OSA device was not able to either forward to a host image or deliver outbound. These packets are available for formatting in the CTRACE SYSTCPOT component, but have not been delivered to any user.
- FramesLost
- The number of frames that were not collected by TCP/IP in the SYSTCPOT buffers.
- TimeActive
- The number of minutes that have elapsed since the last OSAENTA ON command or statement.
- OSAENTA Trace Settings
- The current trace settings that are in effect for this OSAENTA
interface.
- Status
- The current trace status. Possible values are:
- ON
- Tracing is enabled.
- OFF
- Tracing is disabled.
- DataMegsLimit
- The amount of data (in megabytes) to be collected before the trace is automatically stopped. This value was specified on the DATA parameter.
- FramesLimit
- The number of frames to be collected before the trace is automatically stopped. This value was specified on the FRAMES parameter.
- TimeLimit
- The amount of time (in minutes) that data is collected before the trace is automatically stopped. This value was specified on the TIME parameter.
- Abbrev
- The size limit for the frames (in bytes) that are to be traced. This value was specified on the ABBREV parameter. This value can be modified to reflect the size limit set by the OSA.
- Discard
- Identifies which frames being discarded by the OSA-Express device are to be traced. This value was specified on the DISCARD parameter. Possible values are:
- All
- All frames discarded by the OSA-Express device are traced.
- Exception
- Frames discarded by the OSA-Express device for exception conditions are traced.
- None
- No discarded frames are traced.
- list
- A list of from one to eight values, that indicate the type of discarded frames that are to be traced by the OSA-Express device. This list includes decimal discard codes and the keyword parameter EXCEPTION.
- OSAENTA Trace Filters
- The values of the current accumulated filter variables from OSAENTA
commands or statements for this OSA. If a filter variable has not
been specified using OSAENTA commands or statements, then an asterisk
is shown.
- Nofilter
- The filtering behavior when all filters (DEVICEID, MAC, ETHTYPE, VLANID, IPADDR, PROTOCOL, and PORTNUM) have been cleared or are inactive. This behavior applies when no filters have been specified, if the CLEARFILTER parameter is specified, or when the current setting for every filter is an asterisk (*). This filtering behavior applies only to packets that were not discarded by the OSA-Express device. This value was specified on the NOFILTER parameter. Possible values are:
- All
- All frames are traced.
- None
- No frames are traced.
- DeviceID
- Up to eight hexadecimal device identifiers that are specified on the DEVICEID keyword of an OSAENTA command or statement. The value is an asterisk (*) if no device identifiers were specified.
- Mac
- Up to eight hexadecimal MAC addresses that are specified on the MAC keyword of an OSAENTA command or statement. The value is an asterisk (*) if no MAC addresses were specified.
- VLANid
- Up to eight decimal VLAN identifiers that are specified on the VLANID keyword of an OSAENTA command or statement. The value is an asterisk (*) if no VLAN identifiers were specified.
- ETHType
- Up to eight hexadecimal Ethernet types that are specified on the ETHTYPE keyword of an OSAENTA command or statement. The value is an asterisk (*) if no Ethernet types were specified. The name of the Ethernet type filter is displayed for commonly used Ethernet types, such as ARP, IPv4, IPv6, and SNA.
- IPAddr
- Up to eight dotted decimal IPv4 IP addresses and up to eight colon hexadecimal IPv6 IP addresses that are specified on the IPADDR keyword of an OSAENTA command or statement. The value is an asterisk (*) if no IP addresses were specified.
- Protocol
- Up to eight decimal protocol identifiers that are specified on the PROTOCOL keyword of an OSAENTA command or statement. The value is an asterisk (*) if no protocol identifiers were specified. The name of the protocol filter is displayed for commonly used protocols, while the protocol number is displayed for all others.
- PORTNum
- Up to eight decimal port numbers that are specified on the PORTNUM keyword of an OSAENTA command or statement. The value is an asterisk (*) if no port numbers were specified.
- SMCR Link Group Information
- The information of the SMC link group. This section is displayed
for each RNIC interface only when the SMC modifier or the
SMCID/-U filter is specified. The following fields are displayed:
- SMCLinkGroupId
- The group identifier that this TCP/IP stack dynamically creates to represent the SMC-R link group that includes this individual link.
- PNetID
- The physical network ID value that is configured in HCD for this SMC-R link group.
- Redundancy
- The recovery and load balancing capabilities of the link group.
The following list shows the possible values:
- Full
- The link group has redundant active SMC-R links. Both the local and remote stacks have full failover capability. The z/OS server performs load balancing of TCP connections across the SMC-R links that are members of the link group.
- Partial (Single local internal path)
- The link group has redundant active SMC-R links. Both the local and remote stacks have failover capability. The z/OS server performs load balancing of TCP connections across the SMC-R links that are members of the link group. However, the links on the local stack have the same internal path.
- Partial (Single local PCHID, unique ports)
- The link group has redundant active SMC-R links. Both the local and remote stacks have failover capability. The z/OS server performs load balancing of TCP connections across the SMC-R links that are members of the link group. However, the links on the local stack have the same PCHID with unique ports.
- Partial (Single local PCHID and port)
- The link group has redundant active SMC-R links. Both the local and remote stacks have failover capability. The z/OS server performs load balancing of TCP connections across the SMC-R links that are members of the link group. However, the links on the local stack have the same PCHID and port.
- Partial (Single local RNIC)
- The link group has multiple active SMC-R links and the remote stack has full failover capability, but the local stack has no failover capability. The z/OS server does not perform load balancing of TCP connections.
- Partial (Single remote RNIC)
- The link group has multiple active SMC-R links and the local stack has full failover capability, but the remote stack has no failover capability. The z/OS server does not perform load balancing of TCP connections.
- None (Single local and remote RNIC)
- The link group has a single active SMC-R link. Neither the local stack nor the remote stack has failover capability. The z/OS server cannot perform load balancing of TCP connections.
- Link Group Receive Buffer Total
- Amount of remote memory buffer (RMB) storage that is assigned
to this SMC-R link group.
- 32K Buffer Total
- Amount of 32K RMB storage that is assigned to this SMC-R link group.
- 64K Buffer Total
- Amount of 64K RMB storage that is assigned to this SMC-R link group.
- 128K Buffer Total
- Amount of 128K RMB storage that is assigned to this SMC-R link group.
- 256K Buffer Total
- Amount of 256K RMB storage that is assigned to this SMC-R link group.
- Other Buffer Total
- For RMB storage that is allocated as buffers larger than 256K, the amount of these other buffers that are assigned to this SMC-R link group. If no buffers larger than 256K are allocated, this information is not displayed.
- LocalSMCLinkId
- The link identifier this TCP/IP stack dynamically creates to represent the SMC-R link in this SMC-R link group.
- RemoteSMCLinkId
- The SMC-R link identifier that the remote peer uses to represent the link in this SMC-R link group. The value is provided to this TCP/IP stack during link activation.
- PNETID Report Specific Information
-
- Associated
- This field is displayed only for IPAQIQDC, IPAQIQDC6, ISM, and RNIC
interfaces. It indicates whether the interface is currently used for SMC or IQDC
communications for the PNETID value that is associated with the interface. The following values
are valid:
- Yes
- The interface is currently used for SMC or IQDC
communications for this PNETID.
- If IntfType is RNIC, the interface is used for SMC-R communications. At most two RNIC interfaces can actively be used for a given PNETID.
- If IntfType is ISM, the interface is used for SMC-D communications. The value of Associated is always YES for ISM interfaces with a non-null PNETID.
- If IntfType is IPAQIQDC and IPAQIQDC6, the interface is used for IQDC communications. The value of Associated is always YES for IQDC interfaces.
- No
- The interface is currently not used for SMC-R communications for this PNETID.
Unassociated ISM interfaces will have No for associated, but they are used for SMC-Dv2 communications.
- PChid
- The CHPID value that is associated with this interface.
- VChid
- The virtual channel ID value that is associated with this interface.