No, we primarily work with Netapp and in particular one of these clients uses 
the low end S550 (formerly Storevault).  Nice units with NFS/Cifs and iSCSI.  

The other client is using an internal RAID5 array with I think just 10K SAS 
drives.  We have found that SATA drives just don't prefrom well enough in local 
raid 5.  Even the lowest end SAS drives seem to work well. 

-Matt

>>> "Picher, Michael" <mpic...@cmctechgroup.com> 01/06/09 4:56 AM >>>

 <o:shapedefaults v:ext="edit" spidmax="1026" />
<![endif]-->
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout><![endif]-->Matt,<o:p></o:p>
<o:p> </o:p>
Are you folks using OpenFiler for your SAN stuff?<o:p></o:p>
<o:p> </o:p>
Thanks,<o:p></o:p>
                Mike<o:p></o:p>
<o:p> </o:p>
 
sipx-users-boun...@list.sipfoundry.org[mailto:sipx-users-boun...@list.sipfoundry.org]
 On Behalf Of Matt White
Sent: Monday, January 05, 2009 7:59 PM
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] SipX on VMWare ESXi<o:p></o:p>


<o:p> </o:p>
Ishould add we have two installation of Sipx on ESXi with "good"success.

Here is what we have found.  Here are some rules we have found that workmost of 
the time.
1. Use the latest version of ESX...ie 3.5.x
2. Never try to run anything else on the server, I know, seems to be counter 
tovirtualization 
3. Use at least a quad core
4. Use AMD opterons, for some reason they seem to work better for 
sip....I'vedone some research and it seems like the AMD are faster at 
contextswitching...so maybe thats why.
5. Set the VM's CPU, Disk and RAM shares to "high".
6. Only set the VM to a single CPU

We have found this works fairly well considering only VM and auto 
attendsactually hit the sipx server.  I'm sure this will not work well with 
the4.0 release and it's sipxbridge.  But for 3.10 with an ingate this workswell.

Also, most of our clients are opting for Exchnage UM, so that removes 
thevoicemail from the equation anyways.

The reason why we go through this trouble is the ease of DR and"safety".  We 
typically take a "snapshot" of thesystem in the final config and put it on a 
DVD.  If the server ever blowsup, we can have it up and running much faster 
than installing Centos and thenrestoring the config.  The customer can also 
make snapshots and revert backif they break somthing.

The sipx snapshots are nice, but typically things get modified on the 
linuxserver itself that is not captured by the "backup".

So, we use Virtualization not for consildation but for all the other perks.

Good luck.....but like the others have said, virtualization is gonna be 
muchmore tempermental than a physcial server...and will require a larger server 
toperform at the same level.

-M



>>> "Tony Graziano" 01/05/09 7:45 PM >>>
Thanks for following up with him Matt. 

I think even if you dedicate resources, there's still always a possible 
issue.It's fine for lab use, but not really for production use I think. Unless 
youhave a really good way to always guarantee all resources without latency in 
avirtual environment, it's not a good idea in production. Latency + sip =misery.

This has been discussed in detail many times on the list, and your best 
answeris to back it up through sipxconfig and restore to a standalone system.

>>> "Matt White" 01/05/09 7:19 PM >>> How manyphysical cores are in the ESXi 
>>> server?

It's a common mistake for people to assign 2 vSMP to a host.  Generallyspeaking 
with ESX, you will get lower performance when using multiple cpu'sinside a VM.  
Thats because there is a performance hit to virtualizing twocpu's.  The only 
time this works out is if the software running in the VMis heaviliy 
multi-threaded.

And if there's not at least 4 CPU's int he ESXi server than it's really 
aproblem becuase the virtual machine with fight with the Service console for 
cputime.

-M

>>> Jhony Perez <jpe...@zbzoom.net> 01/05/09 6:26 PM>>>
Hello everyone,

I have SipX 3.10.2 with CentOS 5 running on a VMWare ESXi server, I've 
assign 1GB of RAM and selected 2 CPU during the install, the system 
seems to run just fine but we started having intermittent issues with 
voicemail quality, at first it was only on the playback of the message 
but now it seems to be on the message itself, as we can hear it during 
the playback from forwarding it to email.

I've dedicated resources to the SipX, (1GHz and 1GB RAM) now I'm going 
to monitor the server closely but if this continues to happen I'm gonna 
have to move it to a dedicated server. By the way, we only have 5 users 
on the system which it is live.

Has anyone installed SipX on VMWare and if so, how does it run?? is 
there any tweak I can do to get it working better??

Your help is greatly appreciated.

Jhony
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

-- 
This email was Anti Virus checked by the Summit Technology Consulting 
GroupsAstaro Security Gateway. http://www.astaro.com

<o:p></o:p>


</mpic...@cmctechgroup.com>
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to