Virtualized Workloads Supported Instant Messaging (IM) IM Conferencing Presence Enterprise Voice (PSTN) Audio/Video Conferencing Web Conferencing Application Sharing Remote Access, Federation (Edge Server) Response Group Service Persistent Chat Back-End Database Archiving/Monitoring Databases

CounterDescriptionHealthy Range \Processor Information(*)\ % Processor TimeCPU Utilization< 80% (highest core) \Memory\Available MbytesDisplays the amount of physical memory, in bytes, available to processes running on the computer.>20% total system MB \PhysicalDisk\Avg. Disk Sec/Read A key measure of disk latency representing the average time, in milliseconds, of each read to disk where > 20 is poor, <20 is good/fair, <12 is better, <8 is best 25 ms Red \PhysicalDisk\Avg. Disk sec/Write A key measure of disk latency representing the average time, in milliseconds, of each write to disk, where non-cached writes. (>20 poor, 4 poor, <4 fair, <2 better, <1 best ). For online transaction processing (OLTP) databases, the lower this number the better, especially for disks holding the transaction log. 25 ms Red LS:Usrv - DBStore\Usrv – Queue Latency (msec) Queue latency is the amount of time (in milliseconds) that it takes for a request to leave the Front End Server’s queue toward the back-end database. If this value by itself is high, you may have be encountering a network problem between the Front End Server and the SQL Server. If this value is high and Sproc Latency is high, it is most commonly a bottleneck with the Back End Server. <100ms sustained LS:USrv – DBStore\Usrv – Sproc Latency (msec) Sproc latency is the amount of time (in milliseconds) that it takes for the SQL Server database to process the request. This performance value is collected from the time the request leaves the Front End Server queue until that the request returns. If this value by itself is high, it is likely a bottleneck with the Back End Server. <100ms sustained \SQL Server Buffer Manager\Page life expectancy Tells, on average, how many seconds SQL Server expects a data page to stay in cache. The target on an OLTP system should be at least 300 (5 min). When under 300, this may indicate poor index design (leading to increased disk I/O and less effective use of memory) or, simply, a potential shortage of memory. A low value, below 3600 seconds (together with high lazy writes/sec and checkpoint pages/sec) indicates memory pressure. < 300 \MSSQL$RTC:Memory Manager\Total Server Memory(KB) Shows the amount of memory that SQL Server is currently using. This value should grow until it is equal to Target Server Memory, as it populates its caches and loads pages into memory. When it has finished, SQL Server is said to be in a “steady-state”. Until it is in steady-state, performance may be slow and IO may be higher. < 80% of physical memory \ASP.NET Apps v (*)\Requests Rejected < 80%

QtyMfg Part #Description B21HP DL560 Gen8 CTO Server L21HP E DL560 Gen8 FIO Kit B21HP E DL560 Gen8 Kit B21HP 16GB 2Rx4 PC R-11 Kit B21HP 300GB 6G SAS 15K 2.5in SC ENT HDD B21HP Smart Array P222/512MiB FBWC Ctrlr B21HP Smart Array P421/2GiB FBWC Controller 8AJ764AHP 82Q 8Gb Dual Port PCI-e FC HBA B21HP 1GbE 4-port 331FLR Adapter FIO Kit B21HP 1GB FBWC for P-Series Smart Array 8AJ940AHP StorageWorks D2600 Disk Enclosure B21HP 600GB 6G SAS 15K 3.5in DP ENT HDD

Storage LocationInternal External DisksDisks 0-3 Disks 4-7Disks 8-11 ArrayArray 0 (RAID 10)Array 1 (RAID 10)Array 2 (RAID 10)Array 3 (RAID 10) Capacity600 GB1.2 TB IOPS (100% Read %)700 IOPS IOPS (100% Write %)350 IOPS

Logical Proc Host01Host02Host03Host04Host05Host06Host07Host FE01FE02FE03BE01BE02Edge01Edge02ST DC01DC02ST OWAS01 BE03 (Witness) OWAS02 ST ST01ST02ST03 ST04ST Reserved