Configuring Network Settings Parent topic

You can use the management console to make changes to the network interface settings after the initial deployment.
You can configure the host name, the IPv4 addresses of the Deep Discovery Web Inspector appliance, and other network settings.
Note
Note
As part of the configuration, you can enable LACP and use trunked interfaces for data ingress and data egress. To deploy LACP link aggregation for Transparent Bridge or Transparent HA modes, the appliance must be equipped with two bypass cards. You must configure the connected switches with the corresponding LACP configuration.
See How LACP Works With Deep Discovery Web Inspector.

Procedure

  1. Go to Administration → System Settings → Network.
  2. Specify the general network settings that affect all interfaces.
    Option
    Description
    Host name
    Specify the host name.
    Gateway
    Specify the IPv4 address of the gateway.
    Primary DNS server and Secondary DNS server
    Specify the IPv4 addresses of the primary DNS server and optionally, the secondary DNS server.
  3. Specify the IPv4 address and subnet mask for the eth0 port:
    The eth0 interface handles management console traffic, SSH connections, Trend Micro updates, and other related Trend Micro traffic.
    eth0 is known as the:
    • Data and Management interface for the Forward Proxy deployment mode by default
    • Management interface for the Transparent Bridge deployment mode
    • Management interface for the Transparent HA deployment mode
  4. Specify the IPv4 address and subnet mask for the eth1 port if you plan on using a custom network for Virtual Analyzer sandbox instances to connect to the Internet.
    The eth1 interface is known as the dirty line port for Virtual Analyzer custom network connections. If Custom network is selected when configuring Virtual Analyzer network connections, Virtual Analyzer connects to the Internet using eth1, which is isolated from the management network.
  5. Specify the IPv4 address and subnet mask for other Ethernet interface ports that you will use in your deployment.
    The available ports will vary depending on the deployment mode and your particular deployment.
    Deployment Mode Port Information
    Forward Proxy
    • eth4: Dedicated interface for Authentication/Proxy service
    • Hide the configurations of unused network ports (eth2, eth3 and eth5)
    You can configure eth4 with static IP address.
    Transparent Bridge
    • eth2: Dedicated interface for Authentication service
    • eth4: Designated as eth4 — Data Ingress Port
    • eth5: Designated as eth5 — Data Egress Port
    • Hide the configuration of unused network port (eth3)
    Transparent HA
    • eth2: Dedicated interface for Authentication service
    • eth4: Designated as eth4 — Data Ingress Port
    • eth5: Designated as eth5 — Data Egress Port
    • Hide the configuration of unused network port (eth3)
    For Transparent HA, you can modify the br0 IP address and VLAN tag.
    Transparent Bridge with LACP trunks
    • eth2: Dedicated interface for Authentication service
    • eth4/eth6: Teamed to become the team0 interface
    • eth5/eth7: Teamed to become the team1 interface
    • Hide the configuration of unused network port (eth3)
    The teamed interfaces are used for data ingress/data egress.
    Transparent HA with LACP trunks
    • eth2: Dedicated interface for Authentication service
    • eth4/eth6: Teamed to become the team0 interface
    • eth5/eth7: Teamed to become the team1 interface
    • Hide the configuration of unused network port (eth3)
    The teamed interfaces are used for data ingress/data egress.
    You can modify the br0 IP address and VLAN tag.
  6. Click Save.
    When you save network changes, network services are restarted. After the restart, you must log on to the console again.