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

[Tommy Schlotterer]

We do this before the install, it is up to the customer to not overload their SAN going forward.

If the test fails or Data Center Engineers recommend moving other high intensity applications off the SAN or adding drives to increase IOPS.

Tommy

Tommy Schlotterer | Systems Engineer
CCNA, CCNA Voice
48325 Alpha Dr. Ste. 150
Wixom, MI 48393
p 248.468.0710
e tschlotterer at netechcorp.com<mailto:tschlotterer at netechcorp.com>
w netechcorp.com<http://netechcorp.com/>
 [cid:image001.png at 01D01AAD.CCF8B4A0]
[cid:image002.png at 01D01AAD.CCF8B4A0]<https://www.linkedin.com/company/75843?trk=tyah&trkInfo=tarId%3A1397760375508%2Ctas%3Anetech%2Cidx%3A3-1-5> [cid:image003.png at 01D01AAD.CCF8B4A0] <https://www.facebook.com/NetechCorporation>  [cid:image004.png at 01D01AAD.CCF8B4A0] <https://twitter.com/netechcorp>  [cid:image005.png at 01D01AAD.CCF8B4A0] <https://www.youtube.com/user/NetechCorporation>

From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
Sent: Wednesday, December 17, 2014 10:18 PM
To: Tommy Schlotterer
Cc: Josh Warcop; cisco-voip voyp list
Subject: Re: [cisco-voip] UC on UCS storage.....

Interesting.

Is the test run periodically or just on demand? Is there a historical graph available?

Is the test itself passive with a simple high volume read/write and it comes back with results or is it stress based, ie you punch an IOPS value and it tries to do that much traffic.

Most importantly, if the test fails, how do they follow up. That's the biggest fear I have.

Sent from my iPhone

On Dec 17, 2014, at 9:52 PM, Tommy Schlotterer <tschlotterer at netechcorp.com<mailto:tschlotterer at netechcorp.com>> wrote:

We have our data center guys run an iops test VM to determine whether or not the storage is provide the required iops, and we recommend that the customer is  already experienced with a storage environment. We don't want an admin accidentally bringing the storage array down.

C series is the recommendation unless its a high end enterprise customer.

Tommy

Sent from my phone.
On Dec 17, 2014 9:44 PM, Josh Warcop <josh at warcop.com<mailto:josh at warcop.com>> wrote:
All good until our storage guy messed up the NFS permissions and the call manager died.

Sent from my Windows Phone
________________________________
From: Scott Voll<mailto:svoll.voip at gmail.com>
Sent: ‎12/‎17/‎2014 7:16 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] UC on UCS storage.....
I just found this:  http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#Storage

Looks like all the protocols are supported.  FCoE, iSCSI, NFS for 3rd party.

Anyone running any of this in production and care to put in your two cents?

Scott

On Wed, Dec 17, 2014 at 2:55 PM, Scott Voll <svoll.voip at gmail.com<mailto:svoll.voip at gmail.com>> wrote:
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

_______________________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141218/a80b196f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 42291 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141218/a80b196f/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1012 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141218/a80b196f/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 804 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141218/a80b196f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1152 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141218/a80b196f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1485 bytes
Desc: image005.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20141218/a80b196f/attachment-0004.png>