Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
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:

      set interface bond0

      set interface eth4 slave true master bond0

      set interface eth5 slave true master bond0

    • Configure custom routes using the following syntax

      set interface <interface> route <definitions>

      For details on how to properly set up routes and rules (including full syntax for route definitions), type, "help routing" in the system context.

    • To set the system hostname, use the following syntax:

      set hostname <hostname>

    • 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 management VIP by using the following syntax:

      set management-vip <ip>/<netmask>

      This will set the IP address as a floating IP address to be used by the management interfaces of the HA pair. The floating IP must be a valid IPv4 address and should include the netmask.

    • Configure the traffic VIP by using the following syntax:

      set traffic-vip <ip>/<netmask>

      This will set the IP address as a floating IP address used by traffic interfaces (all non-management interfaces). This IP will be used for regular application traffic. As with the management VIP, ensure the IP is a valid IPv4 address and be sure to include the netmask.

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

    • Configure the master address using the following syntax:

      set master-address <ip>

      After changing the address of the management interface of the master appliance in a clustered deployment, it becomes necessary to inform all nodes in a cluster of this new management address. Set the master address using this command on each node in a cluster individually.

    Published: 2015-02-04