Florian Götz wrote:
> I got a network problem with one of my Debian VMs. The VM runs on an
> ESX Host (5.1) with several other VMs (SLES11).
> It´s a Debian 6 (can´t upgrade due to errors with the other running
> software at the moment) which hosts a Network Management System
> (Opsview) based
Karl E. Jorgensen wrote:
> On Mon, Feb 03, 2014 at 09:56:24AM +0100, Florian Götz wrote:
>> It takes about an hour before the hosts get back to state "pingable"
>> on the Debian machine.
> a whole hour!? That is way too long for spanning tree to settle down.
> So spanning tree/routing can probab
Hi
On Mon, Feb 03, 2014 at 09:56:24AM +0100, Florian Götz wrote:
> Hi Debian-Users,
>
> I got a network problem with one of my Debian VMs.
> The VM runs on an ESX Host (5.1) with several other VMs (SLES11).
>
> It´s a Debian 6 (can´t upgrade due to errors with the other running
> software at the
VM has one eth interface (one virtual GBit NIC).
I tried ssh to the unpingable device, but got no reaction.
The reverse way (ping from device to Debian VM) doesn´t work either.
It´s like the complete path between the two devices is blocked.
Best regards
Florian Götz
Mit freundlichen Grüßen
F
On Mon, Feb 3, 2014 at 8:56 AM, Florian Götz wrote:
> Anyone got a hint where to search for a solution to that?
Not an expert, but, does the machine have more than one NIC? If so,
have you tried ping -i? Or other services in the unpingable machines?
What about the reverse way?
HTH
--
To UNSUBS
Hi Debian-Users,
I got a network problem with one of my Debian VMs.
The VM runs on an ESX Host (5.1) with several other VMs (SLES11).
It´s a Debian 6 (can´t upgrade due to errors with the other running
software at the moment) which hosts a Network Management System
(Opsview) based on nagios.
If
6 matches
Mail list logo
