Network configuration

Table of contents

  1. FAQ
  2. Key features
  3. Network topology
  4. Network configuration
    1. Management network requirements
    2. Routing rules
    3. Basic network configuration
    4. NIC teaming
    5. VLANs
    6. IP routes
    7. NIC Status
  5. Date/Time
    1. NTP server synchronization
    2. Manual date and time
  1. FAQ

  2. Key features

  3. Network topology

  4. Network configuration

    1. Management network requirements

      TCP port 80 for HTTP trafic has to be opened to operate the system correctly.
      COMPANY_NAME also recommends to open TCP port 3389 for Remote Desktop connexion (for maintenance reasons).
    2. Best practices

      When working with a device having multiple network interfaces:
      • Avoid using all the NICs in the same subnet
      • Avoid specifying a gateway for more than one NIC
      • If usage of multiple gateways can't be avoided, add persistent routing rules to avoid packets sending out of the wrong network interface.
    3. Routing rules

      • Unicast trafic is always sent by following Operating System routing tables.
      • Multicast trafic is always received/sent from/to the selected ethernet interface.
    4. Basic network configuration

      From device "Network setup" panel, enable "DHCP" or change manually IP address, netmask, gateway, Preferred/Alternate DNS, and click on "Save pending changes" button.
    5. NIC teaming

      • NIC teaming allows multiple network adapters to be placed into a team to prevent connectivity loss in the event of a network component failure.
        Intel NIC Teaming ressources

        One Team:

        • Two physical plugs
        • One IP address
        • Managed by Intel's NIC controller
      • Teaming modes:

        • AFT (Adapter Fault Tolerant): Provides automatic redundancy for a server's network connection. A 'failed' primary adapter passes its MAC and Layer 3 address to the failover (secondary) adapter. All adapters in the team should be connected to the same hub or switch with Spanning Tree (STP) set to Off.
        • SFT (Switch Fault Tolerant): Uses two adapters connected to two switches and provides a fault tolerant network connection if the first adapter, its cabling, or the switch fails. Only two adapters can be assigned to an SFT team.
      • Teaming configuration:

        • From device "Team/VLAN" panel, click-on "Create SFT" or "Create AFT" button, select physical interfaces to include in the team and configure IP settings of the team.

          A new "teamed" interface is created. Original physical adapters are removed from the list.

          Click on "Save pending changes" button to apply changes.

        • To remove a Team, in "Team/VLAN" panel, click-on "Remove" button.
          From "Network Setup" panel, set IP settings of physical adapters removed from the team and click on "Save pending changes" button.
    6. VLANs

      • Virtual Local Area Network (VLAN) is a logical grouping of hosts. The grouping allows hosts to communicate as if they were on the same LAN, regardless of the physical topology of the network.
        COMPANY_NAME equipment supports "tagged" VLAN which are based on the IEEE 802.1Q specification. Each packet has a 4-byte tag added to the packet header. The switch must support IEEE 802.1Q tagging and be properly configured.
        Intel VLAN ressources
      • VLAN configuration :

        • From device "Team/VLAN" panel, click on "Create VLAN" button, select physical interface to tag, set VLAN tag number, configure IP settings of the new VLAN interface and click on "Create" button.

          A network adapter can be tagged several times. Teamed adapter can be tagged.


          Default VLAN interface is removed. A new taged interface is created.

          Click on "Save pending changes" button to apply changes.

        • To remove a tagged interface, in "Team/VLAN" panel, click-on "Remove" button.
          From "Network setup" panel, set IP settings of default VLAN interface and click on "Save pending changes" button.
    7. IP routes

      • Configuration

        Persistent routing rules can be added to sort out complex networking situation.

        From "IP Routes" panel, add custom route by setting desination IP, netmask, gateway and physical adapters. Click on "Add Route" and click on "Save pending changes" button.
      • Use case

        When a destination IP address (192.168.1.100) does not fall within the subnet of any NIC (10.3.1.1/16 and 10.4.1.1/16), then a default gateway is used to relay packets to the outside network. If multiple default gateways exist (10.3.1.254 for adapter_0 and 10.4.1.254 for adapter_1), then packets may be routed to the wrong outside network.

        Adding a permanent route forces packets with destination IP address 192.168.1.100 to be routed through gateway 10.3.1.254.
    8. NIC Status

      • Non teamed adapters

        • Link status : CONNECTED, NOT CONNECTED or ERROR
        • Link speed : 10Gb, 1Gb, 100Mb, 10Mb or 0Mb (if link is not connected)

        SNMP trap is sent when non teamed adapter status is updated.

      • Teamed adapters

        AFT/SFTP Teams status can be monitored from "Teaming Status" panel.

        When the team doesn't exist, teaming information is not available.
        When the team exists, there are 3 major states :
        • Team Status is OK : One Adapter Status is "Active" and the others are "Standby". All network adapters work correctly.
        • Team Status is WARNING : One of the Adapter Status is "Inactive". One of the network adapters doesn't work correctly but the system is still functional.
        • Team Status is ERROR : All Adapter Status are "Inactive". All network adapters are failing. The system is not functional.

        SNMP trap is sent when teamed adapter status is updated.

  5. Date/Time

    Device clock can be synchronized to a NTP server or configured manually.

    Date/Time settings can't be changed while channels are running. All channels must be stopped.