DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.


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.

Note

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.

Initial Orchestration

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 NameOrchestration TypeVariable Name
AWSManual Creation through consoleREMOTE_SSH_MACHINE_IP (in user-data)
Cloud FormationremoteSSHMachinePublicIP
Terraformremote_ssh_ip
GCPManual creation through consoleREMOTE_SSH_MACHINE_IP (in startup script)
Terraformremote_ssh_ip
AzureManual Creation using CLIREMOTE_SSH_MACHINE_IP (in customData)
Terraformremote_ssh_ip

Updating Remote SSH IPs

The following steps depict how to update the Remote SSH IPs for each public cloud.

Note
When you add a new Remote SSH Machine IP, make sure to supply the full list of IPs for which you need to creates routes, not just the new IP.

These steps will cause network outages as the HFE requires a reboot to pick up the latest list.

AWS

Use the following steps to update the Remote SSH IP in the AWS console:

  1. Select EC2.
  2. Select the HFE instance.
  3. Click Actions.
  4. Click Instance settings.
  5. Click Edit user data.

  6. 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

  7. Click Save.

  8. Stop instance and Start instance through Instance state for the changes to take affect.

GCP

Use the following steps to update the Remote SSH IP in the GCP console:

  1. Select Compute Engine.
  2. Select VM instances.
  3. Select the HFE instance.
  4. Click EDIT.
  5. Go to Custom metadata.

  6. 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
  7. Click Save.
  8. Click STOP and then START/RESUME for the changes to take affect.

Azure

Azure does not support updating Custom Data after a VM is created. To update a HFE variable, use the following procedure:

  1. Log on to the HFE node as rbbn user.

  2. 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

  3. Reboot the HFE.

    sudo reboot
Note
Any variable added to /opt/HFE/natVars.user will overwrite the values set for the variables in custom data.