My question is , if the kepware is ok , that means the plc and network should be ok , but why ignition failed, how to set ignition successfully read the opc-ua tags?
Make sure you're entering the URL and not just the IP and port number. In your screenshot you only entered the IP and port without the opc.tcp:// prefix. That's required if I recall.
At this point, I'd check your logs and possibly even turn on debugging on whichever logger is generating the error to see if you can get any more detail on what the problem could be.
When testing Kepware, are you doing it from the Ignition server or another PC?
Your IP addresses suggest you have an oversized subnet unless you have a router or firewall between Ignition and your NATR device. 10.84.x.x and 10.90.x.x are at a minimum a /12 (255.240.0.0 subnet) with over 1 million usable IPs. If you are using a firewall or router between these and you're not testing Kepware from the Ignition server, I suspect you have a network issue. It could be routing (are all default gateways configured properly?) or a firewall blocking it.
On a separate note, if your subnet really is that large, I highly suggest rethinking your network architecture. That large of a subnet means you have a huge broadcast domain and if you're not having problems yet, you will eventually.
Ignition and Kepware Server are in the same server, if the network setting or PLC have issue, how can kepware read success without issue and ignition not able to read
That's the thread, not the log. Look in your live diagnostic logs, not the thread dump. If you're using the diagnostics bundle it will be in the wrapper.log file.
If you're not required to use v8.3.7 I'd suggest updating to v8.3.10 as there have been several updates regarding OPC-UA in the last several versions and it's possible they could fix things for you. Even if they don't you'll know you're on the latest version so if you reach out to support that is something they won't have to have you do as a troubleshooting step for them.