EZZ8163I

Explanation
 The TCP/IP stack informed OMPROUTE that the specified
interface is defined to the stack.  The MTU value defined to the stack
for the interface is  not the same MTU value that is being used by
OMPROUTE for the interface.  
 In the message text: stack_name
The name of the TCP/IP stack.
stack_val
The MTU value that is defined to the stack for the interface.
interface
The name of the interface.
omproute_procname
The name of the OMPROUTE instance.
omproute_val 
The MTU value that is being used by OMPROUTE for the interface.

System action
 OMPROUTE continues.  All routes that are using
the specified interface that are added to the stack route table by
OMPROUTE will have the MTU value set to the value  that is being used
by OMPROUTE.

Operator response
 Contact the system programmer.

System programmer response
 Take one of the following actions
so that the stack and OMPROUTE will use the same  MTU value for the
interface:  If OMPROUTE is using the correct MTU value for the interface:
 Use the VARY TCPIP,,STOP command to stop the interface. 
Issue the VARY TCPIP,,OBEYFILE command with a profile that contains
an INTERFACE  DELETE statement for the interface, followed by an INTERFACE
DEFINE statement  for the interface that includes the correct MTU
value. 
Use the VARY TCPIP,,START command to start the interface.
(Optional) To make the change to the MTU value permanent in the
TCP/IP profile, modify the  INTERFACE statement that defines the interface
in the TCP/IP profile to specify  the value that is being used by
OMPROUTE.  
See IPAQENET OSA-Express QDIO  interfaces in z/OS Communications Server: IP Configuration
Reference for information about the INTERFACE  statement
in the TCP/IP profile.
 See VARY TCPIP,,START
or VARY TCPIP,,STOP in z/OS Communications Server: IP System Administrator's
Commands for information about the VARY TCPIP,,STOP
and VARY TCPIP,,START commands.  See VARY TCPIP,,OBEYFILE in z/OS Communications Server: IP System Administrator's
Commands for information about the VARY  TCPIP,,OBEYFILE
command.

If the stack is using the correct MTU value for the interface:  Modify any OSPF_INTERFACE, RIP_INTERFACE, and INTERFACE statements
that define the interface in the OMPROUTE configuration file to specify
the  value being used by the stack.
 If the interface is configured to OMPROUTE using a wildcard configuration
statement, you might need to explicitly configure this interface with
a separate configuration statement.
If this interface is not configured to OMPROUTE and you do not
want to add it  to the OMPROUTE configuration, modify the OMPROUTE
configuration file to include a GLOBAL_OPTIONS statement that specifies
 IGNORE_UNDEFINED_INTERFACES=YES.  See OMPROUTE
configuration file in z/OS Communications Server: IP Configuration
Reference for information about the OSPF_INTERFACE,
 RIP_INTERFACE, INTERFACE, and GLOBAL_OPTIONS statements in the OMPROUTE
 configuration file.
After you have made the appropriate changes to the OMPROUTE configuration
file, restart OMPROUTE.

User response
 Not applicable.

Problem determination
 See the system programmer response.

Source
 z/OS® Communications
Server TCP/IP: OMPROUTE

Module
 EZAORCFG, EZAORMII

Routing code
 10

Descriptor code
 12

Automation
 This message is displayed on the system console.
 You can use automation to issue an alert when the stack and OMPROUTE
are using different MTU values for  an interface.

Example
  EZZ8163I TCPCS1 MTU value 8992 for OSA1 differs from OMPROUT1 MTU value 5000