Configure an SFP+ port

The Connect EZ 16/32 includes two SPF+ ports, to which you can connect an SFP+ transceiver module for fiber connection, such as the Finisar Network FTLX8574D3BCL SFP+.

Before you use the SFP+ ports, you must enable them and to any optional configuration.

Note Connect EZ 16/32  can support both a copper port and an SFP+ port at the same time. If an SFP+ port is enabled, the SFP+ port LED will illuminate if an SPF+ transceiver is installed, regardless of whether the optical/fiber cable is connected end-to-end.

Additional configuration items

To configure an SFP+ port:

 

  1. Log into Digi Remote Manager, or log into the local Web UI as a user with full Admin access rights.
  2. Access the device configuration:

    1. Locate your device as described in Use Digi Remote Manager to view and manage your device.
    2. Click the Device ID.
    3. Click Settings.
    4. Click to expand Config.

    1. On the menu, click System. Under Configuration, click Device Configuration.

      The Configuration window is displayed.

  3. Click Network > Interfaces , then SFP1 or SFP2.
  4. The SFP+ ports are disabled by default. To enable toggle on Enable.
  5. For Interface Type, select Ethernet. This is the default.
  6. For Zone, select Edge. This is the default.
  7. For Device, select a port: Device: SFP1 or Device: SFP2. The selection must match the SFP+ port you are configuring.

  8. The Connect EZ 16/32 can function as an 802.1x authenticator; it does not function as an 802.1x supplicant.

    1. Click to expand Authentication.
    2. Click Enable server to enable the 802.1x authenticator on the Connect EZ 16/32 device.
    3. Set the Reauth period.
  9. Configure IPv4 settings:
    1. Click to expand IPv4.

      IPv4 support is enabled by default.

    2. For Type, select Static IP addressDHCP address.
    3. For Address, type the IP address and subnet of the LAN interface. Use the format IPv4_address/netmask, for example, 192.168.2.1/24.
      1. Set the Metric.

        See Configure WAN/WWAN priority and default route metrics for further information about metrics.

      2. For Weight, type the relative weight for default routes associated with this interface. For multiple active interfaces with the same metric, Weight is used to load balance traffic to the interfaces.
      3. Set the Management priority. This determines which interface will have priority for central management activity. The interface with the highest number will be used.
      4. Set the MTU.
      5. For Use DNS, select one of the following:
        • Always: DNS will always be used for this WAN; when multiple interfaces have the same DNS server, the interface with the lowest metric will be used for DNS requests.
        • When primary default route: Only use the DNS servers provided for this interface when the interface is the primary route.
        • Never: Never use DNS servers for this interface.
      6. Enable DHCP Hostname to instruct the Connect EZ 16/32 device to include the device's system name with DHCP requests as the Client FQDN option. The DHCP server can then be configured to register the device's hostname and IP address with an associated DNS server.
        • See RFC4702 for further information about DHCP server support for the Client FQDN option.
        • See Configure system information for information about setting the Connect EZ 16/32 device's system name.
    5. Enable the DHCP server:
      1. Click to expand DHCP server.
      2. Click Enable.

      See DHCP servers for information about configuring the DHCP server.

    6. Enable Force link to keep the network interface active even when the device link is down.
  10. See Configure DHCP relay for information about configuring DHCP relay.
    1. Click to expand IPv6.
    2. Enable IPv6 support.
    3. For Type, select IPv6 prefix delegrationDHCPv6 address.
    4. For Prefix length, type the minimum length of the prefix to assign to this LAN. If the minimum length is not available, then a longer prefix will be used.
    5. For Prefix ID, type the identifier used to extend the prefix to the assigned length. Leave blank to use a random identifier.
    6. Set the Metric.

      See Configure WAN/WWAN priority and default route metrics for further information about metrics.

    7. For Weight, type the relative weight for default routes associated with this interface. For multiple active interfaces with the same metric, Weight is used to load balance traffic to the interfaces.
    8. Set the Management priority. This determines which interface will have priority for central management activity. The interface with the highest number will be used.
    9. Set the MTU.
    10. For Use DNS:
      • Always: DNS will always be used for this WAN; when multiple interfaces have the same DNS server, the interface with the lowest metric will be used for DNS requests.
      • When primary default route: Only use the DNS servers provided for this interface when the interface is the primary route.
      • Never: Never use DNS servers for this interface.
    11. Enable DHCP Hostname to instruct the Connect EZ 16/32 device to include the device's system name with DHCP requests as the Client FQDN option. The DHCP server can then be configured to register the device's hostname and IP address with an associated DNS server.
      • See RFC4702 for further information about DHCP server support for the Client FQDN option.
      • See Configure system information for information about setting the Connect EZ 16/32 device's system name.

  12. Incoming packets will be dropped from any devices whose MAC addresses is included in the MAC address denylist.

    1. Click to expand MAC address denylist.
    2. For Add MAC address, click .
    3. Type the MAC address.

  13. If allowlist entries are specified, incoming packets will only be accepted from the listed MAC addresses.

    1. Click to expand MAC address allowlist.
    2. For Add MAC address, click .
    3. Type the MAC address.
  14. See Configure SureLink active recovery to detect WAN/WWAN failures for information about configuring SureLink.
  15. Click Apply to save the configuration and apply the change.
  1. Select the device in Remote Manager and click Actions > Open Console, or log into the Connect EZ 16/32 local command line as a user with full Admin access rights.

    Depending on your device configuration, you may be presented with an Access selection menu. Type admin to access the Admin CLI.

  2. At the command line, type config to enter configuration mode:

    > config
(config)>

  3. Navigate to the SFP+ port you want to configure.
    (config)> network interface sfp1 
(config network interface sfp1)>
  4. Enable the SFP1 port.
    (config network interface sfp1)>enable true
(config network interface sfp1)>
  5. Set the interface type.
    (config network interface sfp1)>type ethernet
(config network interface sfp1)>
  6. Set the appropriate firewall zone:
    (config network interface sfp1)>zone edge
(config network interface sfp1)>
  7. Set the device.
    (config network interface sfp1)>/network/device/sfp1
(config network interface sfp1)>
  8. Configure IPv4 settings:
    • IPv4 support is enabled by default. To disable:
      (config network interface my_wan)> ipv4 enable false
(config network interface my_wan)>
    • Configure the WAN to be a DHCP clientThe WAN is configured by default to use a static IP address for its IPv4 configuration. To configure the WAN to be a DHCP client, rather than using a static IP addres:
      (config network interface my_wan)> ipv4 type dhcp
(config network interface my_wan)>

      These instructions assume that the LAN will use a static IP address for its IPv4 configuration.

    1. Set the IPv4 address and subnet of the LAN interface. Use the format IPv4_address/netmask, for example, 192.168.2.1/24.
      (config network interface my_lan)> ipv4 address ip_address/netmask
(config network interface my_lan)>
      1. Set the IP metric:
        (config network interface my_wan)> ipv4 metric num
(config network interface my_wan)>

        See Configure WAN/WWAN priority and default route metrics for further information about metrics.

      2. Set the relative weight for default routes associated with this interface. For multiple active interfaces with the same metric, the weight is used to load balance traffic to the interfaces.

        (config network interface my_wan)> ipv4 weight num
(config network interface my_wan)>
      3. Set the management priority. This determines which interface will have priority for central management activity. The interface with the highest number will be used.
        (config network interface my_wan)> ipv4 mgmt num
(config network interface my_wan)>
      4. Set the MTU:
        (config network interface my_wan)> ipv4 mtu num
(config network interface my_wan)>
      5. Configure how to use DNS:
        (config network interface my_wan)> ipv4 use_dns value
(config network interface my_wan)>

        where value is one of:

        • always: DNS will always be used for this WAN; when multiple interfaces have the same DNS server, the interface with the lowest metric will be used for DNS requests.
        • primary: Only use the DNS servers provided for this interface when the interface is the primary route.
        • never: Never use DNS servers for this interface.

      6. Enable DHCP Hostname to instruct the Connect EZ 16/32 device to include the device's system name with DHCP requests as the Client FQDN option. The DHCP server can then be configured to register the device's hostname and IP address with an associated DNS server.
        (config network interface my_wan)> ipv4 dhcp_hostname true
(config network interface my_wan)>
        • See RFC4702 for further information about DHCP server support for the Client FQDN option.
        • See Configure system information for information about setting the Connect EZ 16/32 device's system name.
    3. Enable the DHCP server:
      (config network interface my_wan)> ipv4 dhcp_server enable true

      See DHCP servers for information about configuring the DHCP server.

    1. Enable IPv6 support:
      (config network interface my_wan)> ipv6 enable true
(config network interface my_wan)>
    2. Set the IPv6 type to DHCP:
      (config network interface my_wan)> ipv6 type dhcpv6
(config network interface my_wan)>
    3. Generally, the default settings for IPv6 support are sufficient. You can view the default IPv6 settings by using the question mark (?):
      (config network interface my_wan)> ipv6 ?

IPv6

 Parameters                Current Value
 -------------------------------------------------------------------------------
 dhcp_hostname             false              DHCP Hostname
 enable                    true               Enable
 metric                    0                  Metric
 mgmt                      0                  Management priority
 mtu                       1500               MTU
 type                      dhcpv6             Type
 use_dns                   always             Use DNS
 prefix_id                 1                  Prefix ID
 prefix_length             48                 Prefix length
 type                      prefix_delegation  Type
 weight                    10                 Weight

 Additional Configuration
 -------------------------------------------------------------------------------
 connection_monitor        Active recovery
 dhcpv6_server             DHCPv6 server

(config network interface my_wan)>

      View default settings for the IPv6 DHCP server:

      (config network interface my_wan)> ipv6 dhcpv6_server ?

DHCPv6 server: The DHCPv6 server settings for this network interface.

 Parameters                Current Value
 -------------------------------------------------------------------------------
 enable                    true           Enable

(config network interface my_wan)>
    4. Modify any of the remaining default settings as appropriate. For example, to change the metricminimum length of the prefix:
      (config network interface my_wan)> ipv6 metric 1prefix_length 60
(config network interface my_wan)>

      If the minimum length is not available, then a longer prefix will be used.

      See Configure WAN/WWAN priority and default route metrics for further information about metrics.

  10. Note The Connect EZ 16/32 can function as an 802.1x authenticator; it does not function as an 802.1x supplicant.

    1. Enable the 802.1x authenticator on the Connect EZ 16/32 device:
      (config network interface my_wan)> 802_1x authentication enable true
(config network interface my_wan)>
    2. Set the frequency period for reauthorization:
      (config network interface my_wan)> 802_1x authentication reauth_period value
(config network interface my_wan)>

      3. where value is an integer between 0 and 86400. The default is 3600.

  11. Incoming packets will be dropped from any devices whose MAC addresses is included in the MAC address denylist.

    1. Add a MAC address to the denylist:
      (config network interface my_wan)> add mac_denylist end mac_address
(config network interface my_wan)>

      where mac_address is a hyphen-separated MAC address, for example, 32-A6-84-2E-81-58.

    2. Repeat for each additional MAC address.

  12. If allowlist entries are specified, incoming packets will only be accepted from the listed MAC addresses.

    1. Add a MAC address to the allowlist:
      (config network interface my_wan)> add mac_allowlist end mac_address
(config network interface my_wan)>

      where mac_address is a hyphen-separated MAC address, for example, 32-A6-84-2E-81-58.

    2. Repeat for each additional MAC address.
  13. See Configure SureLink active recovery to detect WAN/WWAN failures for information about configuring SureLink for active recovery.
  14. Save the configuration and apply the change.
    (config network interface my_wan)> save
Configuration saved.
>
  15. Type exit to exit the Admin CLI.

    Depending on your device configuration, you may be presented with an Access selection menu. Type quit to disconnect from the device.