Network BrickStor SP is a network file sharing system so managing network configuration is important. Hub leverages basic networking configuration for configuring IP addresses, MTU and DNS. IP addresses To configure additional IP addresses, follow the steps below: Navigate to the Network Addresses page. Click Add Address. (Optional) Provide a Name. Choose a physical or virtual interface for this IP address using the Link field. Enter an IP address using a CIDR format in the Address field or choose a DHCP option. (Optional) Provide a VLAN ID. (Optional) Change the MTU. Auto will use the MTU of the underlying physical interface. (Optional) Add a route or a default gateway using Add Route. Click Add. To remove an unused IP address, follow the steps below: Removing an IP address will prevent network connectivity to the address, potentially causing a service outage or losing Hub access. Navigate to the Network Addresses page. Select the network interface or click the action cog () to the left of the interface. Select Remove. Enable/disable network interfaces Virtual interfaces can be enabled or disabled which can be useful in the troubleshooting situations. To enable or disable an interface, follow the steps below: Removing an IP address will prevent network connectivity to the address, potentially causing a service outage or losing Hub access. Navigate to the Network Addresses page. Select the network interface or click the action cog () to the left of the interface. Select Enable or Disable. Configure DNS BrickStor SP is highly dependent on DNS name resolution when used with identity services like LDAP, Active Directory, and Kerberos. Get DNS servers from DHCP To configure DNS servers from DHCP, follow the steps below: Navigate to the Network Addresses page. Click Configure DNS. Check Get DNS servers from DHCP. Configure DNS servers To configure DNS servers manually, follow the steps below: Navigate to the Network Addresses page. Click Configure DNS. Uncheck Get DNS servers from DHCP. Enter DNS servers in the DNS Servers field (one per line). (Optional) Enter DNS search domains in the Search Domain field. Click Next to display configuration summary and status of each DNS server. Click Apply. DNS lookup DNS lookup is the process of translating a domain name into an IP address. Hub provides a DNS lookup utility to test DNS name resolution. To perform a DNS lookup, follow the steps below: Navigate to the Network Addresses page. Click DNS Lookup. Enter a DNS name in the Search field. Choose a Type of DNS record to lookup. Choose a specific DNS server to use or all to use all configured DNS servers. Click Lookup. Aggregates To enhance performance and reliability multiple network interfaces can be bonded into a single logical aggregate. In order for this to work, the network switch ports must be configured accordingly. Most enterprise network switches support Link Aggregation Control Protocol (LACP) or 802.3ad link aggregation protocol therefore this is a preferred method for BrickStor SP. Static aggregates can also be used but only if instructed by RackTop support team. Create LACP aggregates BrickStor SP supports configuring LACP (802.3ad) aggregates being preferred link bonding method by RackTop. When creating LACP aggregates be sure to select preferred mode active or passive according to the network switch configuration. In active mode, a device actively initiates LACP negotiation by sending LACP PDUs to establish configuration and waits for responses. In passive mode, the device only waits for LACP PDUs and does not initiate the negotiation. LACP aggregates will only function if at least the BrickStor SP or the network switch is in active mode; it will not become operational if both sides are passive. LACP policy specifies the port selection policy to use for load spreading of outbound traffic. The policy specifies which network interface is used to send the packets. L2 Balances traffic based on source and destination MAC addresses. L3 Balances traffic based on source and destination IP addresses. L4 Balances traffic based on source and destination protocol, i.e., TCP/UDP port (default). L2,L4 Balances traffic using both MAC addresses and the protocol. To create an LACP aggregate, follow the steps below: Navigate to the Network Links page. Click the action cog () to the left of the desired network link and select Create Aggregate. (Optional) Enter a name for the aggregate. Select the proper LACP Policy according to the system configuration. Select active or passive for LACP Mode depending on the network switch configuration. The default is active. Select physical interface for this aggregate using Links checkboxes. 1 selection is allowed but 2 or more is ideal. Click Create. The network switch ports must be configured according to the LACP mode, timeout and the load spreading policy selection. Create static aggregates To create a static aggregate, follow the steps below: Navigate to the Network Links page. Click the action cog () to the left of the desired network link and select Create Aggregate. (Optional) Enter a name for the aggregate. Select off for LACP Mode. Select physical interface for this aggregate using Links checkboxes. 1 selection is allowed but 2 or more is ideal. Click Create. Manage aggregates To modify an existing BrickStor SP aggregate configuration such as policy, mode, add or remove aggregate interfaces, follow the steps below: Navigate to the Network Links page. Click the action cog () to the left of the desired aggregate and select Configure Aggregate. Modify the configuration as desired. Click Apply. Configure MTU MTU is the maximum size of a packet that can be sent over a network without fragmentation. The default MTU is 1500 bytes but it is commonly increased up to 9000 bytes for high throughput applications. Extra care should be taken when increasing the MTU as it can cause significant performance issues if not properly configured. To configure the MTU for a network interface, follow the steps below: Navigate to the Network Links page. Select the network interface to configure. Click Configure MTU. Choose Auto, 1500 or 9000. Click Apply. Auto is relevant to the virtual interface using the MTU of the underlying physical interface.