Explanation
This message is the first message in a group of
messages displayed when the dialing of an Enterprise Extender (HPR/IP)
connection fails because the remote IP address is not in the same
IP address family as the local IP address; for instance, the remote
IP address is an IPv4 address and the local is an IPv6 address. If
the addresses are in different family types, the Enterprise Extender
connection cannot be established. A complete description of the message
group follows the example.
IST1891I line ACTIVATION FAILED - MISMATCH OF IP ADDRESS FAMILIES
IST1680I type IP ADDRESS ip_address
[IST1909I REMOTE HOSTNAME value]
[IST1911I value]
IST1680I type IP ADDRESS ip_address
[IST1910I LOCAL HOSTNAME value]
[IST1911I value]
IST314I END
IST1680I - type is either LOCAL or REMOTE to identify
the IP address displayed.
- ip_address is either the remote IP address
or the local IP address. The first instance of IST1680I will display
the remote IP address, and the second instance of IST1680I will display
the local IP address. If ip_address is ****NA****,
it means that the remote node is using IPv6 protocols but the local
connection is using IPv4 protocols.
IST1891I - line is the name of the Enterprise Extender
(HPR/IP) connection that failed.
IST1909I - value is the host name, owned by a target
remote node, that was used to acquire the remote IP address as part
of name-to-address resolution. If the host name is longer than 44
characters, then the first 44 characters are displayed as value and
the remaining characters are displayed in one or more IST1911I messages.
IST1910I - value is the host name used to acquire the
local static VIPA address used as part of the attempted route determination.
If the host name is longer than 45 characters, then the first 45 characters
are displayed as value and the remaining characters
are displayed in one or more IST1911I messages.
IST1911I - value is the continuation of value on
IST1909I or IST1910I. IST1911I is repeated as many times as necessary
to display the entire character string.
System action
Activation of the Enterprise Extender (HPR/IP)
connection failed.
Operator response
System programmer response
The Enterprise Extender connection
cannot activate if the local and remote IP addresses are not in the
same address family. The IP addresses can be obtained from the following
sources:
- For both predefined and connection network Enterprise Extender
connections, the local IP address (ip_address on the IST1680I instance
with type LOCAL) is obtained from one of the following:
- The TCP/IP stack identified on the TCPNAME start option.
- The IPADDR start option, or the IPADDR operand on the XCA major
node GROUP definition statement associated with the Enterprise Extender
connection network or predefined Enterprise Extender connection used
for the failed route attempt, when IST1910I is not displayed.
- The name-to-address resolution of value on IST1910I, which represents
either the value supplied as the HOSTNAME start option, or the value
specified as the HOSTNAME operand on the XCA major node GROUP definition
statement associated with the Enterprise Extender connection network
or predefined Enterprise Extender connection used for the failed route
attempt.
- For predefined Enterprise Extender connections, the remote IP
address (ip_address on the IST1680I instance with type REMOTE) is
obtained from one of the following:
- The IPADDR operand on the PATH statement, when IST1909I is not
displayed.
- The name-to-address resolution of value on IST1909I, which represents
the value specified as the HOSTNAME operand on the PATH definition
statement.
- For connection network Enterprise Extender connections, the remote
IP address (ip_address on the IST1680I instance with type REMOTE)
is obtained from one of the following:
- The IPv4 address provided by the remote Enterprise Extender node
in the APPN Route Selection Control Vector (RSCV) describing the
session route to use, when IST1909I is not displayed.
- The name-to-address resolution of value on IST1909I, which represents
the host name provided by the remote Enterprise Extender node in
the APPN Route Selection Control Vector (RSCV) describing the session
route to use.
Ensure that one of the following is true:
- The local or remote address was specified correctly.
- The correct local or remote host name, or both, have been used
for name-to-address resolution.
- For an EE Connection Network, verify that all nodes are defining
identical EE Connection Network names with an IP address from the
same IP address family.
Routing code
Descriptor code