Configuring basic Branch Gateway connectivity

Last Updated : Nov 09, 2023 |

About this task

You can run an installation script on a newly installed Branch Gateway to configure the basic network parameters required to achieve network connectivity. A remote technician can then further configure the gateway as required. Note that the installation script does not require running any CLI command.

Procedure

  1. Prepare a laptop with SSH client software.
  2. Set the laptop's TCP/IP properties as follows:
    • IP address: 192.11.13.5

    • Subnet mask: 255.255.255.252

    • Disable DNS service

    • Disable WINS Resolution

  3. Connect the laptop to the Branch Gateway Services (SVCS) port using an Ethernet cable.
  4. SSH to 192.11.13.6.
  5. At the prompt, enter the default username: root and password: root
  6. At the prompt, configure a new password.

    Follow the password complexity rules while setting a new password. For password rules, see Avaya Branch Gateway G430 CLI Reference

  7. At the Enhanced Access Security Gateway (EASG) prompt, read the following message:
    *****************************************************
    Enhanced Access Security Gateway (EASG) Confirmation.
    *****************************************************
    Please confirm whether Avaya is granted login access this system.
    You may change this setting any time after confirmation is completed.
    
    Enable EASG: (Recommended)
    By enabling Avaya Logins you are granting Avaya access to your system.
    This is necessary to maximize the performance and value of you Avaya
    support entitlements, allowing Avaya to resolve product issues in a
    timely manner.
    
    In addition to enabling the Avaya Logins, this product should be
    registered with Avaya and technically onboarded for remote connectivity
    and alarming. Please see the Avaya support site
    (support.avaya.com/registration) for additional information for
    registering products and establishing remote access and alarming.
    
    Disable EASG:
    By disabling Avaya Logins you are preventing Avaya access to your system.
    This is not recommended, as it impacts Avaya’s ability to provide support
    for the product. Unless the customer is well versed in managing the
    product themselves, Avaya Logins should not be disabled.
    Enter 1 to Enable EASG (Recommended) or 2 to Disable EASG? 1
    
  8. At the prompt, enter 1 or 2 to enable or disable EASG.
    The following message is displayed:
    Do you want to continue (Y/N)?
  9. At the prompt, enter Y to continue.
  10. At the prompt, enter Y to configure basic gateway connectivity.

    If you enter n, you can use the script-config CLI command to run the installation script, as long as you have not saved any configuration changes you may have made.

    If you need to configure the gateway in FIPS mode, enter n and run the command set fips-mode enable. The command will remove the existing configuration and resets the gateway. After the reset, repeat from step 4 above.

  11. Configure the following parameters:

    For each parameter, you can enter a value, or click Enter to accept the default value shown in square brackets:

    • VLAN number

    • IPv4 enabled or disabled

    • Static IPv4 address

    • IPv4 address for the primary management interface

    • IPv4 Subnet mask for the primary management interface

    • IPv4 address for the default gateway (router)

    • IPv6 enabled or disabled

    • IPv6 Unicast global address.

    • IPv6 prefix length

    • IPv6 Link local address

    • IPv6 PMI (Global or Link Local)

    • IPv6 Default gateway

    • Up to eight IP addresses (four IPv4 and four IPv6) to specify the Media Gateway Controllers

    • Hostname for the Branch Gateway

    The settings you configured are displayed, and you are prompted for confirmation.

    • If you confirm the settings, they are saved and the Branch Gateway reboots.

    • If you do not confirm the settings, you are prompted to re-configure them. If you enter y, the parameters are presented again for configuration.

  12. Connect the Ethernet port to the network to enable remote access to the Branch Gateway.

    A remote technician can now further configure the Branch Gateway using the CLI.