Anyone else experienced issue with URL Redirection post migration?

[BrianMarks]

Previous RSA SecurID Authentication Manager 7.1 SP4 P5 [Enterprise Primary & Replica] has been migrated to RSA SecurID Authentication Manager 8.1 SP1 P13 successfully, now in Production. Generated a new RSA Replica and brought online. The Primary (ONLY) is experiencing the following issue:

Type URL: https://server-rsa01.fqdn.local

and the URL is redirected to: https://server-server-rsa01.fqdn.local:7004/console-ims/

and of course produces an error, "This site can’t be reached... server DNS address could not be found."

I am able to manually correct the FQDN in the redirected URL and successfully get to the login page, it is only the automated redirect that fails. Any thoughts on resolving this issue?

Also, this issue is NOT occurring on the Replica, which was built post migration.

[MHelmy]

Hi Brian,

I believe the FQDN of the primary server may be incorrectly configured on AM. Please try the below:

1. Login to the Operations Console > Administration > Network > Appliance Network Settings

2. Make sure the Fully Qualified Domain Name is correct, if not change it and save (any changes will prompt for rebooting the server).

If you still face the same behaviour (or if the FQDN was already correctly configured), make sure the DNS records are correct. Try using nslookup from your PC's cmd to check which IP address is registered server-rsa01.fqdn.local, then again nslookup that IP address to check which name are registered for that IP. Both outpust should be consistant (as in the below example, all FQDNs in Green  are the same, and all IPs in Blue are the same):

C:\Users\helmym1>nslookup server-rsa01.fqdn.local

Server:  dns.fqdn.local

Address:  10.10.10.10

Name:    server-rsa01.fqdn.local

Address:  192.168.2.30

C:\Users\helmym1>nslookup 192.168.2.30

Server:  dns.fqdn.local

Address:  10.10.10.10

Name:    server-rsa01.fqdn.local

Address:  192.168.2.30

Please let me know if the above is helpful or not.

[BrianMarks]

I have verified the AD DNS records and checked the configurations of the IPs and FQDNs on each box, all is correct. Forward & Reverse DNS worked properly prior to the migration, and continues to work properly after the migration. There are no host records. This issue can be duplicated from multiple Endpoints accessing the Administration in the manner described that are part of the domain and not. This does not occur on the Replica, only the Primary. We have had previous issues on this particular Primary Server with menu options missing. During the migration we did change platforms, migrate 7.x Windows to 8.x SUSE Linux 11.

[StevenSpicer]

Did you use the network tools menu on the Primary OC to check the addresses? Those run on the Primary, so you will see what the Primary thinks it is.  Try both nslookup and ping, they sometimes give different answers. You can run the commands on one of the Replicas as well to see what it thinks the Primary is.