[cisco-voip] UC on UCS LUN Best Practices for Co-residency

[Chris Ward (chrward)]

Hi Ted,

 

LUNs don't have to be dedicated to physical hardware. You setup the
mappings on your SAN switch. So for example, in my lab, I have a 8-blade
UCS B-Series chassis connected to an MDS with 2 SANs hanging off of it.
I configured my MDS port mappings to allow all 8 ESXi hosts to be able
to reach all 22 LUNS (between the two SANs). This isn't necessarily
recommended, but in my lab environment I am looking for flexibility more
than anything else. So you can certainly have more than one host access
a single LUN.

 

I don't really understand your first question about physical disk
saving, but if you provide some clarity for me, perhaps I can help there
also.

 

+Chris

Hosted Collaboration Solution TME

 

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ted Nugent
Sent: Thursday, January 19, 2012 9:42 PM
To: Cisco VoIPoE List
Subject: [cisco-voip] UC on UCS LUN Best Practices for Co-residency

 

Does anyone have a best practices are for LUN configuration regarding UC
B-Series Co-Residency? I have read through the doc below regarding
"shared storage considerations" but still have some things that don't
add up (no pun intended)

 

I see that LUN size should be between 500 GB and 1.5 TB and hold between
4 and 8 UC Apps (I assume the later is to conserve physical Disk space)
however is there a logical way that these should be dedicated to the
physical server with regards to physical server portability down the
road? Can a LUN be mapped to more than one physical server, I would
think not? These may be stupid questions but I'm a bit new to
VMWare/B-Series so I didn't know if there were some best practices from
the field that people adhere to? If physical space was not an issue it
would almost seem more logical to make all LUNs 500GB and just have a
1:1 mapping to VDisks for portability but again I'm a UCS/VMWare Noob.
Thanks for any guidance

 

http://docwiki.cisco.com/wiki/Shared_Storage_Considerations

 

T

 

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