NAS SMB Interfaces

You can control which IP addresses or network interfaces the Appliance Controller uses to publish or bind the SMB server, which allows you to restrict access and optimize network behavior.

Note: These commands are node-specific and not cluster-aware. You must individually configure each node.

This command allows you to display the current interface settings.

Example:

> nas show smb interfaces

SMB interfaces are not set using defaults: eth0 eth1

This command allows you to force the SMB server to only listen on a specified interface.

Note: This option is not available in cluster mode as it might disrupt fail-over functionality.

Example:

> nas set smb bind interfaces eth0

Setting SMB Bind interfaces: lo eth0 ...

Applying localsam configuration settings ...

Checking SMB interface list: lo eth0

Checking SMB interface 'eth0:10.65.182.140' status ...

Successfully configured SMB Bind interfaces: lo eth0 ...

 

> nas show smb interfaces

SMB interfaces are bound

SMB bind interfaces: lo eth0

This command allows you to prevent the SMB server from advertising an interface (for example, management networks) as a valid SMB path. This is especially useful in the following scenarios:

  • SMB multichannel configurations

  • Avoiding multi-homed Windows clients from creating redundant paths

Note: This command does not bind the interface; in other words, the connections through other IP addresses (for example, VIPs) remain active.

Example:

> nas set smb network interfaces eth1

Setting SMB Network interfaces: eth1 ...

Applying localsam configuration settings ...

Successfully configured SMB Network interfaces: eth1 ...

Other nodes in cluster are unaffected.

 

> nas show smb interfaces

SMB interfaces are not bound

SMB network interfaces: eth1

This command allows you to reset the SMB interface configuration to its default settings, which includes all primary interfaces.

Example:

> nas reset smb interfaces force

Resetting SMB Network interfaces to defaults...

Applying localsam configuration settings ...

Successfully reset SMB Network interfaces to defaults...

Other nodes in cluster are unaffected.

 

> nas show smb interfaces

SMB interfaces are not set using defaults: eth1 eth0

  • This situation could be the result of an Appliance Controller upgrade issue, specifically if you used the system upgrade or system upgrade local command to upgrade a node that is joined to a NAS cluster. In this case, reboot the node to repair the configuration. This removes the errant daemons and updates the config files for the new configuration.

    If rebooting the cluster node does not resolve the issue, or if the issue isn't related to an upgrade, then review the following information.

  • The Samba server may not be connected to the correct interface or IP address — it needs to be bound to the same interface or IP address as your Appliance Controller's network is.

    To resolve this issue, you will need to verify that the Samba server is connected appropriately. If the Samba server is not bound to the correct interface or IP address, you will need to reset its connection.

  1. Log in to the Appliance Controller CLI.
  2. Verify that Samba is connected to the IP address configured for your Appliance Controller's network. Enter:

    3. nas show smb interfaces detail

    Example:

    > nas show smb interfaces detail

    SMB bind interfaces: lo 10.65.190.178

  1. Log in to the Appliance Controller CLI.
  2. Configure the SMB interface.
    • Bind the server to listen only to certain IP(s) in a multichannel SMB configuration. Enter:
      • nas set smb interfaces <interface> [, <interface>, ...]

      Example (listen to two IP addresses):

      nas set smb interfaces lo 192.168.10.10 192.168.11.10

    The parameter is:

    <interface>

    The interface, such as eth0, to which to reset the Samba server's connection.

    You can enter wildcards (*) with the interface name, such as eth*. In addition, you can enter multiple interfaces in a single command.

    Caution: Using the net set smb inferfaces command can be incompatible with the use of a VIP pool. If you are using a VIP pool, clear the setting by entering an empty value for the <interface> parameter.