Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    The CLI: The Set Command

    The set command allows you to set the various local system network settings.

    Note: The following commands imply you are already in the system context in the cli.

    • Configure Network Interfaces–The syntax for setting network interface attributes is as follows:

      set interface <interface> <attr1> <value1> <attr2> <value2> ... <attrN> <valueN>

      The settings will not take affect immediately and will require a restart of the interface to actually take affect. You may set multiple attributes on a single interface at one time. The available attributes can be see by using the tab completion when setting an interface.

    • Configure an Alias Interface–Specify the interface using the following format:

      set interface <physical interface>:<alias number>

      For example, if you are configuring the first alias on physical device eth0, then the interface you would give would be eth0:0.

    • Configure a Vlan Tagged Interface–Specify the interface using the following format:

      set interface <physical interface>:<vlan id>

      You must also need to set the vlan attribute to true.

    • Configure a Bonded Interface–Specify the interface using the following format:

      set interface bond<bond number>

      Configure the bond interface itself as you would any other interface , where <bond_number> is the number to assign to the bond name. For each physical interface that will be a part of the bond you will need to set the slave attribute to true and set the master attribute to the bond interface. For example:

      cli system set interface bond0

      cli system set interface eth4 slave true master bond0

      cli system set interface eth5 slave true master bond0

    • Configure Hostname Resolution–Use the following syntax:

      set dns nameservers <servers>

      set dns domain <domain>

      set dns search <search>

      These settings let you configure how hostnames are resolved by the local system. If you provide multiple nameservers to use for DNS resolution, they should be separated by a command and given in the order of priority.

    • Configure System HTTP Proxy–Use the following syntax:

      set proxy <protocol>://[<username>:<password>@]<host>:<port>

      To setup a HTTP or HTTPS proxy to use for the local system you would provide the proxy information in the above format. The <protocol> will determine which one the proxy is used for, and you can optionally specify a username and password to be used for connecting to the proxy.

    • Configure the Management Interface–Specify the interface using the following format:

      set management-interface <interface>

      Sets the management interface for the local system. All management traffic and internode communications will be restricted to the given interface. The only exception to this is HA replication traffic. The replication traffic will only happen on the interconnect.

    • Configure the HA Management VIP–Use the following syntax:

      set management-vip <ip>/<netmask>

      Set the floating IP address to be used by the management interfaces of the HA pair. The floating IP address must be a valid IPV4 address and should include the netmask to be used.

    • Configure the HA Traffic VIP(s)–Use the following syntax:

      set traffic-vip <name> <ip>/<netmask>

      Add a floating IP address to be used by the HA pair for handling of application traffic.

    • Configure the Interface Monitor–Use the following syntax:

      set ethmonitor <interface>

      Set a network interface to be monitored for availability. If the given interface is detected to be down, then a failover event will occur with the HA pair.

    • Specify a custom IP route and/or rule - Use the following format:

      system set interface <interface> route <route definition>

      system set interface <interface> rule <rule definition>

      To allow complete IP routing customizability, WebApp Secure allows administrators to define custom routing rules and routes. Using the above format, you can apply specific routing behavior to any interface so you can better handle any routing issue that may arise. Once added, they should be listed with the interface when running system show interfaces. The routes/rules do not take affect immediately; they require a restart of the network service the same as any other network interface change. After restarting the network service you can verify that the routes/rules have taken affect with the commands ip route list and ip rule list. For information on how to define route and rule definitions, exit the CLI and type ip route help and ip rule help from the WebAppSecure bash prompt

    Published: 2014-06-27