We are upgrading CER from V9.0 to V11.5.2.20000-6. CER Publisher upgraded successfully, where as the subscriber failed. We involved TAC and they said subscriber is crashed and we need to rebuild it from scratch. We were given CER 10.5 OVA template. We chose 20000 User deployment and tried installing CER subscriber with the same security password as the Publisher (at least 10 times); however, the installation fails at network connectivity validation to Publisher. It throws an error saying Publisher might be down, incorrect security password, subscriber not added into Publisher, etc. We have verified all of those things, in fact changed security password multiple times on Publisher with TAC on call, still the same issue persisted. As Publisher and Subscriber are in different UCS (NY and DE), we then tried installing subscriber on the same UCS as Publisher with same subnet IP with new DNS entry, still it threw same error. We did'nt want to ruin the Publisher, so we built a test Publisher (using 10.5 OVA) and test subscriber in two UCS servers same as original cluster with same subnet IP, still the same issue persists. It has been 2 weeks now and we are running on a Stand-alone publisher. Multiple TAC engineers have worked on this case, but no fruitful outcome yet. Then we built 10.5 and 9.0 Publisher in test environment, even then subscriber installation fails with same error. We have verified every aspect that cause the issue, such as NTP, reverse and forward DNS, firewall, security password, not giving a lengthy password, not enabling DNS, same UCS with same subnet IP, everything. Network guys say they see TCP packet aged out between Pub and Sub on firewall. If anyone can help us to get out of this issue, it would be very great.
