In this section:
This section contains instructions to set multiple Secure Shell (SSH) IPs to access the HFE node and update the instances to add more SSH IPs.
Do not set REMOTE_SSH_MACHINE_IP to an IP if call traffic is originating from it, as it will break the HFE logic and block the traffic from reaching the SBC.
During orchestration, you can supply multiple IP addresses to the appropriate variable with a comma separated list. For example: 10.0.0.1,10.0.0.2,10.0.0.3.
The following tables outlines the variable to set depending on cloud and orchestration type:
Cloud Name | Orchestration Type | Variable Name |
---|---|---|
AWS | Manual Creation through console | REMOTE_SSH_MACHINE_IP (in user-data) |
Cloud Formation | remoteSSHMachinePublicIP | |
Terraform | remote_ssh_ip | |
GCP | Manual creation through console | REMOTE_SSH_MACHINE_IP (in startup script) |
Terraform | remote_ssh_ip | |
Azure | Manual Creation using CLI | REMOTE_SSH_MACHINE_IP (in customData) |
Terraform | remote_ssh_ip |
The following steps depict how to update the Remote SSH IPs for each public cloud.
These steps will cause network outages as the HFE requires a reboot to pick up the latest list.
Use the following steps to update the Remote SSH IP in the AWS console:
Edit the REMOTE_SSH_MAHCHINE_IP line. For example:
/bin/echo "REMOTE_SSH_MACHINE_IP=\"10.0.0.1,10.10.10.10\"">> $NAT_VAR
Click Save.
Use the following steps to update the Remote SSH IP in the GCP console:
In the value for startup-script edit the REMOTE_SSH_MACHINE_IP line. For example:
/bin/echo "REMOTE_SSH_MACHINE_IP=\"10.0.0.1,10.10.10.10\"">> $NAT_VAR
Azure does not support updating Custom Data after a VM is created. To update a HFE variable, use the following procedure:
Write the updated variable to /opt/HFE/natVars.user
. For example:
echo "REMOTE_SSH_MACHINE_IP=\"10.27.0.54,10.36.9.6\"" | sudo tee -a /opt/HFE/natVars.user
Reboot the HFE.
sudo reboot
/opt/HFE/natVars.user
will overwrite the values set for the variables in custom data.