Amazing timing guys!  I’ve been struggling with this very issue for weeks and you just solved my problem.

Cheers!

---

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Scott Lowe
Sent: May 3, 2007 7:28 PM
To: James Beal; toasters@mathworks.com
Subject: RE: The simulator and vmware esx

James,

Thanks for sharing your solution.  I ran into this same issue on ESX Server last year and documented it here on my personal blog:

<http://blog.scottlowe.org/2006/06/27/netapp-ontap-simulator-and-esx-server/>

This documents the solution for ESX 2.5.x; I guess I need to update it for ESX 3.0.x.

Thanks,
Scott Lowe
Senior Engineer
ePlus Technology, Inc.
slowe@eplus.com


-----Original Message-----
From:   owner-toasters@mathworks.com on behalf of James Beal
Sent:   Thu 5/3/2007 8:00 PM
To:     toasters@mathworks.com
Cc:    
Subject:        The simulator and vmware esx

I sent this from my un-subscribed work address so if we get two copies
apologies.

I have been banging my head against the traditional problem with the
simulator and not being able to see the network.

Its interesting to discover that esx has an option (Security) under each
network "vswitch". The security tab has a policy exceptions area. There
is an option for Promiscuous mode, the simulator doesn't talk to the
network by default, you need to allow promiscuous mode access to the
virtual switch.

Once you know the option is there in esx its obvious how it should be
set I just didn't know it existed. I haven't seen this recorded as a
solution to the problem yet and thought people may be interested.

james