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
 new topic  join  help  home
latest topics : statistics
FORUMS arrow How-tos arrow General Q&A arrow Troubleshooting Networks in v3.5
Topic Title: Troubleshooting Networks in v3.5
Topic Summary:
Created On: 03/09/2007 12:20 PM
 Linear : Threading : Single : Branch
  Troubleshooting Networks in v3.5   - DougBaer - 03/09/2007 12:20 PM  
  Troubleshooting Networks in v3.5   - DougBaer - 03/09/2007 12:32 PM  
  Troubleshooting Networks in v3.5   - cbarclay - 03/09/2007 02:40 PM  
Topic Tools Topic Tools
View topic in raw text format. Print this topic.
03/09/2007 12:20 PM
User is offline View Users Profile Print this message


DougBaer
New User

Posts: 4
Joined: 03/09/2007

I have a new 3.5 install with a management network on eth1 of the virtualized node that handles the PXE boot. This works fine and the node will boot from the image on the management server. Unfortunately, eth0 and eth2 are attached to my lab network, but I never seem to get an IP address on that network and no networks besides the Management Network will show up in the VI management interface. What are my options for troubleshoooting in the node? Can I get to a command prompt where I can troubleshoot? eth0 is in the same switch as the lab DHCP server that has 95% of the scope free and is serving addresses just fine to the other hosts there.
Reply : Quote : Top : Bottom
FORUMS : How-tos : General Q&A : Troubleshooting Networks in v3.5

Topic Tools Topic Tools
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