friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/qtoclstphyifcdta.htm

2050 lines
61 KiB
HTML
Raw Permalink Blame History

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>List Physical Interface Data (QtocLstPhyIfcDta) API</title>
<!-- Begin Header Records -->
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<!-- Created for V5R1-->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!-- 050602 SGLEZ Made V5R4 changes -->
<!-- Edited by Sglez Jun 05 ========================================= -->
<!-- End Header Records ============================================= -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<a name="Top_Of_Page"></a>
<!--Java sync-link-->
<script type="text/javascript" language="Javascript" src="../rzahg/synch.js">
</script>
<h2>List Physical Interface Data (QtocLstPhyIfcDta) API</h2>
<div class="box" style="width: 60%;">
&nbsp;&nbsp;Required Parameter Group:<br>
<!-- iddvc RMBR -->
<br>
<table width="100%">
<tr>
<td align="center" valign="top" width="10%">1</td>
<td align="left" valign="top" width="50%">Qualified user space name</td>
<td align="left" valign="top" width="20%">Input</td>
<td align="left" valign="top" width="20%">Char(20)</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">Format name</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(8)</td>
</tr>
<tr>
<td align="center" valign="top">3</td>
<td align="left" valign="top">Error Code</td>
<td align="left" valign="top">I/O</td>
<td align="left" valign="top">Char(*)</td>
</tr>
</table>
<br>
&nbsp;&nbsp;Service Program: QTOCNETSTS<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: Yes<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The List Physical Interface
Data (QtocLstPhyIfcDta) API returns a list of physical interfaces and detailed
information about TCP/IP related data for each one. Depending on which output
format is requested, IPv4 and also IPv6 information can be requested for each
physical interface.</p>
<p>TCP/IP must be active on this system; otherwise error message TCP84C0 will
be issued.</p>
<br>
<h3>Authorities and Locks</h3>
<dl>
<dt><em>User Space Library Authority</em></dt>
<dd>*EXECUTE</dd>
<dt><em>User Space Authority</em></dt>
<dd>*CHANGE</dd>
<dt><em>User Space Lock</em></dt>
<dd>*SHRNUP</dd>
</dl>
<br>
<h3>Required Parameter Group</h3>
<dl>
<dt><strong>Qualified user space name</strong></dt>
<dd>INPUT; CHAR(20)
<p>The user space that receives the information, and the library in which it is
located. The first 10 characters contain the user space name, and the second 10
characters contain the library name. You can use these special values for the
library name:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*CURLIB</em></td>
<td align="left" valign="top">The job's current library.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*LIBL</em></td>
<td align="left" valign="top">The library list.</td>
</tr>
</table>
<br>
</dd>
<dt><strong>Format name</strong></dt>
<dd>INPUT; CHAR(8)
<p>The format of the space information to be returned. The format names
supported are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>IFCD0100</em></td>
<td align="left" valign="top">Basic physical interface data and detailed IPv4
specific data. Refer to <a href="#IFCD0100">IFCD0100 Format</a> for details on
the format.</td>
</tr>
<tr>
<td align="left" valign="top"><em>IFCD0200</em></td>
<td align="left" valign="top">Filter and IPSec Physical interface data. Refer
to <a href="#IFCD0100">IFCD0100 Format</a> and <a href="#IFCD0200">IFCD0200
Format</a> for details on the format.</td>
</tr>
<tr>
<td align="left" valign="top"><em>IFCD0300</em></td>
<td align="left" valign="top">Detailed IPv6 specific physical interface data.
Refer to <a href="#IFCD0100">IFCD0100 Format</a> and <a href=
"#IFCD0300">IFCD0300 Format</a> for details on the format.</td>
</tr>
</table>
<br>
</dd>
<dt><strong>Error Code</strong></dt>
<dd>I/O; CHAR(*)
<p>The structure in which to return error information. For the format of the
structure, see <a href="../apiref/error.htm#hdrerrcod">Error Code Parameter</a>.</p>
</dd>
</dl>
<br>
<h3>Format of Physical Interface Lists</h3>
<p>To request a list of TCP/IP data for all physical interfaces, use format
IFCD0100. For detailed information about Filter and IPSec physical interface
data in addition to the IFCD0100 format data, use format IFCD0200.</p>
<p>The physical interface description list consists of:</p>
<ul>
<li>A user area</li>
<li>A generic header</li>
<li>An input parameter section</li>
<li>A header section</li>
<li>A list data section:
<ul type="disc">
<li>IFCD0100 format.</li>
<li>IFCD0200 format.</li>
<li>IFCD0300 format</li>
</ul>
</li>
</ul>
<p>For details about the user area and generic header, see <a href=
"../apiref/usf.htm">User Space Format for List APIs</a>. For details about the remaining
items, see the following sections.</p>
<p>When you retrieve list entry information from a user space, you must use the
entry size returned in the generic header. The size of each entry may be padded
at the end. If you do not use the entry size, the result may not be valid. For
examples of how to process lists, see API <a href=
"../apiref/apiexmp.htm">Examples</a>.</p>
<h3>Input Parameter Section</h3>
<table border width="80%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">CHAR(10)</td>
<td align="left" valign="top" width="60%">User space name specified</td>
</tr>
<tr>
<td align="center" valign="top">10</td>
<td align="center" valign="top">A</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">User space library name specified</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Format name specified</td>
</tr>
<tr>
<td align="center" valign="top">28</td>
<td align="center" valign="top">1C</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
</table>
<br>
<br>
<h3>Header Section</h3>
<table border width="80%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">CHAR(10)</td>
<td align="left" valign="top" width="60%">User space name</td>
</tr>
<tr>
<td align="center" valign="top">10</td>
<td align="center" valign="top">A</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">User space library name used</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
</table>
<br>
<br>
<h3> <a name="FRCD">Format of
Returned Connection Data</a></h3>
<p>To retrieve basic Physical interface data, and IPv4 specific statistics
about each physical interface, use format <a href="#IFCD0100">IFCD0100</a>. To
retrieve IPv4 Filter and IPSec statistics about each physical interface, in
addition to format IFCD0100 information, use format <a href=
"#IFCD0200">IFCD0200</a>. To retrieve IPv6 specific information and statistics
about each physical interface, in addition to format IFCD0100 information, use
format <a href="#IFCD0300">IFCD0300</a>.</p>
<br>
<h3><a name="IFCD0100">IFCD0100 Format</a></h3>
<p>The following data about a physical interface is returned for the IFCD0100
format. For detailed descriptions of the fields in the table, see <a href=
"#IFCD0100_FIELD">Field Descriptions</a>.</p>
<table border width="80%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Line type</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Packet rules</td>
</tr>
<tr>
<td align="center" valign="top">8</td>
<td align="center" valign="top">8</td>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Total bytes received</td>
</tr>
<tr>
<td align="center" valign="top">16</td>
<td align="center" valign="top">10</td>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Total bytes sent</td>
</tr>
<tr>
<td align="center" valign="top">24</td>
<td align="center" valign="top">18</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total unicast packets received</td>
</tr>
<tr>
<td align="center" valign="top">28</td>
<td align="center" valign="top">1C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total non-unicast packets received</td>
</tr>
<tr>
<td align="center" valign="top">32</td>
<td align="center" valign="top">20</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total inbound packets discarded</td>
</tr>
<tr>
<td align="center" valign="top">36</td>
<td align="center" valign="top">24</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total unicast packets sent</td>
</tr>
<tr>
<td align="center" valign="top">40</td>
<td align="center" valign="top">28</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total non-unicast packets sent</td>
</tr>
<tr>
<td align="center" valign="top">44</td>
<td align="center" valign="top">2C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total outbound packets discarded</td>
</tr>
<tr>
<td align="center" valign="top">48</td>
<td align="center" valign="top">30</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Physical interface status</td>
</tr>
<tr>
<td align="center" valign="top">52</td>
<td align="center" valign="top">34</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Line description</td>
</tr>
<tr>
<td align="center" valign="top">62</td>
<td align="center" valign="top">3E</td>
<td align="left" valign="top">CHAR(17)</td>
<td align="left" valign="top">Physical address</td>
</tr>
<tr>
<td align="center" valign="top">79</td>
<td align="center" valign="top">4F</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Date - retrieved</td>
</tr>
<tr>
<td align="center" valign="top">87</td>
<td align="center" valign="top">57</td>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Time - retrieved</td>
</tr>
<tr>
<td align="center" valign="top">93</td>
<td align="center" valign="top">5D</td>
<td align="left" valign="top">CHAR(3)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">96</td>
<td align="center" valign="top">60</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to additional information</td>
</tr>
<tr>
<td align="center" valign="top">100</td>
<td align="center" valign="top">64</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of additional information</td>
</tr>
<tr>
<td align="center" valign="top">104</td>
<td align="center" valign="top">68</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Internet protocol version</td>
</tr>
<tr>
<td align="center" valign="top">108</td>
<td align="center" valign="top">6C</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
</table>
<br>
<br>
<h3><a name="IFCD0100_FIELD">Field Descriptions</a></h3>
<p><strong>Date - retrieved.</strong> Date when information is retrieved and
valid. Format: YYYYMMDD, where:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top">YYYY</td>
<td align="left" valign="top">Year</td>
</tr>
<tr>
<td align="left" valign="top">MM</td>
<td align="left" valign="top">Month</td>
</tr>
<tr>
<td align="left" valign="top">DD</td>
<td align="left" valign="top">Day</td>
</tr>
</table>
<p> <strong>Internet protocol
version.</strong> The version of the Internet Protocol (IP) that is currently
in use on this line.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">IPv4</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">IPv6</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">IPv4 &amp; IPv6</td>
</tr>
</table>
<p><strong>Length of additional information.</strong> The length in bytes of
additional information returned that is not part of format IFCD0100.</p>
<p><strong>Line description.</strong> Each TCP/IP interface is associated with
a physical network. This field displays the name of the communications line
description that identifies the physical network associated with an
interface.</p>
<p>The following special values may also be displayed:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*IPI</em> </td>
<td align="left" valign="top">This interface is used by Internet Protocol (IP)
over Internetwork Packet Exchange (IPX). A specific physical line is not
associated with an interface used by IP over IPX (IPI).
<p><strong>Note:</strong> As of V5R2,
IP over IPX is no longer supported.</p>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>*IPS</em> </td>
<td align="left" valign="top">The interface is used by Internet Protocol (IP)
over SNA. A specific physical line is not associated with an interface used by
IP over SNA (IPS).</td>
</tr>
<tr>
<td align="left" valign="top"><em>*LOOPBACK</em> </td>
<td align="left" valign="top">The interface is a loopback interface. Processing
associated with a loopback interface does not extend to a physical line. There
is no line description associated with a loopback address.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*VIRTUALIP</em> </td>
<td align="left" valign="top">The virtual interface is a circuitless interface.
It is used in conjunction with the associated local interface (LCLIFC) when
adding standard interfaces. This special value is used to accommodate any of
the following cases:
<ol>
<li>Load balancing. This is the means of having a fixed source IP address
regardless of which interface the traffic is being distributed.</li>
<li>Frame-relay multi-access network to define the local network IP address.
This allows for multiple virtual circuits to share the same IP network.</li>
<li>Alternate method of network access translation (NAT). This eliminates the
need for a NAT box by assigning a globally unique single IP address directly to
the box without the need to define an entire network.</li>
<li>Unnumbered networks. This provides a means of associating a local source IP
address for an unnumbered point-to-point network.</li>
</ol>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>*OPC</em> </td>
<td align="left" valign="top">This special value is used if you are adding an
OptiConnect interface over TCP/IP. This interface is attached to the optical
bus (OptiConnect).</td>
</tr>
<tr>
<td align="left" valign="top"><em>*TNLCFG64</em> </td>
<td align="left" valign="top">This special value means this line description is
a Configured 6-4 (IPv6 over IPv4) tunneling line. IPv6 Neighbor Discovery does
not work over a Configured tunnel, so you don't get the benefit of stateless
autoconfiguration.
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this value is no longer supported.
<img src="deltaend.gif" alt="End of change"></p></td>
</tr>
</table>
<p><strong>Line type.</strong> Type of line used by an interface. The following
link protocols are supported:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>-1</em> </td>
<td align="left" valign="top">OTHER -
<table cellpadding="5">
<tr>
<td align="left" valign="top">IPI - An Internet Protocol (IP) over Internetwork
Pack Exchange (IPX).
<br><strong>Note:</strong> As of V5R2,
IP over IPX is no longer supported.
</td>
<td align="left" valign="top">IPS - An Internet Protocol (IP) over SNA
interface.</td>
<td align="left" valign="top">WLS - Wireless local area network protocol.</td>
<td align="left" valign="top">TDLC - Twinaxial Datalink Control. Used for
TCP/IP over Twinax.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>-2</em> </td>
<td align="left" valign="top">NONE - Line is not defined. There is no line type
value for these interfaces.</td>
</tr>
<tr>
<td align="left" valign="top"><em>-3</em> </td>
<td align="left" valign="top">ERROR - This value is displayed if any system
errrors other than those for *NOTFND are received while trying to determine the
link type for an interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>-4</em> </td>
<td align="left" valign="top">NOTFND - Not found. This value is displayed if
the line description object for this interface cannot be found.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em> </td>
<td align="left" valign="top">ELAN - Ethernet local area network protocol.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em> </td>
<td align="left" valign="top">TRLAN - Token-ring local area network
protocol.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em> </td>
<td align="left" valign="top">FR - Frame relay network protocol.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em> </td>
<td align="left" valign="top">ASYNC - Asynchronous communications
protocol.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em> </td>
<td align="left" valign="top">PPP - Point-to-point Protocol.</td>
</tr>
<tr>
<td align="left" valign="top"><em>6</em> </td>
<td align="left" valign="top">X.25 - X.25 protocol.</td>
</tr>
<tr>
<td align="left" valign="top"><em>7</em> </td>
<td align="left" valign="top">DDI - Distributed Data Interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>8</em> </td>
<td align="left" valign="top">OPC - OptiConnect interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>9</em> </td>
<td align="left" valign="top">LOOPBACK - Loopback interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>10</em> </td>
<td align="left" valign="top">IPv6 Tunneling Line - Any kind of IPv6 over IPv4
tunnel.
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this value is no longer supported.
<img src="deltaend.gif" alt="End of change"></p></td>
</tr>
</table>
<p><strong>Offset to additional information.</strong> The offset in bytes to
the rest of the information if a format other than IFCD0100 is requested.</p>
<p><strong>Packet rules.</strong>Indicates what kind of packet rules data is
available for a particular line.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em> </td>
<td align="left" valign="top">None - No NAT and no filters are loaded for the
line specified.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em> </td>
<td align="left" valign="top">NAT - NAT is enabled for this line.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em> </td>
<td align="left" valign="top">Filters - Filters are defined for this line.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em> </td>
<td align="left" valign="top">NAT and Filters - NAT enabled and Filters
defined.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em> </td>
<td align="left" valign="top">Filters and IPSec - Filters and IPSec filters are
defined for this line.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em> </td>
<td align="left" valign="top">NAT and Filters and IPSec - NAT enabled and
Filters and IPSec filters defined.</td>
</tr>
</table>
<p><strong>Physical address.</strong> The MAC address of the interface. Format:
XX:XX:XX:XX:XX:XX, where 'X' is a hexadecimal digit.</p>
<p><strong>Physical interface status.</strong> The current operational state of
the physical interface (line).</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em> </td>
<td align="left" valign="top">Unknown - The status of this physical interface
is unknown.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em> </td>
<td align="left" valign="top">Active - The physical interface is
operational.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em> </td>
<td align="left" valign="top">Inactive - The physical interface is not
operational.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em> </td>
<td align="left" valign="top">Failed - The desired state of the physical
interface is active, but it is currently in the inactive state.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em> </td>
<td align="left" valign="top">Starting - The system is processing the request
to start this physical interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em> </td>
<td align="left" valign="top">Ending - The system is processing the request to
start this physical interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>6</em> </td>
<td align="left" valign="top">Recovery Pending - An error has been detected
with this physical interface and the system is recovering.</td>
</tr>
<tr>
<td align="left" valign="top"><em>7</em> </td>
<td align="left" valign="top">Recovery Canceled - An error has been detected
with this physical interface and system recovery has been canceled.</td>
</tr>
</table>
<p><strong>Reserved.</strong> An ignored field.</p>
<p><strong>Time - retrieved.</strong> Time when information is retrieved and
valid. Format: HHMMSS, in 24 hour time, where:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top">HH</td>
<td align="left" valign="top">Hour</td>
</tr>
<tr>
<td align="left" valign="top">MM</td>
<td align="left" valign="top">Minute</td>
</tr>
<tr>
<td align="left" valign="top">SS</td>
<td align="left" valign="top">Second</td>
</tr>
</table>
<p><strong>Total bytes received.</strong> The total number of bytes received on
the interface, including framing characters.</p>
<p><strong>Total bytes sent.</strong> The total number of bytes transmitted out
of the interface, including framing characters.</p>
<p><strong>Total inbound packets discarded.</strong> The number of inbound
packets which were chosen to be discarded even though no errors had been
detected to prevent their being deliverable to a higher-layer protocol. One
possible reason for discarding such a packet could be to free up buffer
space.</p>
<p><strong>Total non-unicast packets received.</strong> The number of
non-unicast (that is, broadcast or multicast) packets delivered to a higher-layer
protocol.</p>
<p><strong>Total non-unicast packets sent.</strong> The total number of packets
that higher-level protocols requested be transmitted to a non-unicast (that is,
broadcast or multicast) address, including those that were discarded or not
sent.</p>
<p><strong>Total outbound packets discarded.</strong> The number of outbound
packets which were chosen to be discarded even though no errors had been
detected to prevent their being transmitted. One possible reason for discarding
such a packet could be to free up buffer space.</p>
<p><strong>Total unicast packets received.</strong> The number of unicast
packets delivered to a higher-layer protocol.</p>
<p><strong>Total unicast packets sent.</strong> The total number of packets
that higher-level protocols requested to be transmitted to a unicast address,
including those that were discarded or not sent.</p>
<br>
<h3><a name="IFCD0200">IFCD0200 Format</a></h3>
<p>This format returns detailed Filter and IPSec Physical interface data in
addition to data about a physical interface from the IFCD0100 format. For
detailed descriptions of the fields in the table, see <a href=
"#IFCD0200_FIELD">Field Descriptions</a>.</p>
<table border width="80%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%"><br>
</td>
<td align="left" valign="top" width="60%">Returns everything from format
IFCD0100.</td>
</tr>
<tr>
<td valign="top" colspan="2" rowspan="35">Decimal and hexadecimal offsets are
reached by using the offset to additional information field in format
IFCD0100.</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Date - filter rules loaded or unloaded</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Time - filter rules loaded or unloaded</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound filter packets discarded</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound filter packets permitted</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound packets non-filtered</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound IPSec packets</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound IPSec packets discarded - no
connection</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound IPSec packets discarded - ondemand</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound IPSec packets discarded - VPN NAT</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound IPSec packets discarded - other</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound NAT packets</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound NAT packets discarded</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound packets discarded - other</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Outbound packets discarded - rule exception</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets permitted</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - no
connection</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - no AH/ESP</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - ondemand</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - VPN NAT</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - anti-replay
fail</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - selector
mismatch</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - mode
mismatch</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - authentication
error</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound IPSec packets discarded - other</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound NAT packets</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound filter packets discarded</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound filter packets permitted</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound packets non-filtered</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound packets discarded - other</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Inbound packets discarded - rule exception</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">NAT rules</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Filter rules</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">IPSec rules</td>
</tr>
</table>
<br>
<br>
<h3><a name="IFCD0200_FIELD">Field Descriptions</a></h3>
<strong>Date - filter rules loaded or unloaded.</strong>
<p>Date when the filter rules were most recently successfully loaded on or
unloaded from this interface. Format: YYYYMMDD, where:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top">YYYY</td>
<td align="left" valign="top">Year</td>
</tr>
<tr>
<td align="left" valign="top">MM</td>
<td align="left" valign="top">Month</td>
</tr>
<tr>
<td align="left" valign="top">DD</td>
<td align="left" valign="top">Day</td>
</tr>
</table>
<br>
<p>The following is a special value:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>00000000</em> </td>
<td align="left" valign="top">Rules have never been loaded since interface was
loaded.</td>
</tr>
</table>
<p><strong>Filter rules.</strong> Indicates whether filter rules exist on the
system. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em> </td>
<td align="left" valign="top">No filter rules exist.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em> </td>
<td align="left" valign="top">Filter rules exist.</td>
</tr>
</table>
<p><strong>Inbound IPSec packets.</strong> Total inbound IPSec packets (AH or
ESP) processed without error.</p>
<p><strong>Inbound IPSec packets permitted.</strong> Total inbound packets
permitted by pre-IPSec filters.</p>
<p><strong>Inbound IPSec packets discarded - authentication error.</strong>
Authentication error or failed.</p>
<p><strong>Inbound IPSec packets discarded - no connection.</strong> Total
inbound packets discarded because a VPN connection was not started.</p>
<p><strong>Inbound IPSec packets discarded - no AH/ESP.</strong> Total inbound
packets discarded because packet should have had a AH or ESP header, and did
not.</p>
<p><strong>Inbound IPSec packets discarded - ondemand.</strong> Total inbound
packets discarded due to a starting on-demand VPN connection.</p>
<p><strong>Inbound IPSec packets discarded - anti-replay fail.</strong> Total
inbound packets discarded due to failed anti-replay audit.</p>
<p><strong>Inbound IPSec packets discarded - mode mismatch.</strong> Total
inbound packets discarded because the mode (tunnel or transport) of the packet
did not match the mode of the VPN connection.</p>
<p><strong>Inbound IPSec packets discarded - other.</strong> Total inbound
packets discarded for other reasons, relating to IPSec.</p>
<p><strong>Inbound IPSec packets discarded - selector mismatch.</strong> Total
inbound packets discarded because the packet did not match the VPN connection
(selectors).</p>
<p><strong>Inbound IPSec packets discarded - VPN NAT.</strong> Total inbound
packets that could not be NAT'd because an IP address was not available from a
VPN NAT pool.</p>
<p><strong>Inbound NAT packets.</strong> Total inbound packets processed by
conventional NAT.</p>
<p><strong>Inbound filter packets discarded.</strong> Total inbound packets
discarded by filter action = DENY.</p>
<p><strong>Inbound filter packets permitted.</strong> Total inbound packets
permitted by filter action = PERMIT.</p>
<p><strong>Inbound packets non-filtered.</strong> Total inbound packets not
filtered (occurs only when no filters exist).</p>
<p><strong>Inbound packets discarded - other.</strong> Total inbound packets
discarded for some other reason.</p>
<p><strong>Inbound packets discarded - rule exception.</strong> Total inbound
packets discarded for exception reason.</p>
<p><strong>IPSec rules.</strong> Indicates whether IPSec filter rules exist on
the system. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em> </td>
<td align="left" valign="top">No IPSec filter rules exist.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em> </td>
<td align="left" valign="top">IPSec filter rules exist.</td>
</tr>
</table>
<p><strong>NAT rules.</strong> Indicates whether NAT rules exist on the system.
The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em> </td>
<td align="left" valign="top">No NAT rules exist.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em> </td>
<td align="left" valign="top">NAT rules exist.</td>
</tr>
</table>
<p><strong>Outbound filter packets discarded.</strong> Total outbound packets
discarded by filter action = DENY.</p>
<p><strong>Outbound filter packets permitted.</strong> Total outbound packets
permitted by filter action = PERMIT.</p>
<p><strong>Outbound packets non-filtered.</strong> Total outbound packets not
filtered (occurs only when no filters exist).</p>
<p><strong>Outbound IPSec packets.</strong> Total outbound IPSec packets (AH or
ESP) processed without error.</p>
<p><strong>Outbound IPSec packets discarded - no connection.</strong> Total
outbound packets that could not be handled by IPSec because a VPN connection
was not started.</p>
<p><strong>Outbound IPSec packets discarded - ondemand.</strong> Total outbound
packets discarded due to a starting on-demand VPN connection.</p>
<p><strong>Outbound IPSec packets discarded - other.</strong> Total outbound
packets that could not be handled for other reasons.</p>
<p><strong>Outbound IPSec packets discarded - VPN NAT.</strong> Total outbound
packets that could not be NAT'd because an IP address was not available from a
VPN NAT pool.</p>
<p><strong>Outbound NAT packets.</strong> Total outbound packets processed by
conventional NAT.</p>
<p><strong>Outbound NAT packets discarded.</strong> Total outbound packets that
could not be handled by masquerade NAT due to lack of available
conversation.</p>
<p><strong>Outbound packets discarded - other.</strong> Total outbound packets
discarded for some other reason.</p>
<p><strong>Outbound packets discarded - rule exception.</strong> Total outbound
packets discarded for exception reason.</p>
<p><strong>Reserved.</strong> An ignored field.</p>
<p><strong>Time - filter rules loaded or unloaded.</strong> Time when the
filter rules were most recently successfully loaded on or unloaded from this
interface. Format: HHMMSS, in 24 hour time, where:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top">HH</td>
<td align="left" valign="top">Hour</td>
</tr>
<tr>
<td align="left" valign="top">MM</td>
<td align="left" valign="top">Minute</td>
</tr>
<tr>
<td align="left" valign="top">SS</td>
<td align="left" valign="top">Second</td>
</tr>
</table>
<p>The following is a special value:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><strong>000000</strong></td>
<td align="left" valign="top">Rules have never been loaded since interface was
loaded.</td>
</tr>
</table>
<br>
<h3><a name="IFCD0300">IFCD0300
Format</a></h3>
<p>This format returns detailed IPv6 specific information and statistics for
each Physical interface, in addition to data about a physical interface from
the IFCD0100 format. For detailed descriptions of the fields in the table, see
<a href="#IFCD0300_FIELD">Field Descriptions</a>.</p>
<table border width="80%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%"><br>
</td>
<td align="left" valign="top" width="60%">Returns everything from format
IFCD0100.</td>
</tr>
<tr>
<td valign="top" colspan="2" rowspan="36">Decimal and hexadecimal offsets are
reached by using the offset to additional information field in format
IFCD0100.</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Packet rules - IPv6</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Total IPv6 bytes received</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">Total IPv6 bytes sent</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total IPv6 unicast packets received</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total IPv6 multicast packets received</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total IPv6 anycast packets received</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total inbound IPv6 packets discarded</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total IPv6 unicast packets sent</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total IPv6 multicast packets sent</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total IPv6 anycast packets sent</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Total outbound IPv6 packets discarded</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(25)</td>
<td align="left" valign="top">IPv6 interface identifier</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(8)</td>
<td align="left" valign="top">IPv6 interface identifier binary</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">MTU - configured</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">MTU - current</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Hop limit - configured</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Hop limit - current</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Use stateless autoconfig</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Use stateful address configuration</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Use other stateful configuration</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Accept router advertisements</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Accept redirects</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Neighbor discovery base reachable time -
configured</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Neighbor discovery base reachable time -
current</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Neighbor discovery reachable time</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Neighbor solicitation retransmit interval -
configured</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Neighbor solicitation retransmit interval -
current</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Duplicate address detection max transmits</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(15)</td>
<td align="left" valign="top">Local tunnel endpoint IPv4 address</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Local tunnel endpoint IPv4 address binary</td>
</tr>
<tr>
<td align="left" valign="top"><img src="delta.gif" alt="Start of change"> CHAR(50)</td>
<td align="left" valign="top">Text description</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Text description CCSID</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Autoconfig line status<img src="deltaend.gif" alt="End of change"></td>
</tr>
</table>
<br>
<br>
<h3><a name="IFCD0300_FIELD">Field Descriptions</a></h3>
<p><strong>Accept redirects.</strong> Whether the system is currently accepting
and using ICMPv6 Redirects that it receives on this physical interface.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">No - this interface is not accepting
redirects.
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, the physical interface will always accept redirects.
As a result, 0 will never be returned.
<img src="deltaend.gif" alt="End of change"></p>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Yes - this interface is accepting redirects.</td>
</tr>
</table>
<p><strong>Accept router advertisements.</strong> Whether the system is
currently accepting and using Router Advertisements that it receives on this
physical interface.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">No - this interface is not accepting router
advertisements.
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, the physical interface will always accept router advertisements.
As a result, 0 will never be returned.
<img src="deltaend.gif" alt="End of change"></p></td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Yes - this interface is accepting router
advertisements.</td>
</tr>
</table>
<p><strong><img src="delta.gif" alt="Start of change">
Autoconfig line status.</strong> Whether this physical interface is
currently using, not using, or is configured for stateless autonfig.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Autonfig is not active on this physical
interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Autonfig has been configured on this physical
interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Autonfig is active on this physical interface.
<img src="deltaend.gif" alt="End of change"></td>
</tr>
</table>
<p><strong>Duplicate address detection max transmits.</strong> The maximum
number of consecutive Neighbor Solicitation messages which will be sent using
this physical interface when TCP/IPv6 performs Duplicate Address Detection
(DAD) on a tentative address.</p>
<p>The following special value may be returned:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">This physical interface is currently configured
to not perform Duplicate Address Detection.</td>
</tr>
</table>
<p><strong>Hop limit - configured.</strong> The configured IPv6 Hop Limit value
specified for this physical interface. The Hop limit field is the IPv6
replacement for the IPv4 Time to live (TTL) field. The Hop limit value
specifies a relative limit on the number of hops across which an IPv6 datagram
remains active. The Hop limit value is hop count that is decremented by each
gateway to prevent internet routing loops. The default Hop limit value is 64.
Valid values range from 1 through 255 hops.</p>
<p><strong>Hop limit - current.</strong> The IPv6 Hop Limit value currently in
effect for this physical interface. The Hop Limit field is the IPv6 replacement
for the IPv4 Time to live (TTL) field. The Hop Limit value specifies a relative
limit on the number of hops across which an IPv6 datagram remains active. The
Hop Limit value is hop count that is decremented by each gateway to prevent
internet routing loops. The default Hop Limit value is 64. If the current Hop
Limit value differs from the configured Hop Limit value, then it has been set
by a Hop Limit value received in a Router Advertisement packet. Valid values
range from 1 through 255 hops.</p>
<p><strong>IPv6 interface identifier.</strong> A 64-bit number which is
combined with prefixes to create complete IPv6 addresses for the physical
interface. By default it is based on the link layer (MAC) address, if one
exists. The interface identifier is represented here in standard IPv6 address
format notation. It does not include a leading "::" for the first 64 bits of a
full IPv6 address, and it may include an embedded IPv4 address at the end. This
field is NULL padded.</p>
<p><strong>IPv6 interface identifier binary.</strong> Binary representation of
the IPv6 interface identifier.</p>
<p><strong>Local tunnel endpoint IPv4 address.</strong> The IPv4 address of the
local tunnel endpoint of this tunnel, returned in dotted decimal format. This
field is NULL padded.</p>
<p>The following special value may be returned:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0.0.0.0</em></td>
<td align="left" valign="top">This physical interface is not a tunnel, so this
field does not apply.
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, tunneling is not supported. As a result, this field is always set to 0.0.0.0.
<img src="deltaend.gif" alt="End of change"></p>
</td>
</tr>
</table>
<p><strong>Local tunnel endpoint IPv4 address binary.</strong> Binary
representation of the Local tunnel endpoint IPv4 address.</p>
<p>The following special value may be returned:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">This physical interface is not a tunnel
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, tunneling is not supported. As a result, this field is always set to 0.
<img src="deltaend.gif" alt="End of change"></p>
</td>
</tr>
</table>
<p><strong>MTU - configured.</strong> The configured maximum transmission unit
(MTU) value specified for this physical interface.</p>
<p>The following is a special value:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">LIND - The MTU was configured as *LIND, the MTU
value from the line description.</td>
</tr>
</table>
<p><strong>MTU - current.</strong> Maximum transmission unit (MTU) value
currently in effect for this physical interface.</p>
<p>The following is a special value:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">LIND - The interface is not active currently and
the MTU was configured as *LIND.</td>
</tr>
</table>
<p><strong>Neighbor discovery base reachable time - configured.</strong> The
configured Neighbor Discovery (ND) Base Reachable Time value, in seconds,
specified for this physical interface. The ND Base Reachable Time value is a
base time value used for computing the random ND Reachable Time value. The
default ND Base Reachable Time is 30 seconds. Valid values range from 10
through 100 seconds.</p>
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this field is always set to 30.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Neighbor discovery base reachable time - current.</strong> The
Neighbor Discovery (ND) Base Reachable Time value, in seconds, currently in
effect for this physical interface. The ND Base Reachable Time value is a base
time value used for computing the random ND Reachable Time value. The default
ND Base Reachable Time is 30 seconds. If the current ND Base Reachable Time
value differs from the configured value, then it has been set by a ND Base
Reachable Time value received in a Router Advertisement packet. Valid values
range from 10 through 100 seconds.</p>
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this field is always set to 30.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Neighbor discovery reachable time.</strong> The current Neighbor
Discovery (ND) Reachable Time value, in seconds, for this physical interface.
The ND Reachable Time value is the amount of time, in seconds, that a neighbor
is considered reachable after receiving a reachability confirmation. The ND
Reachable Time value is randomly calculated, using the ND Base Reachable Time
and a couple constants. This calculation is performed to prevent Neighbor
Unreachability Detection (NUD) messages from synchronizing with each other.</p>
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this field is always set to 0.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Neighbor solicitation retransmit interval - configured.</strong> The
configured Neighbor Solicitation (NS) Retransmit Interval value, in seconds,
specified for this physical interface. The NS Retransmit Interval is the time,
in seconds, between retransmissions of Neighbor Solicitation messages to a
neighbor when resolving the link-layer address, or when probing the
reachability of a neighbor. The default NS retransmit interval is 1 second.
Valid values range from 1 through 10 seconds.</p>
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this field is always set to 1.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Neighbor solicitation retransmit interval - current.</strong> The
Neighbor Solicitation (NS) Retransmit Interval value currently in effect for
this physical interface. The NS Retransmit Interval is the time, in seconds,
between retransmissions of Neighbor Solicitation messages to a neighbor when
resolving the link-layer address, or when probing the reachability of a
neighbor. The default NS Retransmit Interval is 1 second. If the current NS
Retransmit Interval value differs from the configured value, then it has been
set by a NS Retransmit Interval value received in a Router Advertisement
packet. Valid values range from 1 through 10 seconds.</p>
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this field is always set to 1.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Packet rules - IPv6.</strong> Indicates what kind of IPv6 packet
rules are loaded on a particular line.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">Other - An unknown Packet rules value.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">None - No NAT and no filters are loaded for the
line specified.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">NAT - NAT is enabled for this line.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Filters - Filters are defined for this line.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">NAT and Filters - NAT enabled and Filters defined
for this line.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">Filters and IPSec - Filters and IPSec filters are
defined for this line.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">NAT and Filters and IPSec - NAT enabled and
Filters and IPSec filters defined for this line.</td>
</tr>
</table>
<p><strong>Reserved.</strong> An ignored field.</p>
<p><img src="delta.gif" alt="Start of change"><strong>Text description.</strong> User
added text description associated with the physical interface.</p>
<p><strong>Text description CCSID.</strong> Coded character set ID for the text description.
<img src="deltaend.gif" alt="End of change"> </p>
<p><strong>Total inbound IPv6 packets discarded.</strong> The number of inbound
IPv6 packets which were chosen to be discarded even though no errors had been
detected to prevent their being deliverable to a higher-layer protocol. One
possible reason for discarding such a packet could be to free up buffer
space.</p>
<p><strong>Total IPv6 anycast packets received.</strong> The number of IPv6
anycast packets delivered to a higher-layer protocol.</p>
<p><strong>Total IPv6 anycast packets sent.</strong> The number of IPv6 anycast
packets that higher-level protocols requested be transmitted, including those
that were discarded.</p>
<p><strong>Total IPv6 bytes received.</strong> The total number of IPv6 bytes
received on the interface, including framing characters.</p>
<p><strong>Total IPv6 bytes sent.</strong> The total number of IPv6 bytes
transmitted out of the interface, including framing characters.</p>
<p><strong>Total IPv6 multicast packets received.</strong> The number of IPv6
multicast packets delivered to a higher-layer protocol.</p>
<p><strong>Total IPv6 multicast packets sent.</strong> The number of IPv6
multcast packets that higher-level protocols requested be transmitted,
including those that were discarded.</p>
<p><strong>Total IPv6 unicast packets received.</strong> The number of IPv6
unicast packets delivered to a higher-layer protocol.</p>
<p><strong>Total IPv6 unicast packets sent.</strong> The number of IPv6 unicast
packets that higher-level protocols requested be transmitted, including those
that were discarded.</p>
<p><strong>Total outbound IPv6 packets discarded.</strong> The number of
outbound IPv6 packets which were chosen to be discarded even though no errors
had been detected to prevent their being transmitted. One possible reason for
discarding such a packet could be to free up buffer space.</p>
<p><strong>Use other stateful configuration.</strong> Whether the TCP/IPv6
stack has been informed by a Router Advertisement to use non-address stateful
(that is, DHCPv6) configuration information that it receives on this physical
interface.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">UNKNOWN - The system has not received any Router
Advertisements on this physical interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">NO - The system has been informed to not use any
non-address stateful configuration information that it receives on this
physical interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">YES - The system has been informed to use any
non-address stateful configuration information that it receives on this
physical interface.</td>
</tr>
</table>
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this field is always set to 0.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Use stateful address configuration.</strong> Whether the TCP/IPv6
stack has been informed by a Router Advertisement to use stateful (that is, DHCPv6)
configuration information that it receives on this physical interface for the
purpose of address autoconfiguration.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">UNKNOWN - The system has not received any Router
Advertisements on this physical interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">NO - The system has been informed to not use
stateful configuration information that it receives on this physical interface
for the purpose of address autoconfiguration.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">YES - The system has been informed to use
stateful configuration information that it receives on this physical interface
for the purpose of address autoconfiguration.</td>
</tr>
</table>
<p><img src="delta.gif" alt="Start of change"><strong>Note:</strong>
As of V5R4, this field is always set to 0.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Use stateless autoconfig.</strong> Whether the TCP/IPv6 stack
performs stateless autoconfiguration on this physical interface or not.</p>
<p>Possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">NO - The system will not perform the stateless
autoconfig algorithms on this physical interface.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">YES - The system will perform the stateless
autoconfig algorithms on this physical interface.</td>
</tr>
</table>
<br>
<h3>Error Messages</h3>
<table width="100%" cellpadding="5">
<!-- cols="15 85" -->
<tr>
<th align="left" valign="top">Message ID</th>
<th align="left" valign="top">Error Message Text</th>
</tr>
<tr>
<td width="15%" valign="top">TCP84C0 E</td>
<td width="85%" valign="top">TCP/IP stack not active.</td>
</tr>
<tr>
<td align="left" valign="top">TCP84C5 E</td>
<td align="left" valign="top">API error providing TCP/IP Network Status list
information.</td>
</tr>
<tr>
<td align="left" valign="top">TCP84C6 E</td>
<td align="left" valign="top">Internal operations error - RESULT &amp;1 CC
&amp;2 RC &amp;3 ERRNO &amp;4.</td>
</tr>
<tr>
<td align="left" valign="top">CPF24B4 E</td>
<td align="left" valign="top">Severe error while addressing parameter
list.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C21 E</td>
<td align="left" valign="top">Format name &amp;1 is not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C90 E</td>
<td align="left" valign="top">Literal value cannot be changed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3CF1 E</td>
<td align="left" valign="top">Error code parameter not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF8100 E</td>
<td align="left" valign="top">All CPF81xx messages could be returned. xx is
from 01 to FF.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9801 E</td>
<td align="left" valign="top">Object &amp;2 in library &amp;3 not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9802 E</td>
<td align="left" valign="top">Not authorized to object &amp;2 in &amp;3.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9803 E</td>
<td align="left" valign="top">Cannot allocate object &amp;2 in library
&amp;3.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9807 E</td>
<td align="left" valign="top">One or more libraries in library list
deleted.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9808 E</td>
<td align="left" valign="top">Cannot allocate one or more libraries on library
list.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9810 E</td>
<td align="left" valign="top">Library &amp;1 not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9820 E</td>
<td align="left" valign="top">Not authorized to use library &amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9830 E</td>
<td align="left" valign="top">Cannot assign library &amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9872 E</td>
<td align="left" valign="top">Program or service program &amp;1 in library
&amp;2 ended. Reason code &amp;3.</td>
</tr>
</table>
<br>
<hr>
API introduced: V5R1
<hr>
<center>
<table cellpadding="2" cellspacing="2" align="center">
<tr align="center">
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
"comm.htm">Communications APIs</a> | <a href="aplist.htm">APIs by category</a>
</td>
</tr>
</table></center>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink