ServerView Resource Coordinator VE Setup Guide

7.1 Overview

Using the Pre-configuration function, it is possible to create system definition files that can be later used to setup a Resource Coordinator VE environment. Importing system configuration files makes it easy to perform various registration settings in one operation. This prevents the operating mistakes induced by sequences of individual, manual configuration steps.

The pre-configuration function can be used in the following situations.

• New installation

  From a traditional work office (or another off-site location), define the various parameters required for Resource Coordinator VE and record them in a system configuration file. Next, send this definition file to your actual system location (machine room), and import the file into Resource Coordinator VE using the import functionality of the RC console. This single operation automates the registration of all the servers defined in the system configuration file.

• Backing up a system configuration

  Using the export function of the RC console, the current Resource Coordinator VE configuration can be exported to a system configuration file.

• Batch re-configuration

  The registration settings of already registered resources can be modified easily by exporting the current configuration to a system configuration file and editing the desired configuration items before re-importing that configuration file. The actual re-configuration is then performed as a single import operation.

• Re-use of existing configurations

  Once a system has been fully setup, its configuration can be exported and re-used as a basis for the design of other systems. This makes it easy to design various systems located in different sites.

  Figure 7.1 Examples of use

  

Only system configuration files in CSV format can be imported or exported. For details on the system configuration file's format, refer to "Appendix D Format of CSV System Configuration Files".
Resource Coordinator VE provides a sample in CSV format. An Excel template (hereafter called "system configuration template") is also available from the ServerView Resource Coordinator VE home page. This system configuration template makes it easy to create system configuration files in CSV format.
The system configuration files imported by the system configuration template or the RC console should conform to the format described in "D.2 File Format".
Similarly, system configuration files created by the system configuration template or exported from the RC console always conform to the format described in "D.2 File Format".

The following operations, usually performed from the RC console, can be equally performed using the pre-configuration function.

• Registering resources:

  • "Chapter 6 Setup"

    • "6.1.2 Registering Chassis"

    • "6.1.3 Registering Managed Servers"

    • "6.1.4 Registering LAN Switches"

    • "6.1.5 Registering VM Management Software"

    • "6.1.6 Registering Power Monitoring Devices" (*1)

    • "6.2.1 Configuring VLANs on LAN Switches"

    • "6.2.2 Configuring HBA address rename" (*2)

  • "Chapter 9 Server Switchover Settings"

    • "9.6 Server Switchover Settings"

• Modifying resources:

  • "Chapter 6 Setup"

    • "6.3.1.1 Changing Admin IP Addresses" (*3)

    • "6.3.2.2 Changing Server Names"

    • "6.3.2.3 Changing Admin IP Addresses" (*3)

    • "6.3.2.4 Changing SNMP Communities"

    • "6.3.2.5 Changing Server Management Unit Configuration Settings"

    • "6.3.2.7 Changing VM Host Login Account Information"

    • "6.3.2.8 Changing the VLAN Settings of a LAN Switch"

    • "6.3.2.9 Changing HBA address rename Settings" (*2)

    • "6.3.5 Changing LAN Switch Settings"

    • "6.3.6 Changing VM Management Software Settings"

    • "6.3.7 Changing Power Monitoring Environment Settings"

  • "Chapter 9 Server Switchover Settings"

    • "9.7 Changing Server Switchover Settings"

*1: To start collecting environment data, the collection settings should be manually set from the RC console's option dialog.
*2: Restart all the managed servers that were either registered or modified following an import operation.
*3: The pre-configuration's scope of configuration is the same as that of the RC console.

Moreover, the pre-configuration function can perform the same labels and comments settings as those available in BladeViewer. Those settings are described in "3.6.1 Listing and Editing of Labels and Comments" and "Chapter 3 BladeViewer" in the "ServerView Resource Coordinator VE Operation Guide".

Note

• The following operations cannot be performed by the pre-configuration function, and should be performed from the RC console.

  • Deleting registered resources from Resource Coordinator VE

  • Changing the name of a registered chassis, physical server (only for servers other than PRIMERGY BX servers) or a power monitoring device

  • Discovering, registering, or changing registration settings of a LAN switch

  • Detecting physical link information from a LAN switch

• When using ServerView Deployment Manager on the admin LAN, the following settings cannot be defined using the pre-configuration function. Refer to "Appendix H Co-Existence with ServerView Deployment Manager" for details.

  • Spare server settings (using the backup and restore or HBA address rename method)

  • HBA address rename settings