Joining vSZ-D to the vSZ Controller

Establishes a connection between the vSZ Data Plane (vSZ-D) and the vSZ Controller, enabling traffic handling, tunnel termination, and data path integration. This step is required for proper coordination and control between the management and data planes.
Perform the following steps to join vSZ-D to the vSZ Controller -
  1. After the VM is deployed, click Power On to start the vSZ-D.
  2. Open a console window to log in to the vSZ-D CLI.

    vSZ CLI Console

  3. At the login prompt, login as an Administrator with the username and password.

    Logging In to Privileged EXEC Mode

  4. At the > prompt, enter the enable command and the admin password to access Privileged EXEC mode.
  5. Use the setup command to configure the IP address for the management and data interfaces.

    Using the setup Command

    Note: Add a new hostname if multiple hosts are available for different configurations.
  6. Choose the IP address setup for the management and data interfaces by selecting either MANUAL or DHCP. After defining the IP configuration, the vSZ-D initiates the join process with the vSZ controller.

    Specifying the IP Version Support for Management and Data Interfaces

    Specifying the IP Configuration for for Management and Data Interfaces

  7. Follow the sequence of steps shown in the following figure to join vSZ-D to the vSZ controller. The process changes the FIPS mode for vSZ-D according to the FIPS mode state of vSZ.

    vSZ-D Joining vSZ

  8. To add the vSZ-D to vSZ controller, from the main menu, navigate to Network > Data and Control Plane > Cluster. Under Data Planes section, select the Data Plane and click Approve. Upon approval, the status of the data plane appears dimmed.

    Approved vSZ-D FIPS image

    Note: After the vSZ-D is joined to the vSZ, all management of the vSZ-D is performed via the vSZ. SSH admin access to the vSZ-D is disabled.
  9. To delete the vSZ-D in vSZ controller, from the main menu, navigate to Network > Data and Control Plane > Cluster. Select the vSZ-D and click Delete. Upon approval, the status of the data plane is removed from the Data Planes section.
    Note: Deleting the vSZ-D from the controller prevents all other components from communicating with the vSZ-D.
    Note: While the registration of components is done over a secure TLS channel, this part has not been claimed in the CC evaluation due to limited certificate verification capabilities during the registration. The TOE requires the use of a dedicated channel for the AP and vSZ-D to register with a controller. The administrator must perform the registration of TOE components in a controlled environment in which there is a segregated network with only TOE components present. Further communication between AP/vSZ-D and (v)SZ is secured through the SSH connection.