Configure the data and client networks

Edit online

For the network architecture that is shown in the figure below, the nut channel commands designate the channels (data and client). Then, the specific part of the network to be configured.

Figure 1. Example internal data storage and external client networks

Commands to configure an IBM Cloud Object Storage Accesser® appliance.

Warning: Entering incorrect routes will cause the system to freeze in edit mode unless the routes are deleted.


$ channel data port eth2, eth3
$ channel data bonding balanced
$ channel data ip 10.1.80.4
$ channel data netmask 255.255.255.0
$ channel client port eth4, eth5
$ channel client bonding balanced
$ channel client ip 192.168.240.4
$ channel client gateway 192.168.240.1
$ channel client netmask 255.255.255.0
$ route add 10.1.80.0/24 via 10.1.80.1 data

Commands to configure an IBM Cloud Object Storage Manager™ appliance.

$ channel data port eth2
$ channel data ip 10.1.80.50
$ channel data netmask 255.255.255.0
$ channel data gateway 10.1.80.1

Commands to configure the first Slicestor® Node (slicestor1).

$ channel data port eth2
$ channel data ip 10.1.80.5
$ channel data netmask 255.255.255.0
$ channel data gateway 10.1.80.1

Commands to configure the remote Slicestor® Node

$ channel data port eth2
$ channel data ip 10.1.81.11
$ channel data netmask 255.255.255.0
$ channel data gateway 10.1.80.1

⁴ Sends traffic that is destined for Accesser® Node and Slicestor® Node to the remote internal data storage network.

Note: When the channel, data, and client information are added into the nut configuration and activated, the appliance's routing table is automatically updated if a route does not exist. To verify the route, run the route -n command from a shell on the appliance.