[cisco-voip] Cisco UCS vs Spec's based solution - evaluation

Tim Smith tim.smith at enject.com.au
Wed Nov 27 22:44:04 EST 2013


We see lots of systems with SAN storage. (especially b-series, it’s really the default option here)

Also, OS can still be on the box, boot from SAN and hosting your VM’s on the SAN are two different things.
You can still run your ESXi OS on DAS, and run your apps on the SAN.
Again in a b-series environment – boot from SAN would be more typical.

I would do some more investigation around what skills and resources you have in VM and storage already. This would be a big factor in deciding which way to go. For example, no skills, then I would stick with TRC and DAS, you can then pretty much treat each box as a stand-alone appliance.

If you have infrastructure and skills already, it may be a good idea to take advantage of them.
Hosting your apps on shared storage can give you lots of other benefits.
You can also use separate data centres in VMWare to ensure segregation and custom policies for your UC apps.

Cheers,

Tim.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Thursday, 28 November 2013 2:14 PM
To: Jason Aarons (AM)
Cc: Cisco VoIPoE List
Subject: Re: [cisco-voip] Cisco UCS vs Spec's based solution - evaluation

I'm definitely going to ask for that option. I think in this situation DAS is the way to go. The only issue is that it's going to be the odd duck out. They're going to have to design a RAID array configuration for the chassis. If we want chassis redundancy, it means duplicating the disk array configuration.

My head is beginning to hurt already.

Sent from my iPhone

On 2013-11-27, at 9:21 PM, "Jason Aarons (AM)" <jason.aarons at dimensiondata.com<mailto:jason.aarons at dimensiondata.com>> wrote:
For voice I still like to see DAS.  Seems once in a blue moon the EMC or NetApp, etc needs a upgrade and if everything boots from the SAN that is a big risk.  Just don’t like the idea of my OS not being on the box…call me old school.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Wednesday, November 27, 2013 11:32 AM
To: Nate VanMaren
Cc: Cisco VoIPoE List
Subject: Re: [cisco-voip] Cisco UCS vs Spec's based solution - evaluation


Thanks Nate. Yes, after reading the storage requirements, it's quite complex to understand. Has your experience been with DAS or NAS/SAN? I'm wondering, if we bite the bullet and use DAS, we might eliminate some of the complexity and have (almost) guaranteed performance.


---
Lelio Fulgenzi, B.A.
Senior Analyst, Data Centre and Communications Facilities
Computing and Communications Services (CCS)
University of Guelph

519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

________________________________
From: "Nate VanMaren" <VanMarenNP at ldschurch.org<mailto:VanMarenNP at ldschurch.org>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>, "Cisco VoIPoE List" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Tuesday, November 26, 2013 5:36:00 PM
Subject: RE: [cisco-voip] Cisco UCS vs Spec's based solution - evaluation
All I have used is Cisco UCS specs based.

The biggest number one thing to worry about is DISK, everything else is easy.

The 2nd is if an existing VM farm, getting the admins to actually not over subscribe CPUs.

Thanks,
-Nate

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Tuesday, November 26, 2013 2:36 PM
To: Cisco VoIPoE List
Subject: Re: [cisco-voip] Cisco UCS vs Spec's based solution - evaluation

Sorry, that really should have read, Cisco TRC UCS vs Third party Spec's based solution. :(
---
Lelio Fulgenzi, B.A.
Senior Analyst, Data Centre and Communications Facilities
Computing and Communications Services (CCS)
University of Guelph

519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

________________________________
From: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
To: "Cisco VoIPoE List" <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Sent: Tuesday, November 26, 2013 4:19:50 PM
Subject: [cisco-voip] Cisco UCS vs Spec's based solution - evaluation

I've been asked to produce a short report, comparing the resources and support options of Cisco UCS vs Spec's based solution, i.e. an existing infrastructure.

There is a lot of information out there that I will be using, but I'm also interested in hearing from others who have produced a similar report.

Also, if others are willing to share support issues that have cropped up which you had difficulty dealing with, that would be great too. I'd like to be able to include some real world examples.

Thanks, Lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst, Data Centre and Communications Facilities
Computing and Communications Services (CCS)
University of Guelph

519‐824‐4120 Ext 56354
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip



NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.




itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20131128/03e9c1c4/attachment.html>


More information about the cisco-voip mailing list