On Wednesday, 10/23/2002 at 03:18 ZE2, Robert Matthews
<[EMAIL PROTECTED]> wrote:
> I've just been required to change the IP addresses of all my Linux
virtual
> machines
> and their VM TCP/IP stack in order to transfer everything to a new
subnet. After
> starting the stack I find a PROFILE TCPERROR file on the TCPIP 191 disk
> containing
>
> DTCPAR113I BSD info for links:
>
> then for each link
>
> DTCPAR114I LNXxxx: BrdAddr . . . , DstAddr . . . , MaxMtu 0, Metric 0,
> SubnetMask . . .
>
> The information in the messages is correct but I'm worried by the fact
that I
> never
> had these messages before moving everything to the new subnet and the
fact that
> the "MaxMtu" is reported as 0. Unfortunately the messages are not
documented.
> Can anyone explain what's going on? TCP/IP is level 310 and I'm using
static
> routing with proxyarp.
>
> Bob Matthews,
> University of Geneva.

Bob, look at the console log.  Somewhere prior to this point is an error
message.  When the parser (DTCPAR) hits an error, it issues an error
message and then begins to disgorge everything it knows.  PROFILE TCPERROR
would be present only if you performed an OBEYFILE with errors in it, but
you would have also received a copy in your RDR.

Alan Altmark
Sr. Software Engineer
IBM z/VM Development

Reply via email to