VirtualIron.com | Join | Contact Us

Blog


Welcome to the Virtual Iron Forums!
Here you'll find information to help you get the maximum value from your Virtual Iron software.

Community
Decrease font size
Increase font size
Topic Title: SUN X2200 support
Topic Summary: Experimental certified or not?
Created On: 12/14/2006 04:48 AM
Linear : Threading : Single : Branch
Topic Tools Topic Tools
View topic in raw text format. Print this topic.
 12/14/2006 04:48 AM
User is offline View Users Profile Print this message


TTiSoB
New User

Posts: 3
Joined: 12/14/2006

According this http://www.virtualiron.com/products/servers.cfm the SUN X2200 is experimental certified. But in this post the SUN isn't listed. I tried the bootdisk on a X2200 but it can't get an ip-address from dhcp. It keeps timing out. Will the SUN X2200 be certified?
 12/14/2006 05:37 AM
User is offline View Users Profile Print this message


TTiSoB
New User

Posts: 3
Joined: 12/14/2006

Can I set the bootparameter so that it doesn't use dhcp but a static ip-address?
 12/14/2006 10:38 AM
User is offline View Users Profile Print this message


darmlin
Apprentice

Posts: 23
Joined: 05/03/2006

Yes, the X2200 M2 will be certified and added to the docs you reference. We did have a beta site successfully run on the X2200 M2 and included the NVidia drivers to handle the ports other than the Broadcoms built-in in the 2200 M2.

In general with problems PXE booting you need to make sure that your networking for your dedicated management network is set up properly. Here's a typical layout with fictious addresses used for illustration.

Management Server

eth0 (172.15.15.221) - public/corporate network to access the Virtual Iron Virtualization Manager
eth1 (10.10.1.1) - Dedicated management network that the Virtual Iron Virtualization Manager's dhcp/tftp engine . Typically plugged into a separate 1Gb Ethernet switch or VLANd port on a switch.

Managed Node (X2200 M2)
eth0 - PXE turned on cabled into same switch or VLAN as eth1 on Mgmt Server

I often plug in a laptop or another server and assign it a static address on the dedicated managment server (i.e. 10.10.1.10) and then ping the mgmt server to make sure it is up and visible on that network (10.10.1.1).

Then boot your managed node and watch it PXE boot.
The logs for the dedicated managment network's DHCP server are in the VirtualIron/VirtualizationManager/system/logs/dhcpd.log file(on all platforms the mgmt server runs on) and you will see DHCPDISCOVER, etc from the interface you are booting on.
 12/14/2006 02:00 PM
User is offline View Users Profile Print this message


darmlin
Apprentice

Posts: 23
Joined: 05/03/2006

If you are booting from CD currently no. We'll add the ability to set a static address when booting the CD ROM in a future release.

Once you have PXE boot working with the 2200 M2 you'll be on to the more interesting features. Most likely this is something simple.
 12/15/2006 04:03 AM
User is offline View Users Profile Print this message


TTiSoB
New User

Posts: 3
Joined: 12/14/2006

Simple it was.. I installed on another X2200 SLES9 and the eth0 is the ethernet port above the usb ports. That confused it. Plugged in 4 network cables and the dhcp request was fulfilled. Then it was simple finding out which network cable was on the ethernet port that is eth0. Thnx for the help.
Statistics
222 users are registered to the Community forum.
There are currently 0 users logged in.

FuseTalk Standard Edition - © 1999-2007 FuseTalk Inc. All rights reserved.


Copyright © 2003-2007 Virtual Iron Software, Inc. | Privacy Statement | Terms of Use | Site Map