Troubleshooting
Problem
When TCPIP is configured for IPv4 only, all users are able to successfully connect to the TN3270 server. After the definitions to enable IPv6 communication (IPCONFIG6 and INTERFACE6 statements) are added, clients that then use IPv6 to connect fail. Other functions that communicate using IPv6 (FTP, PING) are successful.
Symptom
A MSG10 screen shows 'No LUs available now, please try later.' When the telnet DEBUG option is enabled, the following message appears at the console:
EZZ6035I TELNET TN3270 DEBUG CONN DETAIL
IP..PORT: aaaa:bbbb:cccc:dddd:eeee:ffff:gggg:hhhh..nnnn
CONN: iiiiiiii LU: MOD: EZBTPGLU
RCODE: 3004-00 LU is not available.
PARM1: 00000000 PARM2: 00000000 PARM3: 00000000
Cause
This system has LUMAPs defined based on the incoming client's address, and one of the following is occurring:
- It is using IPGROUPs, but the IPv6 addresses for the clients are not defined (only the IPv4 addresses).
- It is using HNGROUPs, but the reverse lookup table for the IPv6 addresses (PTR records for the appropriate ip6.arpa domain) has not been defined in the name server. This causes the name lookup performed by the server to fail, which means that no HNGROUP matches.
- It is using HNGROUPs, but the name returned for the IPv6 address of the client is not listed in an HNGROUP (it is different than the IPv4 name).
Resolving The Problem
- If using IPGROUPs, add the appropriate addresses/subnets to the IPGROUP statements.
- If using HNGROUPs, contact the DNS administrator to ensure that all clients' IPv6 addresses are defined in PTR records. Coordinate the names used with the HNGROUPs defined.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21458577