Forum Discussion
Altocumulusgtm_add Error in AWS
Hi All, I just stood up two new DNS devices in AWS, BIG-IP 15.0.1 Build 0.0.11 Final, and I'm running into an error when attempting to run the gtm_add command on the 2nd device. I have TCP 22 and 4353 opened up between the devices but I receive the following error. Does anyone have suggestions? I opened a support case and the sent me a work around to try (K13823) but I'm wondering if there is another way. I'd really like to get the gtm_add command to work instead. Thanks Gang!
[admin@f5-external2:Active:Standalone] ~ # gtm_add admin@xx.xx.xx.xxx
WARNING: Running this script will wipe out the current configuration
files (bigip_gtm.conf, named.conf and named zone files) on the BIG-IP GTM
Controller on which this script is run. The configuration will be
replaced with the configuration of the remote BIG-IP GTM Controller
in the specified sync group
The local BIG-IP GTM MUST already be added in the configuration of the
other GTM.
NOTE: The current master key of this BIG-IP will be changed to match the
master key of the remote BIG-IP GTM.
The BIG-IP config will be saved via:
tmsh save sys config
after the master key is changed.
Are you absolutely sure you want to do this? [y/n] y
Enter admin password if prompted
Password:
Syntax Error: command history is only available in shell mode
ERROR: Can't read remote cert via /usr/bin/ssh -o UserKnownHostsFile=/home/admin/.ssh/known_hosts .
[admin@f5-external2:Active:Standalone] ~ #
Simon_BlakelyEmployee
The account you have used to log into the remote device (admin) has logged into the TMOS shell (tmsh), and not into BASH.
The gtm_add script requires BASH as the login shell.
Try using root as the login.
Dave311Thanks S Blakely! In AWS, root is disabled but thanks to your answer I changed the admin user to default to advanced shell (bash) and that allowed the script to run with admin. Both data centers showed up in the BIG-IP DNS VM I ran the gtm_add command in. However, both BIG-IP DNS VM's show the remote data center as blue availability and syncing is not working. Not sure why. Was expecting both data centers to be green and sync to work. Will keep digging. Thanks again.