Configuring the replacement servers

Virtual Storage Platform One File 32 Gen2 Hardware Reference

Version
15.6.x
Audience
anonymous
Part Number
MK-24VSP1F009-00
ft:lastEdition
2026-08-28

Obtain the necessary IP addresses to be used for the replacement server. Servers shipped from the factory have not yet had the nas-preconfig script run on them, so a replacement server will not have any IP addresses pre-configured for your use.

The following settings are required to configure the replacement server:
  • Eth1 (Admin service private IP address) – Customer IP address
    • Cluster – IP address is temporary removed after server joined to Cluster
    • Single Node – IP address is permanent, used to administer the node
  • Eth1 (Admin Service Private netmask) – Customer netmask
  • Eth1 (Physical Node IP address) – Customer IP address from defective node
  • Eth1 (Physical Node netmask) - Customer netmask from defective node
  • Customer Gateway – Obtain from defective node or customer
  • Domain Name – Obtain from defective node or customer
  • Host name – Obtain from defective node or customer

When the replacement node is added to the cluster, it removes the temporary admin service IP address, and reconfigures the server to the previous server settings.

The reconfigured settings are:

  • Gateway
  • Domain name
  • Host name
  1. Use a keyboard, video, and mouse (KVM) device or a serial cable to connect to the serial port.
  2. Serial connection to the server serial port, use the following PuTTY client settings:
    • 115,200 b/s
    • 8 data bits
    • 1 stop bit
    • No parity
    • No flow control
  3. Log in to the server as root
  4. Run the nas-preconfig script. Follow the script to enter the information gathered from the replaced node.

    The script then displays a summary of the above entries and prompts to accept or decline the settings. If any entries are incorrect, answer N, and the script will return to the beginning.

  5. If the configuration settings are correct, select [y/n]Y.
    A message shows that the mfb.ini is created.
  6. The system will apply the mfb.ini configuration.

    This process may take time. Make sure not to reboot the node.