Network Configuration (BUI)

Language:

When using the BUI to reconfigure networking, the system makes every effort to preserve the current networking connection to your browser. However, some network configuration changes such as deleting the specific address to which your browser is connected, will unavoidably cause the browser to lose its connection. For this reason it is recommended that you assign a particular IP address and network device for use by administrators and always leave the address configured. You can also perform particularly complex network reconfiguration tasks from the CLI over the serial console if necessary.

The following icons are used in the Configuration > Network section:

Table 15 Network Configuration Icons

Icon	Description
	Add new datalink, interface, or route
	Edit datalink, interface, or route settings
	Editing disabled
	Destroy datalink, interface, route
	Destruction disabled
	Drag-and-drop icon
	Connected network port
	Connected network port with I/O activity
	Disconnected network port (link down, cable problem)
	Active InfiniBand port
	Active InfiniBand port with I/O activity
	Inactive InfiniBand port (down, init, or arm state)
	InfiniBand partition device is up
	InfiniBand partition device is down (subnet manager problem)
	Network datalink
	Network datalink VLAN or VNIC
	Network datalink aggregation
	Network datalink aggregation VLAN or VNIC
	Network datalink IB partition
	Interface is being used to send and receive packets (either up or degraded)
	Interface has been disabled by the user
	Interface is offline (owned by the cluster peer)
	Interface has failed or has been configured with a duplicate IP address

At top right is local navigation for Configuration, Addresses and Routing, which display alternate configuration views.

The Configuration page is shown by default, and lists Devices, Datalinks, and Interfaces, along with buttons for administration. Hover over an entry to expose an additional image:Image showing the move icon icon, and click on any entry to highlight other components that are associated with it.

The Devices list shows links status on the right, as well as an icon to reflect the state of the network port. If ports appear disconnected, check that they are plugged into the network properly.

To configure an IP address on a network devices, first create a datalink, and then create an interface to use that datalink. The image:Image showing the add icon icon may be used to do both, which will display dialogs for the Datalink and Interface properties.

There is more than one way to configure a network interface. Try clicking on the move icon image:Image showing the move icon for a device, then dragging it to the datalink table. Then drag the datalink over to the interfaces table. Other moves are possible. This can be helpful for complex configurations, where valid moves are highlighted.

This page shows a summary table of the current network configuration, with fields:

Table 16 Summary of the Current Network Configuration

Field	Description	Example
Network Datalink	Datalink name and detail summary	datalink1 (via igb0)
Network Interface	Interface name and details summary	IPv4 DHCP, via datalink1
Network Addresses	Addresses hosted by this interface	192.168.2.80/22
Host Names	Resolved host names for the network addresses	caji.sf.example.com

This page provides configuration of the IP routing table and associated properties, as discussed above. By default, all entries in the routing table are shown, but the table can be filtered by type by using the subnavigation bar.

To check a specific route, in the CLI use traceroute.

zfssa-source:> traceroute 10.80.198.102
traceroute: Warning: Multiple interfaces found; using 10.80.198.101 @ igb3
traceroute to 10.80.198.102 (10.80.198.102), 30 hops max, 40 byte packets 
1 10.80.198.1 (10.80.198.1) 6.490 ms 0.924 ms 0.834 ms 
2 10.80.198.102 (10.80.198.102) 0.152 ms 0.118 ms 0.099 ms
zfssa-target:> traceroute 10.80.198.101
traceroute: Warning: Multiple interfaces found; using 10.80.198.102 @ igb3
traceroute to 10.80.198.101 (10.80.198.101), 30 hops max, 40 byte packets 
1 10.80.198.1 (10.80.198.1) 1.031 ms 0.905 ms 0.769 ms
2 10.80.198.101 (10.80.198.101) 0.158 ms 0.111 ms 0.109 ms