Configuring Data Plane Network Settings Using the CLI

You can configure the data plane (DP) network settings through the command line interface (CLI) by connecting to the DP instance via SSH or console. The following procedures cover DNS, interface mode, IP addressing, static routes, DHCP/NAT profile binding, and syslog configuration.
Before you begin:
  • Ensure the data plane you want to edit is approved/managed by the controller and is online.
  • Have the DP management IP address along with the admin password and enable password.
  • Confirm that the DP has the required DHCP/NAT licenses if you plan to enable those services.

Accessing the Global Configuration Mode in the CLI

Controller-level configuration is performed via the CLI in Global configuration mode. Complete the following steps to access the Global configuration mode of the DP CLI:
  1. Connect to the DP CLI. For instructions to connect to the DP CLI, refer to Accessing the Data Plane CLI.
  2. After you connect to the DP CLI, enter the username admin and the password.
  3. After successful login, enter the commands enable (followed by the enable password) and config to access the Global configuration mode.
The following example accesses the Global configuration mode of the DP CLI using the Windows Command Prompt:
C:\Users\Administrator>ssh admin@192.168.200.250
The authenticity of host '192.168.200.250 (192.168.200.250)' can't be established.
ECDSA key fingerprint is SHA256:GGBvIIIRaQDISBtOkRGSYx7h9XN7FkkiN2KhKF1lpnw.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.200.250' (ECDSA) to the list of known hosts.
################################
#       Welcome to vSZ-D       #
################################
admin@192.168.200.250's password:
Welcome to the RUCKUS WIRELESS vSZ-D Command Line Interface
vDP-2> enable
Password:
vDP-2# config
vDP-2(config)#

Configuring the IP Address of the Controller

You can change the IP address of the controller that the Data Plane (DP) is pointing to.
Attention: Changing the IP address of the controller a DP is pointing to, requires a reboot of the DP.
Complete the following steps to change the controller IP address configured on the DP:
  1. From the Global configuration mode, enter the command controller to enter the Controller configuration mode.
  2. Enter the ip controller_ip-address command with the IP address of the controller, or enter the ip FQDN command if a DNS entry has been configured.
    Note: Make sure the DP and the controller can reach each other through the network.
  3. Type end to exit the Controller configuration mode and save the changes.
  4. Enter the reboot command followed by y to reboot the DP.
The following example configures the controller’s IP address, saves the configuration, and reboots the DP so that the changes take effect.
vDP-1# config
vDP-1(config)# controller
vDP-1(config-controller)# ip 192.168.110.78
The command was executed successfully. To save the changes, type 'end'.
vDP-1(config-controller)# end
Changed vSZ address to 192.168.110.78!
Please reboot to take effect!
Save changes, and then exits the config context.
vDP-1# reboot
Are you sure you want to reboot vSZ-D[y/n]?

Configuring the Interface IP addressing

The Data Plane (DP) consists of different network interfaces including the Management interface, Data interface, and the Access/Core separation.
Complete the following steps to configure the different DP network interfaces using the CLI.
  1. From the Global configuration mode, enter the interface command followed by the management, data, or access-core-separate keyword to access the interface configuration context.
  2. Within the interface configuration context, enter the command ip address followed by the IP address and subnet mask.
  3. Optionally, enter the vlan vlan_number command to configure a VLAN tag for the interface.
  4. Enter the end command to exit the Global configuration mode and save the changes.
    Note: The Core interface does not require you to specify a default gateway IP address, hence, the command used to configure this interface is ip address ip_address subnet_mask. On the other hand, the Management and Data interfaces do require the default gateway be specified, requiring use of command syntax ip address ip_address subnet_mask default_gateway.

The following example configures the Core interface with a static IP address:

vDP-2(config)# interface access-core-separate
vDP-2(config-core-separate)# ip address 192.168.30.250 255.255.255.0
The command was executed successfully. To save the changes, type 'end'.
vDP-2(config-core-separate)# end
job 14 at Fri Sep  5 04:33:00 2025
Save changes, and then exits the config context.
vDP-2#

The following example configures the Core interface with a DHCP IP address:

vDP-2(config)# interface access-core-separate
vDP-2(config-core-separate)# ip address dhcp
The command was executed successfully. To save the changes, type 'end'.
vDP-2(config-core-separate)# end
job 15 at Fri Sep  5 04:43:00 2025
Save changes, and then exits the config context.
vDP-2#

The following example configures the Management interface:

vDP-2(config)# interface management
vDP-2(config-interface)# ip address 192.168.200.250 255.255.255.0 192.168.200.253
The command was executed successfully. To save the changes, type 'end'.
vDP-2(config-interface)# end
job 17 at Fri Sep  5 04:53:00 2025
Save changes, and then exits the config context.
vDP-2#

Execute the command show interface from the Privileged EXEC mode to verify the current configuration for all the interfaces:

vDP-2# show interface
Configure Management interface:
  proto: static
  address:192.168.200.250
  netmask:255.255.255.0
  gateway:192.168.200.253

Configure Data interface:
  proto: static
  vlan: 55
  address:192.168.55.250
  netmask:255.255.255.0
  gateway:192.168.55.253

Configure access core separate interface:
  proto: static
  address:192.168.30.250
  netmask:255.255.255.0

Current Management interface:
  address:192.168.200.250
  netmask:255.255.255.0

Current Data interface:
  address:192.168.55.250
  netmask:255.255.255.0

Current Access Core Separate interface:
  address:192.168.30.250
  netmask:255.255.255.0

Adding Static Routes

Static routes are required when the DP must reach destinations outside its directly connected subnets (for example, upstream DHCP relay or tunnel endpoints).
Complete these steps to add a static route:
  1. From the Privileged EXEC mode, enter the command route, to enter the route configuration context.
  2. In the route configuration context, enter the command add dest_address subnet_mask next_hop.
  3. Type end to save the configuration changes and exit the route configuration context.
The following example configures a route for the destination host address 10.10.0.1 establishing as the next hop the IP address 192.168.30.253:
vDP-2# route
vDP-2(route)# add 10.10.0.1 255.255.255.0 192.168.30.253
vDP-2(route)# end
job 19 at Fri Sep  5 05:03:00 2025
vDP-2#

Configuring Syslog for DHCP and NAT Logs

You can enable Syslog messages for tracing DHCP and NAT activities, allowing you to configure an external server and enabling the service for DHCP or NAT individually.
Complete the following steps to configure a Syslog server that receives DHCP and NAT logs from the DP:
  1. From the Global configuration mode, enter the command syslog to enter the Syslog configuration context and enter the following:
    • Enter the dhcp enable command to enable syslog for DHCP.
    • Enter the nat enable command to enable syslog for NAT.
    • Enter the syslog-server command with the variables server_IP udp_port to specify the server IP address and port.
    The following example configures the Syslog server IP address 3.2.2.2 with the UDP port 514, and enables syslog for DHCP and NAT:
    vDP-2(config)# syslog
    vDP-2(config-syslog)# syslog-server 3.2.2.2 514
    vDP-2(config-syslog)# dhcp enable
    vDP-2(config-syslog)# nat enable
    vDP-2(config-syslog)# end
    Save changes and notify datacore to read new configure file
    vDP-2(config)#
    Use the command show within the Syslog configuration context to display the current information:
    vDP-2(config-syslog)# show
    syslog server ip: 3.2.2.2
    syslog server port: 514
    syslog server dhcps: enable
    syslog server nat: enable
  2. (Optional) Configure the Syslog level for DHCP and NAT activities. Choose one of the following:
    • Updating DHCP Syslog level.
      1. From the Global configuration mode, enter the dhcp command to enter the DHCP configuration mode.
      2. From the DHCP configuration mode, enter the dhcp-log-syslog level 1-7 command to select the Syslog level to be sent to the Syslog server.
    • Updating NAT Syslog level.
      1. From the Global configuration mode, enter the nat command to enter the NAT configuration mode.
      2. From the NAT configuration mode, enter the nat-log-syslog level 1-7 command to select the Syslog level to be sent to the Syslog server.
    You have successfully configured the DP Syslog settings from the CLI.

Configuring the DNS Server IP address

The DNS server the Data Plane (DP) uses to resolve domain names is configured during initial deployment, however, you can use the DP CLI to update this configuration.
Complete the following steps to update the DNS configuration of the DP:
  1. From the Global configuration mode in the CLI, enter the dns command to enter the DNS configuration mode.
  2. In the DNS configuration mode, enter the command ip primary-dns_server-ip_address secondary-dns_server-ip_address.
  3. Type end to exit the Global configuration mode and save the changes.
The following CLI example changes the DNS server IP to 192.168.200.55 and 8.8.8.8 as the primary and secondary DNS servers, respectively:
vDP-2# config
vDP-2(config)# dns
vDP-2(config-dns)# ip 192.168.200.55 8.8.8.8
vDP-2(config-dns)# end
job 21 at Sat Nov 29 06:11:00 2025
Save changes, and then exits the config context.
vDP-2#
Use the show ip command to display the configured DNS settings:
vDP-2# show ip
IP Name Server: 192.168.200.55, 8.8.8.8
IP Data NAT IP: No Configured!