[cisco-voip] UC on UCS storage.....

[Josh Warcop]

Essentially direct attached storage or via fiber channel. Not to say it wont work via the other methods but it is your choice to stick with the support table or not. I have seen people do it via all of the above and have a don't ask don't tell policy of you engage TAC relating to performance.

My recommendation is to give it what it asks for otherwise your maintenance cycles are going to be measured in days vs. Hours. It takes long enough as it is to patch these suckers and sub-par server and storage performance will make your life miserable.

Sent from my Windows Phone
________________________________
From: Scott Voll<mailto:svoll.voip at gmail.com>
Sent: ‎12/‎17/‎2014 5:58 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: [cisco-voip] UC on UCS storage.....

OK planning storage requirements for UC on UCS upgrade from 8.6(physical)
 to 10.5(vm)

we are looking at 2 CM nodes, 1 UC, 1 UCCx, one CER, PLM, PCD, and
presence.  The way I see it from the VM doc's it looks like I need about 1
TB of storage and roughly 8k IOPS.  What Protocols are supported?  FCoE?
iSCSI? NFS?  The only thing I have found thus far is FC.

Can anyone confirm that IO and Storage looks reasonable?  and let me know
which protocol's are TAC supported?

Thanks

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141217/fcd632b1/attachment.html>
-------------- next part --------------
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip