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

[Nate VanMaren]

The reasons I didn’t use TRC:

Wanted to use the 10 core procs in the C-260.

I refuse to use a 1 RU server.  I had 14 of them die (HP, not Cisco) in a computer room.  I don’t feel like 1 RU gets enough air through them, or the Power supply (not usually redundant or hot swappable in 1 RU) is sufficient.

So I used C210-M2 and then C240-M3 when the C210s went EOS.



From: matthn at gmail.com [mailto:matthn at gmail.com] On Behalf Of Nick Matthews
Sent: Tuesday, November 26, 2013 4:47 PM
To: Nate VanMaren
Cc: Lelio Fulgenzi; Cisco VoIPoE List
Subject: Re: [cisco-voip] Cisco UCS vs Spec's based solution - evaluation

If it adds any color, the majority of all UC on UCS deployments are TRC. Of the specs based deployments (meaning any derivation from the TRC) the majority of those are UCS as well.  (This is an extrapolation on numbers I've seen, as well as what I've seen with customers and feedback from other folks as well).
When I do see specs based, it's usually because there is no other option. When there's only one server at a facility/site, it's only for DR, it's hosted on specs based as a stop gap, etc. But that's just what I see in mid-sized businesses that I work with as well. Voice/collab is usually important enough that the support structure of TRC's supersedes server-politics battles, particularly since there's no significant cost advantage of third party hardware.
-nick
(disclosure: Cisco SE)

On Tue, Nov 26, 2013 at 5:36 PM, Nate VanMaren <VanMarenNP at ldschurch.org<mailto:VanMarenNP at ldschurch.org>> wrote:
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<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.


_______________________________________________
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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20131212/a41f54d1/attachment.html>