Contents

1. Executive Summary
   1. Explanation of objectives
   2. Software used to collect assessment data
   3. Report Interpretation
2. Reference
   1. Summary
   2. Monitored Devices
   3. Device Inventory
   4. WAN Interface Connections
   5. WAN Interface Utilization
   6. Cisco Device CPU Utilization
   7. Cisco Device Free RAM
3. MOS Results
   1. MOS Score to Remote Devices
   2. Call Simulations
4. Recommendations
   1. Discovered Network Issues
   2. WAN Interface Recommendations
   3. Half-Duplex Interfaces
   4. 10Meg Interfaces

I. Executive Summary

I.a. Explanation of objectives

The objective of this report is to identify network weaknesses throughout the infrastructure that will lead to call quality problems. All network devices and interfaces are checked for health and performance statistics every 00 hours, 05 minutes, 00 seconds. As a result, any network anomalies that occur anywhere in the network, any time of day will be detected and reported.

Call Simulations should also be performed from endpoint to endpoint to further validate that the network is properly handling QoS tagging for VoIP calls. Those reports should be attached to this report as part of a complete assessment.

I.b. Software used to collect assessment data

This assessment report has been generated by PathSolutions Network Monitor Release v4.2 (5265). Individual call simulator reports will idenfity the version of the Call Simulator used for each report individually.

I.c. Report Interpretation

This assessment report is divided into three main sections: Reference, MOS Results, and Work to be Done.

The Reference section identifies the network and its current condition and capabilities Each of these items should be investigated further to insure that the network is running according to understood parameters. Care should be taken with the interpretation of the reference information to determine additional network improvements that should be implemented prior to VoIP deployment.

The MOS Results section identifies MOS (Mean Opinion Score) results from the monitoring server out to the monitored devices as well as manually run Call Simulations from various points in the network. If the MOS results show drop-offs or lower quality ratings than expected, the root-causes of the problems may lie with the third section of this report: Recommendations.

The Work to be Done section outlines existing network faults and weaknesses that should be remedied prior to VoIP deployment. Improvements to this section of the report should yield better MOS Results with subsequent tests.

The best practices regarding performing a network assessment include fixing all of the discovered network faults and then running simulated VoIP calls through the network from various points. If the MOS Results from the simulated calls show problems, perform a call path mapping to determine where additional network weaknesses lie.

Optimally, the network should be continuously monitored for health and performance to prevent call quality issues from occurring, as a one-time network assessment tends to not be as valuable as continuous ongoing monitoring.

II. Reference

II.a. Summary

For this report, 22 devices and a total of 587 interfaces were monitored.

9 WAN links with bandwidth less than 10meg were discovered.

6 interfaces were discovered above theshold levels (80% utilization and 3% packet loss) in the past 24 hours.

II.b. Monitored Devices

The following network devices were monitored as part of the assessment.

II.c. Device Inventory

The following device internal descriptions are as follows.

II.d. WAN Interface Connections

Queuing configuration on WAN interfaces is very important to insure proper prioritization of VoIP traffic. The following describes different queuing configurations that may exist on WAN interfaces:

• FIFO:First In First Out
• WFQ:Weighted Fair Queuing
• PQ:Priority Queuing
• MQC:Modular Qos Cli
• CQ:Custom Queuing

The following WAN interfaces below 10mbps were detected on the network.

II.e. WAN Interface Utilization

The following WAN interfaces have bandwidth utilization below 10mbps and may have contention if they have high utilization and VoIP traffic passes along this link. QoS should be evaluated for these links to prevent packet loss during periods of high utilization.

Device & Interface	Description
Denver Int #2	Se0: Serial0 Speed: 1,544,000 bps Peak Tx Rate: 0.547496% Peak Rx Rate: 0.618307%
NewYork Int #2	Se0: Serial0 Speed: 1,544,000 bps Peak Tx Rate: 0.621762% Peak Rx Rate: 0.544041%

II.f. Cisco Device CPU Utilization

CPU utilization is tracked for Cisco devices across the network. The health over the past 24hours is displayed below for each Cisco device.

Device Name	Daily CPU Utilization
Chardonnay 10.100.36.51
SCWANRTR 38.102.148.163
Internet 10.100.36.1
Denver 10.100.36.60
NewYork 192.168.201.2
Atlanta 192.168.202.2

II.g. Cisco Device Free RAM

Free RAM is tracked for Cisco devices across the network. The health over the past 24hours is displayed below for each Cisco device.

Device Name	Daily Free RAM
Chardonnay 10.100.36.51
SCWANRTR 38.102.148.163
Internet 10.100.36.1
Denver 10.100.36.60
NewYork 192.168.201.2
Atlanta 192.168.202.2

III. MOS Results

III.a. MOS Score to Remote Devices

The following devices were monitored for MOS (Mean Opinion Score) over the past 24 hours. If any score is below acceptable levels, further investigation should be performed.

Device Name	Daily Graph
HQ SG 40/8 10.100.36.100	Min: 4.4 Avg: 4.4 Max: 4.4
SF SG 40/8 10.100.37.100	Min: 1.0 Avg: 4.2 Max: 4.4
VELMA 10.100.36.10	Min: 4.4 Avg: 4.4 Max: 4.4
DAGWOOD 10.100.36.11	Min: 4.4 Avg: 4.4 Max: 4.4
Bordeaux 10.100.37.2	Min: 4.3 Avg: 4.4 Max: 4.4
Chiraz 10.100.37.3	Min: 4.3 Avg: 4.4 Max: 4.4
SC_Server 10.0.12.5	Min: 4.4 Avg: 4.4 Max: 4.4
SC_User_SW1 10.0.12.6	Min: 4.4 Avg: 4.4 Max: 4.4
SC_User_SW2 10.0.12.7	Min: 4.4 Avg: 4.4 Max: 4.4
QA_SW1 10.0.12.8	Min: 4.4 Avg: 4.4 Max: 4.4
QA_SW2 10.0.12.9	Min: 4.4 Avg: 4.4 Max: 4.4
PinotNoir 10.100.36.49	Min: 4.4 Avg: 4.4 Max: 4.4
Chardonnay 10.100.36.51	Min: 4.4 Avg: 4.4 Max: 4.4
Gewurztraminer 10.100.36.55	Min: 4.4 Avg: 4.4 Max: 4.4
Muscat 192.168.202.50	Min: 4.2 Avg: 4.4 Max: 4.4
SCWANRTR 38.102.148.163	Min: 4.4 Avg: 4.4 Max: 4.4
Internet 10.100.36.1	Min: 4.4 Avg: 4.4 Max: 4.4
Denver 10.100.36.60	Min: 1.0 Avg: 3.8 Max: 4.0
NewYork 192.168.201.2	Min: 4.1 Avg: 4.3 Max: 4.3
Atlanta 192.168.202.2	Min: 3.1 Avg: 4.3 Max: 4.3
EdgeMarc4500 10.100.36.50	Min: 4.3 Avg: 4.4 Max: 4.4
Router 10.100.36.65	Min: 4.1 Avg: 4.4 Max: 4.4

III.b. Call Simulations

Simulated phone calls should be made across each WAN link for a 24hour period.

IV. Recommendations

IV.a. Discovered Network Issues

The following network issues were discovered on the network. These issues should be evaluated to determine if they should be resolved prior to deploying a VoIP phone system.

IV.b. WAN Interface Recommendations

IV.c. Half-Duplex Interfaces

The following interfaces were shown to have collision counters or are set for half-duplex. They should be set for full-duplex on both sides of the connection to eliminate the possibility of collisions.

IV.d. 10Meg Interfaces

The following interfaces were shown to be operating at 10megabits per second. Most network adapters are capable of being set to 100mbps. These interfaces should be considered for upgrade to 100mbps to alleviate the possibility of bottlenecking.