N1 Provisioning Server 3.1, Blades Edition, Control Center Management Guide

Configuring Servers and Virtual Interfaces

Configuring Servers and Server Groups

This section describes general information about server storage and configuration tasks.

Servers that have local disks physically connect by using SCSI or IDE interfaces. In order to activate and deploy a server, you need to configure at least one boot volume with a bootable OS image on the volume. The disk volume must be equal to or greater than the size of the image. Consider the following when configuring servers and server groups.


Caution – Caution –

When managing an active server group and applying a new disk image, the selected image is applied to each server in the server group. This process causes down time because all the servers will reboot.


Each server interface typically connects to a different subnet. If the interfaces connect to the same subnet, you need to thoroughly understand how the operating system handles this situation. Connect one or both interfaces depending upon your requirement. For example, connect the web server to a front-end subnet and the database server to a back-end subnet for added security. Use the server group mechanism to group servers or not depending on your requirements. You have more control with individual servers, but easier management with server groups.

After the farm is Active, you can perform the following tasks:

ProcedureHow To Configure Servers

Steps
  1. From the Editor screen, double-click the Server element.

    The Configure Server dialog box appears.

  2. In the Name field, type a new name that conforms to DNS naming conventions.

    See DNS Naming Conventions.

  3. Select a device type from the Type drop-down list.

  4. Select an default gateway from the Def. Gateway drop-down list.

  5. Accept the default value (1) for the Server field if appropriate.

    The value indicates the desired number of servers.

  6. Type any relevant notes or comments in the Notes field.

  7. Click the appropriate Storage tab.

    The following columns describe the available storage.

    • Boot indicates if the local disk is bootable.

    • Channel indicates the channel ID for the local disk. Most disks have two channels (0 and 1) and can support two disks (Master and Slave).

    • Disk indicates whether the disk is a Master or Slave disk.

    • Size indicates the disk sizes that have been configured.

  8. Click the Select button to select an image.

  9. Click the OK button.

    The Configure Server dialog box is closed.

See Also

ProcedureHow To Create a Group of Servers

Server groups are defined as a set of servers that share a common function. For example, web servers might be grouped to simplify maintenance and manipulation of multiple individual servers. Server groups allow a number of identical servers to be managed as a single entity. All servers in a server group are considered identical and start off with the same images. Use the following procedure to create a server group by using the Editor screen.


Note –

Any monitor deployed to a server group is automatically applied to each server in the group.


Steps
  1. Double-click the Server element from the Editor screen.

    The Configure Server dialog box appears.

  2. Type the desired number of servers in the Server field.


    Note –

    The gray area now has a scroll bar to allow you to view all the servers you added. The eth0: IP Address and eth1: IP Addresses are assigned after the farm becomes Active.


  3. To add an image to the new disk, click the Select button.

    The Select Disk Image dialog box appears.

  4. Select an appropriate image from the list.

  5. Click OK to exit the Select Disk Image dialog box.

    A warning message appears indicating the server will be shut down to apply the new image.

  6. Click the OK button to apply the new disk image.

  7. Click the OK button to save and exit the Configure Server dialog box.

    The Server element changes to represent a group of servers.

See Also

How To Use an Account Software Image

Configuring Virtual Interfaces

This section describes virtual interface configuration. You may configure up to 16 virtual interface groups for every primary port on a server. The primary ports (ports like eth0/eth1 as opposed to eth0:2) cannot be deleted or changed. The primary ports have DNS names and they might be the primary interface of the device. IP addresses are allocated and displayed for all connected interfaces. Allocate IP addresses on a particular subnet on a server by drawing a wire from a subnet to the interface connection point. In order to submit the farm, all servers must have their eth0 interface allocated. Additionally, if any virtual interface on a primary port is allocated, the primary interface must also be allocated.

The following procedure describes configuration of virtual ports by using the Editor screen in the Control Center.

ProcedureHow To Configure Virtual Interfaces

Steps
  1. Double click the element to which you will add a virtual interface.

    The Configure dialog box appears.

  2. Click the + button in the Virtual Interfaces area of the screen.

    A virtual port is added to the element such as eth0:1 or eth1:1.


    Note –

    You may add up to 16 virtual ports per physical (real) port.


  3. Click OK/Apply.

    The Configure screen is closed.

  4. Choose Save from the File menu.

    The virtual port configuration is saved.

See Also