VMWARE on 2003 Server

Hi all,

I know this is not a VMWARE newsgroup, but it applies to Windows 2003
server Enterprise. Here is my setup and problem. I have two servers, both
2003 server Enterprise. Both patched to SP1 with all updates. I install
VMWARE on each with the same install package, using the same license
key/serial. When you boot up the servers, they both work for a short time,
then one goes offline. Only one server will be available on the network at
any given time. These servers are both plugged into the same switch, running
identical configurations. I thought it might be a nic issue, so I broke the
teams, am only using single nic configuration now but that didn't help. I
wasn't having this problem before I installed VMWARE. Has anyone else had
this problem before. If I use a different key/serial for VMWARE I think this
should go away, but its possible I have something mis-configured, so I
thought I would ask here.

thanks
Joe

Joe,

What version of VMware software are you running? GSX v? Workstation
v? Do you have any VM configured? Are you running NLB on the hosts or on
the VMs? How many NICs total do you have in each host?


--
James E. Price III
Fairway Consulting Group, Inc.
O: 954-727-5126
C: 305-970-4902
E: (E-Mail Removed)
W: www.fcgroup.us


"ACE-Joe" wrote:

> Hi all,
>
> I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> server Enterprise. Here is my setup and problem. I have two servers, both
> 2003 server Enterprise. Both patched to SP1 with all updates. I install
> VMWARE on each with the same install package, using the same license
> key/serial. When you boot up the servers, they both work for a short time,
> then one goes offline. Only one server will be available on the network at
> any given time. These servers are both plugged into the same switch, running
> identical configurations. I thought it might be a nic issue, so I broke the
> teams, am only using single nic configuration now but that didn't help. I
> wasn't having this problem before I installed VMWARE. Has anyone else had
> this problem before. If I use a different key/serial for VMWARE I think this
> should go away, but its possible I have something mis-configured, so I
> thought I would ask here.
>
> thanks
> Joe

Thanks for the reply. I am running GSX version 3.1.0 build 9089 (I know
there is a newer version, but we have not downloaded it yet). I do have one
VM configured on one server, the other server has 4 but will have 6. I am
not running NLB on either server, I was using teaming with the HP Software,
but due to this problem and troubleshooting, I dissolved the team and set it
to a single adapter on each server. I have two nics in each server. Each
guest OS has only one adapter listed.

Thanks
Joe

"James Price" wrote:

> Joe,
>
> What version of VMware software are you running? GSX v? Workstation
> v? Do you have any VM configured? Are you running NLB on the hosts or on
> the VMs? How many NICs total do you have in each host?
>
>
> --
> James E. Price III
> Fairway Consulting Group, Inc.
> O: 954-727-5126
> C: 305-970-4902
> E: (E-Mail Removed)
> W: www.fcgroup.us
>
>
> "ACE-Joe" wrote:
>
> > Hi all,
> >
> > I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> > server Enterprise. Here is my setup and problem. I have two servers, both
> > 2003 server Enterprise. Both patched to SP1 with all updates. I install
> > VMWARE on each with the same install package, using the same license
> > key/serial. When you boot up the servers, they both work for a short time,
> > then one goes offline. Only one server will be available on the network at
> > any given time. These servers are both plugged into the same switch, running
> > identical configurations. I thought it might be a nic issue, so I broke the
> > teams, am only using single nic configuration now but that didn't help. I
> > wasn't having this problem before I installed VMWARE. Has anyone else had
> > this problem before. If I use a different key/serial for VMWARE I think this
> > should go away, but its possible I have something mis-configured, so I
> > thought I would ask here.
> >
> > thanks
> > Joe

Joe,

Your logic sounds good, and you shouldn't have any problems with what
you're trying to do. I've used the HP Teaming for a long time and mostly it
works great. Now after you dissolved the Teams you still have the problem?

In an obilgatory note towards licnesing, if you use more than one copy of a
product from any manufacturer you should always do the right thing and pay
for what you use, it's the morally and ethically correct thing to do. -- End
of lecture

Now to the problem at hand, how do you have your vnmics configured? I don't
recommend using the automatic bridging feature, I recommend you assign
specific NICs to each virtual network. When a virtual machine uses a NIC
assigned to a virtual network it creates a second L2 address on the physical
interface. I don't think based on what I've understood you to say that the
problem happens only when you are running VM, it sounds like it happens on
the boxes anyway. How long after boot up does this happen?

When the problem happens can you still ping the interfaces on each server,
if you can't which interfaces can you ping and which ones can't you ping?
Also take a look at the CAM table on you switch and take a look at the switch
log and see if it's complaining about anything.
--
James E. Price III
Fairway Consulting Group, Inc.
O: 954-727-5126
C: 305-970-4902
E: (E-Mail Removed)
W: www.fcgroup.us


"ACE-Joe" wrote:

> Thanks for the reply. I am running GSX version 3.1.0 build 9089 (I know
> there is a newer version, but we have not downloaded it yet). I do have one
> VM configured on one server, the other server has 4 but will have 6. I am
> not running NLB on either server, I was using teaming with the HP Software,
> but due to this problem and troubleshooting, I dissolved the team and set it
> to a single adapter on each server. I have two nics in each server. Each
> guest OS has only one adapter listed.
>
> Thanks
> Joe
>
> "James Price" wrote:
>
> > Joe,
> >
> > What version of VMware software are you running? GSX v? Workstation
> > v? Do you have any VM configured? Are you running NLB on the hosts or on
> > the VMs? How many NICs total do you have in each host?
> >
> >
> > --
> > James E. Price III
> > Fairway Consulting Group, Inc.
> > O: 954-727-5126
> > C: 305-970-4902
> > E: (E-Mail Removed)
> > W: www.fcgroup.us
> >
> >
> > "ACE-Joe" wrote:
> >
> > > Hi all,
> > >
> > > I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> > > server Enterprise. Here is my setup and problem. I have two servers, both
> > > 2003 server Enterprise. Both patched to SP1 with all updates. I install
> > > VMWARE on each with the same install package, using the same license
> > > key/serial. When you boot up the servers, they both work for a short time,
> > > then one goes offline. Only one server will be available on the network at
> > > any given time. These servers are both plugged into the same switch, running
> > > identical configurations. I thought it might be a nic issue, so I broke the
> > > teams, am only using single nic configuration now but that didn't help. I
> > > wasn't having this problem before I installed VMWARE. Has anyone else had
> > > this problem before. If I use a different key/serial for VMWARE I think this
> > > should go away, but its possible I have something mis-configured, so I
> > > thought I would ask here.
> > >
> > > thanks
> > > Joe

Thanks again for the reply. And yes when I dissolve the team the problem
still occurs. We do own the licenses for more than one copy, but I'm new to
this company, and was only given one install package and one serial to
register with, I have asked for a second serial to see if a licensing issue
is at the root of the problem. But I appreciate your honesty.

I have the VM's configured using the automatic bridge. I want each VM to
have it's own interface and IP. Now when you say virtual network, are you
talking about the vlan stuff I saw in the VMWARE network settings? Is there
a better way to configure networking in the VMs other than bridging, I only
choose that because it was the only one that in the description mentioned
that it would assign each VM its own IP on the external network.

As far as when the problem happens, its shortly after boot, both servers
are available for a short while, then one goes down, I can't ping any
interface on the server, it becomes completely unreachable. There are no
helpful events in the event viewer, no errors on the server itself, it just
quits responding on the IP layer. Thats why I thought it was a licensing
thing, because it really didn't happen until I loaded VMWARE and one works if
the other is off, but they don't work when both are powered on.

I'll ask our cisco admin to take a look at the switch and see if she can
find anything out of the ordinary.

Thanks again
Joe

"James Price" wrote:

> Joe,
>
> Your logic sounds good, and you shouldn't have any problems with what
> you're trying to do. I've used the HP Teaming for a long time and mostly it
> works great. Now after you dissolved the Teams you still have the problem?
>
> In an obilgatory note towards licnesing, if you use more than one copy of a
> product from any manufacturer you should always do the right thing and pay
> for what you use, it's the morally and ethically correct thing to do. -- End
> of lecture
>
> Now to the problem at hand, how do you have your vnmics configured? I don't
> recommend using the automatic bridging feature, I recommend you assign
> specific NICs to each virtual network. When a virtual machine uses a NIC
> assigned to a virtual network it creates a second L2 address on the physical
> interface. I don't think based on what I've understood you to say that the
> problem happens only when you are running VM, it sounds like it happens on
> the boxes anyway. How long after boot up does this happen?
>
> When the problem happens can you still ping the interfaces on each server,
> if you can't which interfaces can you ping and which ones can't you ping?
> Also take a look at the CAM table on you switch and take a look at the switch
> log and see if it's complaining about anything.
> --
> James E. Price III
> Fairway Consulting Group, Inc.
> O: 954-727-5126
> C: 305-970-4902
> E: (E-Mail Removed)
> W: www.fcgroup.us
>
>
> "ACE-Joe" wrote:
>
> > Thanks for the reply. I am running GSX version 3.1.0 build 9089 (I know
> > there is a newer version, but we have not downloaded it yet). I do have one
> > VM configured on one server, the other server has 4 but will have 6. I am
> > not running NLB on either server, I was using teaming with the HP Software,
> > but due to this problem and troubleshooting, I dissolved the team and set it
> > to a single adapter on each server. I have two nics in each server. Each
> > guest OS has only one adapter listed.
> >
> > Thanks
> > Joe
> >
> > "James Price" wrote:
> >
> > > Joe,
> > >
> > > What version of VMware software are you running? GSX v? Workstation
> > > v? Do you have any VM configured? Are you running NLB on the hosts or on
> > > the VMs? How many NICs total do you have in each host?
> > >
> > >
> > > --
> > > James E. Price III
> > > Fairway Consulting Group, Inc.
> > > O: 954-727-5126
> > > C: 305-970-4902
> > > E: (E-Mail Removed)
> > > W: www.fcgroup.us
> > >
> > >
> > > "ACE-Joe" wrote:
> > >
> > > > Hi all,
> > > >
> > > > I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> > > > server Enterprise. Here is my setup and problem. I have two servers, both
> > > > 2003 server Enterprise. Both patched to SP1 with all updates. I install
> > > > VMWARE on each with the same install package, using the same license
> > > > key/serial. When you boot up the servers, they both work for a short time,
> > > > then one goes offline. Only one server will be available on the network at
> > > > any given time. These servers are both plugged into the same switch, running
> > > > identical configurations. I thought it might be a nic issue, so I broke the
> > > > teams, am only using single nic configuration now but that didn't help. I
> > > > wasn't having this problem before I installed VMWARE. Has anyone else had
> > > > this problem before. If I use a different key/serial for VMWARE I think this
> > > > should go away, but its possible I have something mis-configured, so I
> > > > thought I would ask here.
> > > >
> > > > thanks
> > > > Joe

Joe,

I'll be interested to hear what the Network Admin has to say but in the
meantime power up both your servers and wait for the problem to happen. When
it does log onto each server and stop all the VMware services and kill any
VMware proceses that are running that will take VMware out of play and see of
you connectivity returns.

Either way, as for configuring you virtual networks, this may be a little
tricky to explain so if you send me an email I can send you some screenshots
to make what I'm trying to explain more clear. Here goes, VMware creates 10
VMnets (Virutal Networks) 0-9 VMnet 0 is typicaly bridged to the first
physical interface in you host systems (and will stay that way if you are
using automatic bridging) VMnet 1 is the default NATed network that will NAT
against your host's IP, VMnets 3-7 & 9 aren't assigned by default and VMnet 8
is a special host network that only the VMs on that host and the host itself
can see.

I recommend disabling Automatic Bridging and since you have multiple NICs in
the host system to assign them to VMnets manually. This way you know what
you've got and it's easier to troubleshoot and it has the advantage of
allowing you to manage which VM are using which NICs and you can then put the
NICs in separate VLANs and create secure segrated networks.

Now all of this doesn't really fix your problem but it gets us to the point
where we have a better understanding of what you've got set up.
--
James E. Price III
Fairway Consulting Group, Inc.
O: 954-727-5126
C: 305-970-4902
E: (E-Mail Removed)
W: www.fcgroup.us


"ACE-Joe" wrote:

> Thanks again for the reply. And yes when I dissolve the team the problem
> still occurs. We do own the licenses for more than one copy, but I'm new to
> this company, and was only given one install package and one serial to
> register with, I have asked for a second serial to see if a licensing issue
> is at the root of the problem. But I appreciate your honesty.
>
> I have the VM's configured using the automatic bridge. I want each VM to
> have it's own interface and IP. Now when you say virtual network, are you
> talking about the vlan stuff I saw in the VMWARE network settings? Is there
> a better way to configure networking in the VMs other than bridging, I only
> choose that because it was the only one that in the description mentioned
> that it would assign each VM its own IP on the external network.
>
> As far as when the problem happens, its shortly after boot, both servers
> are available for a short while, then one goes down, I can't ping any
> interface on the server, it becomes completely unreachable. There are no
> helpful events in the event viewer, no errors on the server itself, it just
> quits responding on the IP layer. Thats why I thought it was a licensing
> thing, because it really didn't happen until I loaded VMWARE and one works if
> the other is off, but they don't work when both are powered on.
>
> I'll ask our cisco admin to take a look at the switch and see if she can
> find anything out of the ordinary.
>
> Thanks again
> Joe
>
> "James Price" wrote:
>
> > Joe,
> >
> > Your logic sounds good, and you shouldn't have any problems with what
> > you're trying to do. I've used the HP Teaming for a long time and mostly it
> > works great. Now after you dissolved the Teams you still have the problem?
> >
> > In an obilgatory note towards licnesing, if you use more than one copy of a
> > product from any manufacturer you should always do the right thing and pay
> > for what you use, it's the morally and ethically correct thing to do. -- End
> > of lecture
> >
> > Now to the problem at hand, how do you have your vnmics configured? I don't
> > recommend using the automatic bridging feature, I recommend you assign
> > specific NICs to each virtual network. When a virtual machine uses a NIC
> > assigned to a virtual network it creates a second L2 address on the physical
> > interface. I don't think based on what I've understood you to say that the
> > problem happens only when you are running VM, it sounds like it happens on
> > the boxes anyway. How long after boot up does this happen?
> >
> > When the problem happens can you still ping the interfaces on each server,
> > if you can't which interfaces can you ping and which ones can't you ping?
> > Also take a look at the CAM table on you switch and take a look at the switch
> > log and see if it's complaining about anything.
> > --
> > James E. Price III
> > Fairway Consulting Group, Inc.
> > O: 954-727-5126
> > C: 305-970-4902
> > E: (E-Mail Removed)
> > W: www.fcgroup.us
> >
> >
> > "ACE-Joe" wrote:
> >
> > > Thanks for the reply. I am running GSX version 3.1.0 build 9089 (I know
> > > there is a newer version, but we have not downloaded it yet). I do have one
> > > VM configured on one server, the other server has 4 but will have 6. I am
> > > not running NLB on either server, I was using teaming with the HP Software,
> > > but due to this problem and troubleshooting, I dissolved the team and set it
> > > to a single adapter on each server. I have two nics in each server. Each
> > > guest OS has only one adapter listed.
> > >
> > > Thanks
> > > Joe
> > >
> > > "James Price" wrote:
> > >
> > > > Joe,
> > > >
> > > > What version of VMware software are you running? GSX v? Workstation
> > > > v? Do you have any VM configured? Are you running NLB on the hosts or on
> > > > the VMs? How many NICs total do you have in each host?
> > > >
> > > >
> > > > --
> > > > James E. Price III
> > > > Fairway Consulting Group, Inc.
> > > > O: 954-727-5126
> > > > C: 305-970-4902
> > > > E: (E-Mail Removed)
> > > > W: www.fcgroup.us
> > > >
> > > >
> > > > "ACE-Joe" wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> > > > > server Enterprise. Here is my setup and problem. I have two servers, both
> > > > > 2003 server Enterprise. Both patched to SP1 with all updates. I install
> > > > > VMWARE on each with the same install package, using the same license
> > > > > key/serial. When you boot up the servers, they both work for a short time,
> > > > > then one goes offline. Only one server will be available on the network at
> > > > > any given time. These servers are both plugged into the same switch, running
> > > > > identical configurations. I thought it might be a nic issue, so I broke the
> > > > > teams, am only using single nic configuration now but that didn't help. I
> > > > > wasn't having this problem before I installed VMWARE. Has anyone else had
> > > > > this problem before. If I use a different key/serial for VMWARE I think this
> > > > > should go away, but its possible I have something mis-configured, so I
> > > > > thought I would ask here.
> > > > >
> > > > > thanks
> > > > > Joe

Thanks for the info, I think I understand what your saying about the
networking, I'll give that a try if it acts up again. I just got a message
back from the net admin, they broke the team on the second server and they
seem to be working well together now. I broke the team on the first server
because it was usually the one that quit working. now that both are not
using a team, both servers are up and working ok so far. I can't explain it,
but that may have been the issue.

Thanks for all your help, you were very helpful!

Thanks
joe

"James Price" wrote:

> Joe,
>
> I'll be interested to hear what the Network Admin has to say but in the
> meantime power up both your servers and wait for the problem to happen. When
> it does log onto each server and stop all the VMware services and kill any
> VMware proceses that are running that will take VMware out of play and see of
> you connectivity returns.
>
> Either way, as for configuring you virtual networks, this may be a little
> tricky to explain so if you send me an email I can send you some screenshots
> to make what I'm trying to explain more clear. Here goes, VMware creates 10
> VMnets (Virutal Networks) 0-9 VMnet 0 is typicaly bridged to the first
> physical interface in you host systems (and will stay that way if you are
> using automatic bridging) VMnet 1 is the default NATed network that will NAT
> against your host's IP, VMnets 3-7 & 9 aren't assigned by default and VMnet 8
> is a special host network that only the VMs on that host and the host itself
> can see.
>
> I recommend disabling Automatic Bridging and since you have multiple NICs in
> the host system to assign them to VMnets manually. This way you know what
> you've got and it's easier to troubleshoot and it has the advantage of
> allowing you to manage which VM are using which NICs and you can then put the
> NICs in separate VLANs and create secure segrated networks.
>
> Now all of this doesn't really fix your problem but it gets us to the point
> where we have a better understanding of what you've got set up.
> --
> James E. Price III
> Fairway Consulting Group, Inc.
> O: 954-727-5126
> C: 305-970-4902
> E: (E-Mail Removed)
> W: www.fcgroup.us
>
>
> "ACE-Joe" wrote:
>
> > Thanks again for the reply. And yes when I dissolve the team the problem
> > still occurs. We do own the licenses for more than one copy, but I'm new to
> > this company, and was only given one install package and one serial to
> > register with, I have asked for a second serial to see if a licensing issue
> > is at the root of the problem. But I appreciate your honesty.
> >
> > I have the VM's configured using the automatic bridge. I want each VM to
> > have it's own interface and IP. Now when you say virtual network, are you
> > talking about the vlan stuff I saw in the VMWARE network settings? Is there
> > a better way to configure networking in the VMs other than bridging, I only
> > choose that because it was the only one that in the description mentioned
> > that it would assign each VM its own IP on the external network.
> >
> > As far as when the problem happens, its shortly after boot, both servers
> > are available for a short while, then one goes down, I can't ping any
> > interface on the server, it becomes completely unreachable. There are no
> > helpful events in the event viewer, no errors on the server itself, it just
> > quits responding on the IP layer. Thats why I thought it was a licensing
> > thing, because it really didn't happen until I loaded VMWARE and one works if
> > the other is off, but they don't work when both are powered on.
> >
> > I'll ask our cisco admin to take a look at the switch and see if she can
> > find anything out of the ordinary.
> >
> > Thanks again
> > Joe
> >
> > "James Price" wrote:
> >
> > > Joe,
> > >
> > > Your logic sounds good, and you shouldn't have any problems with what
> > > you're trying to do. I've used the HP Teaming for a long time and mostly it
> > > works great. Now after you dissolved the Teams you still have the problem?
> > >
> > > In an obilgatory note towards licnesing, if you use more than one copy of a
> > > product from any manufacturer you should always do the right thing and pay
> > > for what you use, it's the morally and ethically correct thing to do. -- End
> > > of lecture
> > >
> > > Now to the problem at hand, how do you have your vnmics configured? I don't
> > > recommend using the automatic bridging feature, I recommend you assign
> > > specific NICs to each virtual network. When a virtual machine uses a NIC
> > > assigned to a virtual network it creates a second L2 address on the physical
> > > interface. I don't think based on what I've understood you to say that the
> > > problem happens only when you are running VM, it sounds like it happens on
> > > the boxes anyway. How long after boot up does this happen?
> > >
> > > When the problem happens can you still ping the interfaces on each server,
> > > if you can't which interfaces can you ping and which ones can't you ping?
> > > Also take a look at the CAM table on you switch and take a look at the switch
> > > log and see if it's complaining about anything.
> > > --
> > > James E. Price III
> > > Fairway Consulting Group, Inc.
> > > O: 954-727-5126
> > > C: 305-970-4902
> > > E: (E-Mail Removed)
> > > W: www.fcgroup.us
> > >
> > >
> > > "ACE-Joe" wrote:
> > >
> > > > Thanks for the reply. I am running GSX version 3.1.0 build 9089 (I know
> > > > there is a newer version, but we have not downloaded it yet). I do have one
> > > > VM configured on one server, the other server has 4 but will have 6. I am
> > > > not running NLB on either server, I was using teaming with the HP Software,
> > > > but due to this problem and troubleshooting, I dissolved the team and set it
> > > > to a single adapter on each server. I have two nics in each server. Each
> > > > guest OS has only one adapter listed.
> > > >
> > > > Thanks
> > > > Joe
> > > >
> > > > "James Price" wrote:
> > > >
> > > > > Joe,
> > > > >
> > > > > What version of VMware software are you running? GSX v? Workstation
> > > > > v? Do you have any VM configured? Are you running NLB on the hosts or on
> > > > > the VMs? How many NICs total do you have in each host?
> > > > >
> > > > >
> > > > > --
> > > > > James E. Price III
> > > > > Fairway Consulting Group, Inc.
> > > > > O: 954-727-5126
> > > > > C: 305-970-4902
> > > > > E: (E-Mail Removed)
> > > > > W: www.fcgroup.us
> > > > >
> > > > >
> > > > > "ACE-Joe" wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> > > > > > server Enterprise. Here is my setup and problem. I have two servers, both
> > > > > > 2003 server Enterprise. Both patched to SP1 with all updates. I install
> > > > > > VMWARE on each with the same install package, using the same license
> > > > > > key/serial. When you boot up the servers, they both work for a short time,
> > > > > > then one goes offline. Only one server will be available on the network at
> > > > > > any given time. These servers are both plugged into the same switch, running
> > > > > > identical configurations. I thought it might be a nic issue, so I broke the
> > > > > > teams, am only using single nic configuration now but that didn't help. I
> > > > > > wasn't having this problem before I installed VMWARE. Has anyone else had
> > > > > > this problem before. If I use a different key/serial for VMWARE I think this
> > > > > > should go away, but its possible I have something mis-configured, so I
> > > > > > thought I would ask here.
> > > > > >
> > > > > > thanks
> > > > > > Joe

Joe,

No problem, just curious did you have the HP Team configured for
software of switch assisted? You may recall I said the HP Teaming "mostly"
worked for me, as a rule of thumb that's always one for my fisrt suspects in
this type of configuration.

~jp
--
James E. Price III
Fairway Consulting Group, Inc.
O: 954-727-5126
C: 305-970-4902
E: (E-Mail Removed)
W: www.fcgroup.us


"ACE-Joe" wrote:

> Thanks for the info, I think I understand what your saying about the
> networking, I'll give that a try if it acts up again. I just got a message
> back from the net admin, they broke the team on the second server and they
> seem to be working well together now. I broke the team on the first server
> because it was usually the one that quit working. now that both are not
> using a team, both servers are up and working ok so far. I can't explain it,
> but that may have been the issue.
>
> Thanks for all your help, you were very helpful!
>
> Thanks
> joe
>
> "James Price" wrote:
>
> > Joe,
> >
> > I'll be interested to hear what the Network Admin has to say but in the
> > meantime power up both your servers and wait for the problem to happen. When
> > it does log onto each server and stop all the VMware services and kill any
> > VMware proceses that are running that will take VMware out of play and see of
> > you connectivity returns.
> >
> > Either way, as for configuring you virtual networks, this may be a little
> > tricky to explain so if you send me an email I can send you some screenshots
> > to make what I'm trying to explain more clear. Here goes, VMware creates 10
> > VMnets (Virutal Networks) 0-9 VMnet 0 is typicaly bridged to the first
> > physical interface in you host systems (and will stay that way if you are
> > using automatic bridging) VMnet 1 is the default NATed network that will NAT
> > against your host's IP, VMnets 3-7 & 9 aren't assigned by default and VMnet 8
> > is a special host network that only the VMs on that host and the host itself
> > can see.
> >
> > I recommend disabling Automatic Bridging and since you have multiple NICs in
> > the host system to assign them to VMnets manually. This way you know what
> > you've got and it's easier to troubleshoot and it has the advantage of
> > allowing you to manage which VM are using which NICs and you can then put the
> > NICs in separate VLANs and create secure segrated networks.
> >
> > Now all of this doesn't really fix your problem but it gets us to the point
> > where we have a better understanding of what you've got set up.
> > --
> > James E. Price III
> > Fairway Consulting Group, Inc.
> > O: 954-727-5126
> > C: 305-970-4902
> > E: (E-Mail Removed)
> > W: www.fcgroup.us
> >
> >
> > "ACE-Joe" wrote:
> >
> > > Thanks again for the reply. And yes when I dissolve the team the problem
> > > still occurs. We do own the licenses for more than one copy, but I'm new to
> > > this company, and was only given one install package and one serial to
> > > register with, I have asked for a second serial to see if a licensing issue
> > > is at the root of the problem. But I appreciate your honesty.
> > >
> > > I have the VM's configured using the automatic bridge. I want each VM to
> > > have it's own interface and IP. Now when you say virtual network, are you
> > > talking about the vlan stuff I saw in the VMWARE network settings? Is there
> > > a better way to configure networking in the VMs other than bridging, I only
> > > choose that because it was the only one that in the description mentioned
> > > that it would assign each VM its own IP on the external network.
> > >
> > > As far as when the problem happens, its shortly after boot, both servers
> > > are available for a short while, then one goes down, I can't ping any
> > > interface on the server, it becomes completely unreachable. There are no
> > > helpful events in the event viewer, no errors on the server itself, it just
> > > quits responding on the IP layer. Thats why I thought it was a licensing
> > > thing, because it really didn't happen until I loaded VMWARE and one works if
> > > the other is off, but they don't work when both are powered on.
> > >
> > > I'll ask our cisco admin to take a look at the switch and see if she can
> > > find anything out of the ordinary.
> > >
> > > Thanks again
> > > Joe
> > >
> > > "James Price" wrote:
> > >
> > > > Joe,
> > > >
> > > > Your logic sounds good, and you shouldn't have any problems with what
> > > > you're trying to do. I've used the HP Teaming for a long time and mostly it
> > > > works great. Now after you dissolved the Teams you still have the problem?
> > > >
> > > > In an obilgatory note towards licnesing, if you use more than one copy of a
> > > > product from any manufacturer you should always do the right thing and pay
> > > > for what you use, it's the morally and ethically correct thing to do. -- End
> > > > of lecture
> > > >
> > > > Now to the problem at hand, how do you have your vnmics configured? I don't
> > > > recommend using the automatic bridging feature, I recommend you assign
> > > > specific NICs to each virtual network. When a virtual machine uses a NIC
> > > > assigned to a virtual network it creates a second L2 address on the physical
> > > > interface. I don't think based on what I've understood you to say that the
> > > > problem happens only when you are running VM, it sounds like it happens on
> > > > the boxes anyway. How long after boot up does this happen?
> > > >
> > > > When the problem happens can you still ping the interfaces on each server,
> > > > if you can't which interfaces can you ping and which ones can't you ping?
> > > > Also take a look at the CAM table on you switch and take a look at the switch
> > > > log and see if it's complaining about anything.
> > > > --
> > > > James E. Price III
> > > > Fairway Consulting Group, Inc.
> > > > O: 954-727-5126
> > > > C: 305-970-4902
> > > > E: (E-Mail Removed)
> > > > W: www.fcgroup.us
> > > >
> > > >
> > > > "ACE-Joe" wrote:
> > > >
> > > > > Thanks for the reply. I am running GSX version 3.1.0 build 9089 (I know
> > > > > there is a newer version, but we have not downloaded it yet). I do have one
> > > > > VM configured on one server, the other server has 4 but will have 6. I am
> > > > > not running NLB on either server, I was using teaming with the HP Software,
> > > > > but due to this problem and troubleshooting, I dissolved the team and set it
> > > > > to a single adapter on each server. I have two nics in each server. Each
> > > > > guest OS has only one adapter listed.
> > > > >
> > > > > Thanks
> > > > > Joe
> > > > >
> > > > > "James Price" wrote:
> > > > >
> > > > > > Joe,
> > > > > >
> > > > > > What version of VMware software are you running? GSX v? Workstation
> > > > > > v? Do you have any VM configured? Are you running NLB on the hosts or on
> > > > > > the VMs? How many NICs total do you have in each host?
> > > > > >
> > > > > >
> > > > > > --
> > > > > > James E. Price III
> > > > > > Fairway Consulting Group, Inc.
> > > > > > O: 954-727-5126
> > > > > > C: 305-970-4902
> > > > > > E: (E-Mail Removed)
> > > > > > W: www.fcgroup.us
> > > > > >
> > > > > >
> > > > > > "ACE-Joe" wrote:
> > > > > >
> > > > > > > Hi all,
> > > > > > >
> > > > > > > I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> > > > > > > server Enterprise. Here is my setup and problem. I have two servers, both
> > > > > > > 2003 server Enterprise. Both patched to SP1 with all updates. I install
> > > > > > > VMWARE on each with the same install package, using the same license
> > > > > > > key/serial. When you boot up the servers, they both work for a short time,
> > > > > > > then one goes offline. Only one server will be available on the network at
> > > > > > > any given time. These servers are both plugged into the same switch, running
> > > > > > > identical configurations. I thought it might be a nic issue, so I broke the
> > > > > > > teams, am only using single nic configuration now but that didn't help. I
> > > > > > > wasn't having this problem before I installed VMWARE. Has anyone else had
> > > > > > > this problem before. If I use a different key/serial for VMWARE I think this
> > > > > > > should go away, but its possible I have something mis-configured, so I
> > > > > > > thought I would ask here.
> > > > > > >
> > > > > > > thanks
> > > > > > > Joe

I can tell you that when I setup the Team I Did NOT set it to use switch
assisted. It was all controlled through the HP software. So far I have 5
VMs on one server, and 1 VM on the other, and they are all talking to each
other, and working great. I'm doing a DNS testing lab, so this is really
convenient now that everything is working.

Thanks again
Joe

"James Price" wrote:

> Joe,
>
> No problem, just curious did you have the HP Team configured for
> software of switch assisted? You may recall I said the HP Teaming "mostly"
> worked for me, as a rule of thumb that's always one for my fisrt suspects in
> this type of configuration.
>
> ~jp
> --
> James E. Price III
> Fairway Consulting Group, Inc.
> O: 954-727-5126
> C: 305-970-4902
> E: (E-Mail Removed)
> W: www.fcgroup.us
>
>
> "ACE-Joe" wrote:
>
> > Thanks for the info, I think I understand what your saying about the
> > networking, I'll give that a try if it acts up again. I just got a message
> > back from the net admin, they broke the team on the second server and they
> > seem to be working well together now. I broke the team on the first server
> > because it was usually the one that quit working. now that both are not
> > using a team, both servers are up and working ok so far. I can't explain it,
> > but that may have been the issue.
> >
> > Thanks for all your help, you were very helpful!
> >
> > Thanks
> > joe
> >
> > "James Price" wrote:
> >
> > > Joe,
> > >
> > > I'll be interested to hear what the Network Admin has to say but in the
> > > meantime power up both your servers and wait for the problem to happen. When
> > > it does log onto each server and stop all the VMware services and kill any
> > > VMware proceses that are running that will take VMware out of play and see of
> > > you connectivity returns.
> > >
> > > Either way, as for configuring you virtual networks, this may be a little
> > > tricky to explain so if you send me an email I can send you some screenshots
> > > to make what I'm trying to explain more clear. Here goes, VMware creates 10
> > > VMnets (Virutal Networks) 0-9 VMnet 0 is typicaly bridged to the first
> > > physical interface in you host systems (and will stay that way if you are
> > > using automatic bridging) VMnet 1 is the default NATed network that will NAT
> > > against your host's IP, VMnets 3-7 & 9 aren't assigned by default and VMnet 8
> > > is a special host network that only the VMs on that host and the host itself
> > > can see.
> > >
> > > I recommend disabling Automatic Bridging and since you have multiple NICs in
> > > the host system to assign them to VMnets manually. This way you know what
> > > you've got and it's easier to troubleshoot and it has the advantage of
> > > allowing you to manage which VM are using which NICs and you can then put the
> > > NICs in separate VLANs and create secure segrated networks.
> > >
> > > Now all of this doesn't really fix your problem but it gets us to the point
> > > where we have a better understanding of what you've got set up.
> > > --
> > > James E. Price III
> > > Fairway Consulting Group, Inc.
> > > O: 954-727-5126
> > > C: 305-970-4902
> > > E: (E-Mail Removed)
> > > W: www.fcgroup.us
> > >
> > >
> > > "ACE-Joe" wrote:
> > >
> > > > Thanks again for the reply. And yes when I dissolve the team the problem
> > > > still occurs. We do own the licenses for more than one copy, but I'm new to
> > > > this company, and was only given one install package and one serial to
> > > > register with, I have asked for a second serial to see if a licensing issue
> > > > is at the root of the problem. But I appreciate your honesty.
> > > >
> > > > I have the VM's configured using the automatic bridge. I want each VM to
> > > > have it's own interface and IP. Now when you say virtual network, are you
> > > > talking about the vlan stuff I saw in the VMWARE network settings? Is there
> > > > a better way to configure networking in the VMs other than bridging, I only
> > > > choose that because it was the only one that in the description mentioned
> > > > that it would assign each VM its own IP on the external network.
> > > >
> > > > As far as when the problem happens, its shortly after boot, both servers
> > > > are available for a short while, then one goes down, I can't ping any
> > > > interface on the server, it becomes completely unreachable. There are no
> > > > helpful events in the event viewer, no errors on the server itself, it just
> > > > quits responding on the IP layer. Thats why I thought it was a licensing
> > > > thing, because it really didn't happen until I loaded VMWARE and one works if
> > > > the other is off, but they don't work when both are powered on.
> > > >
> > > > I'll ask our cisco admin to take a look at the switch and see if she can
> > > > find anything out of the ordinary.
> > > >
> > > > Thanks again
> > > > Joe
> > > >
> > > > "James Price" wrote:
> > > >
> > > > > Joe,
> > > > >
> > > > > Your logic sounds good, and you shouldn't have any problems with what
> > > > > you're trying to do. I've used the HP Teaming for a long time and mostly it
> > > > > works great. Now after you dissolved the Teams you still have the problem?
> > > > >
> > > > > In an obilgatory note towards licnesing, if you use more than one copy of a
> > > > > product from any manufacturer you should always do the right thing and pay
> > > > > for what you use, it's the morally and ethically correct thing to do. -- End
> > > > > of lecture
> > > > >
> > > > > Now to the problem at hand, how do you have your vnmics configured? I don't
> > > > > recommend using the automatic bridging feature, I recommend you assign
> > > > > specific NICs to each virtual network. When a virtual machine uses a NIC
> > > > > assigned to a virtual network it creates a second L2 address on the physical
> > > > > interface. I don't think based on what I've understood you to say that the
> > > > > problem happens only when you are running VM, it sounds like it happens on
> > > > > the boxes anyway. How long after boot up does this happen?
> > > > >
> > > > > When the problem happens can you still ping the interfaces on each server,
> > > > > if you can't which interfaces can you ping and which ones can't you ping?
> > > > > Also take a look at the CAM table on you switch and take a look at the switch
> > > > > log and see if it's complaining about anything.
> > > > > --
> > > > > James E. Price III
> > > > > Fairway Consulting Group, Inc.
> > > > > O: 954-727-5126
> > > > > C: 305-970-4902
> > > > > E: (E-Mail Removed)
> > > > > W: www.fcgroup.us
> > > > >
> > > > >
> > > > > "ACE-Joe" wrote:
> > > > >
> > > > > > Thanks for the reply. I am running GSX version 3.1.0 build 9089 (I know
> > > > > > there is a newer version, but we have not downloaded it yet). I do have one
> > > > > > VM configured on one server, the other server has 4 but will have 6. I am
> > > > > > not running NLB on either server, I was using teaming with the HP Software,
> > > > > > but due to this problem and troubleshooting, I dissolved the team and set it
> > > > > > to a single adapter on each server. I have two nics in each server. Each
> > > > > > guest OS has only one adapter listed.
> > > > > >
> > > > > > Thanks
> > > > > > Joe
> > > > > >
> > > > > > "James Price" wrote:
> > > > > >
> > > > > > > Joe,
> > > > > > >
> > > > > > > What version of VMware software are you running? GSX v? Workstation
> > > > > > > v? Do you have any VM configured? Are you running NLB on the hosts or on
> > > > > > > the VMs? How many NICs total do you have in each host?
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > James E. Price III
> > > > > > > Fairway Consulting Group, Inc.
> > > > > > > O: 954-727-5126
> > > > > > > C: 305-970-4902
> > > > > > > E: (E-Mail Removed)
> > > > > > > W: www.fcgroup.us
> > > > > > >
> > > > > > >
> > > > > > > "ACE-Joe" wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > I know this is not a VMWARE newsgroup, but it applies to Windows 2003
> > > > > > > > server Enterprise. Here is my setup and problem. I have two servers, both
> > > > > > > > 2003 server Enterprise. Both patched to SP1 with all updates. I install
> > > > > > > > VMWARE on each with the same install package, using the same license
> > > > > > > > key/serial. When you boot up the servers, they both work for a short time,
> > > > > > > > then one goes offline. Only one server will be available on the network at
> > > > > > > > any given time. These servers are both plugged into the same switch, running
> > > > > > > > identical configurations. I thought it might be a nic issue, so I broke the
> > > > > > > > teams, am only using single nic configuration now but that didn't help. I
> > > > > > > > wasn't having this problem before I installed VMWARE. Has anyone else had
> > > > > > > > this problem before. If I use a different key/serial for VMWARE I think this
> > > > > > > > should go away, but its possible I have something mis-configured, so I
> > > > > > > > thought I would ask here.
> > > > > > > >
> > > > > > > > thanks
> > > > > > > > Joe