VCL VM Pre-install Checklist




1) Install Blade Center(s) in rack. Ensure you can connect to each blade center's management module via IP.

2) Select a single username/password to be the username VCL will use to login to every Blade Center Management Module. Create a 'Supervisor Profile' with the selected username/password on every blade center management module containing blades to be managed by VCL Also, ensure this profile has 'Supervisor' priveledges and is scoped to ONLY the blades you want VCL to manage.

3) You'll need to install, or use an existing DHCP server to hand out IP addresses to your blades 'public' interfaces (eth0). Configure DHCP such that your blades always get the same IP address for their eth0. This will require the loading of every blade's 'public' interface (eth0) MAC address into DHCP service. The IP address received should be a valid, routable address from wherever your clients are connecting from. Each blade's hostname must follow the form below. This is best tested with a live CD.

CHASSISNAME-blSLOTNUM.your.fully.qualified.domain.com

for example: blade 2 in chassis named 'test' on the .cnl.ncsu.edu network would be named test-bl2.cnl.ncsu.edu

4) For each blade desired to be managed by VCL ...

a) physically connect its public interface (eth0) to a public, routable VLAN. This should DHCP properly from step 3, and always to the same IP address.
b) physically connect its private interface (eth1) to a private, non-routable VLAN. Put all blades on the same non-routable VLAN. There should be nothing else on this network, except other VCL managed blade's private interfaces (eth1). If properly configured, any VCL blade should be able to ping another VCL blade's eth1.

5) Select a blade to host the VCL VM, and ensure ESX 3i is installed. The instructions will refer to this 3i blade as the 'VCL-Host'.

6) Sanity check your configuration against the below diagram.

hosted by ibiblio