XYZ company's executives have approached you to architect, design, and recommend if they should use an IP network infrastructure for all their applications.

Here is some information you gathered about the company:

1. MyCo has 14 locations. The locations are 1 HQ, 2 regional centers (RC), and 11 local offices (LOs).

2. About 10,000 people work in this company, 25% at the HQ, 10% at each RCs, and 5% at each LOs.

10,000 total people:

                        25% x 10,000 @ HQ (2,500)

                        10% x 10,000 @ RC1 (1000)

                        10% x 10,000 @ RC2 (1000)

                        5%  x 10,000 @ each LO ( 500) - 5,500 people

3. The overall topology is tree-like where HQ is connected to the 2 RCs and 5 LOs, and each RC is connected to 3 LOs each. There is no other direct connection (e.g., between RC1 and RC2), or between LOs, etc.

4. At least 3 different types of major classes of applications exist today:

1. Priority Data Communications involved in
   1. engineering
   2. sales
   3. payroll
   4. marketing
   5. administrative
   6. operations functions.

1. Non-priority data applications such as:
   1.  e-mail
   2.  data-base update

1. Voice telephony
2. Conferencing
3. Real time-video training

There may be other applications coming soon, like conferencing, real time video-based training, etc.

5.      The HQ building houses Management (5%), Administrative and Operations (10%), Payroll (5%), Product Marketing (20%), Engineering (30%), and Sales (30%) people. The Regional Centers both have Admin & Ops (20%), Engineering (40%), and Sales people (40%). The Local Offices have only Sales people. Note that % are given for each location.

HQ has 2,500 people of which:

Subnet allocated - 150.75.32.0 - 150.75.32.1 - 150.75.45.254

Management (5%) x 2500 = 125 - 37.5 = 163          

Admin/Oper (10%) x 2500 = 250 - 75 = 325

Payroll          (5%) x 2500 = 125 - 37.5 = 163

            Product Mark (20%) x 2500 = 500 - 150 = 650

            Engineering    (30%) x 2500 = 750 - 225 = 975

            Sales            (30%) x 2500 = 750 - 225 = 975                    

            Total = 2,500 + .30%

            Total IP 3,250

RC 1 has 1000 of which:

Subnet allocated - 150.75.64.0 - 150.75.64.1 - 150.75.70.254

            Admin & Ops (20%) x 1000 = 200 - 260     

            Engineering    (40%) x 1000 = 400 - 520      

            Sales            (40%) x 1000 = 400 - 520

            Total = 1,000 + .30%

            Total IP = 1,300

RC 2 has 1000

Subnet allocated - 150.75.96.0 - 150.75.96.1 - 150.75.102.254

            Admin & Ops (20%) x 1000 = 200 - 260     

            Engineering    (40%) x 1000 = 400 - 520

            Sales                (40%) x 1000 = 400 - 520     

            Total = 1,000 + .30%

            Total IP = 1,300

Each LO has 5% of 10,000, 5,500 people

Subnet allocated - 150.75.128.0 - 150.75.128.1 - 150.75.157.254

            Sales 500 people per each LO x 11 total 5,500

            Total = 5,500 + .30% =

            Total IP = 7,150

6. Here is some more detailed information on the data applications:

The PM, Eng, and Sales people access Compute Servers and Storage Servers (databases) located at the HQ, RC1, and RC2. The engineers run product design related interactive computing applications to Compute Servers. The interactive computing application requires processing 5-10MB files with responses in 0.1 s. We can assume that no more than 10% of the engineers run the interactive computing application at a time in each location.

Engineers also make database inquiries and receive responses. An application for database inquiries (20 KB) and responses (20 MB) take typically 0.5 s. There are also batch database update applications run by engineers, which are 500MB to 2 GB files taking up to 15 minutes. The PM and Sales people only run database inquiry/responses. We can assume that no more than 10% of the engineers, or PMs, or sales people, run the database inquiry/response or the batch database update applications at a time in each location.

All groups use local servers only. The one exception is the Sales people at LOs need to access the Storage Servers at the nearest large office (HQ, or RC1, or RC2) as there is no Storage Server at the LOs. However, for cost savings and based on usage, 2 licenses are bought for the special software needed to access these software per LO location. In other words, only two sales people at a LO can simultaneously access the Storage Servers.

There are also data migrations (backup) between Storage Servers (databases) between the HQ and RC1 and separately between HQ and RC2 locations. These are 100 GB files run at night and takes several hours (~10,000 seconds).

Selected dataset (roughly half of the 100 GB file update mentioned above) is sent from the HQ Storage to an External server separated by a DMZ for access by customers through Internet. The selected dataset upload also happens at night and takes roughly an hour.

There is one Internet Access Server at the HQ which directs all company personnel access to Internet. We heard that for Internet access an average bandwidth of 30 Kbps per user is sufficient and no more than 15% of the employees access Internet concurrently. Internet access is only during day time hours.

Based on the above information, you are asked to provide answers to the following questions:

Q1. Develop traffic flow mapping and performance requirements for flows.

Traffic Flow Mapping - Already got this part done and submitted for grading

Performance Requirements -                          

Q2. Calculate data bandwidth requirements from and to each site.

Q4. This address block is quite large for them. Given the departments and number of people in each department at all locations (as noted above), develop a variable-length addressing scheme with some reserved addresses to accommodate possible future hires and addition of devices. MyCo suggests reserving at least 30% more IP addresses for each group. Be reasonable in your allocation and do not over-allocate addresses. Provide different address blocks for each department at each location for routing and security reasons, and make addresses contiguous; so that the unused address block can be traded or used for future use. (ALREADY DONE)

• Management - Subnet - 150.75.16.0 (150.75.16.1 - 150.75.31.254)
  • HQ - 163
  • [IP - 150.75.16.1 - 150.75.16.162]
• Admin - 150.75.32.0, (150.75.32.1 - 150.75.47.254)
  • HQ - 325
  • 150.75.32.1 - 150.75.32.254
  • 150.75.33.1 - 150.75.33.71
  • RC1 - 260
  • 150.75.33.72 - 150.75.33.254
  • 150.75.34.1 - 150.75.34.72
  • RC2 - 260
  • 150.75.34.73 - 150.75.34.254
  • 150.75.35.1 - 150.75.35.80
• Payroll - 150.75.80.0 (150.75.80.1 - 150.75.95.254)
  • 150.75.80.1 - 150.75.80.163
• Product Marketing - 150.75.48.0 (150.75.48.1 - 150.75.63.254)
  • IP - 150.75.48 - 150.75.254
  • 150.75.49.1 - 150.75.49.254
  • 150.75.50.1 - 150.75.50.1 - 150.75.50.142
• Engineering - Subnet - 150.75.64.0 (150.75.64.1 - 150.75.79.254)
  • HQ - 975
  • 150.75.64.1 - 150.75.64.254
  • 150.75.65.1 - 150.75 65.254
  • 150.75.66.1 - 150.75.66.254
  • 150.75.67.1 - 150.75.67.213
  • RC1 - 520
  • 150.75.67.213 - 150.75.76.254
  • 150.75.68.1 - 150.75.68.254
  • 150.75.69.1 - 150.75.69.225
  • RC2 - 520
  • 150.75.69.226 - 150.75.69.254
  • 150.75.70.1 - 150.75.70.254
  • 150.75.71.1 - 150.75.71.238
• Sales - 150.75.80.0 (150.75.80.1 - 150.75.95.254)
  • HQ - 975
  • 150.75.80.1 - 150.75.80.254
  • 150.75.80.1 - 150.75.80.254
  • 150.75.80.1 - 150.75.80.254
  • 150.75.80.1 - 150.75.80.213
  • LO1 - 650
  • 150.75.80.213 - 150.75.80.254
  • 150.75.81.1 - 150.75.81.254
  • 150.75.82.1 - 150.75.82.254
  • 150.75.83.1 - 150.75.83.101
  • LO2 - 650
  • 150.75.83.102 - 150.75.83.254
  • 150.75.84.1 - 150.75.84.254
  • 150.75.85.1 - 150.75.85.244
  • LO3 - 650
  • 150.75.85.245 - 150.75.85.254
  • 150.75.86.1 - 150.75.86.254
  • 150.75.87.1 - 150.75.87.254
  • 150.75.88.1 - 150.75.88.133
  • LO4 - 650
  • 150.75.88.134 - 150.75.88.254
  • 150.75.89.1 - 150.75.89.254
  • 150.75.90.1 - 150.75.90.254
  • 150.75.91.1 - 150.75.91.21
  • LO5 - 650
  • 150.75.91.22 - 150.75.91.254
  • 150.75.92.1 - 150.75.92.254
  • 150.75.93.1 - 150.75.93.163
  • RC1 - 520
  • 150.75.93.164 - 150.75.93.254
  • 150.75.94.1 - 150.75.94.254
  • 150.75.95.1 - 150.75.95.175
  • LO6 - 650 - subnet - 150.75.96.0 (150.75.96.1 - 150.75.111.254)
  • 150.75.96.1 - 150.75.96.254
  • 150.75.97.1 - 150.75.97.254
  • 150.75.9 8.1 - 150.75.98.141
  • LO7 - 650
  • 150.75.98.142 - 150.75.98.254
  • 150.75.99.1 - 150.75.99.254
  • 150.75.100.1 - 150.75.100.254
  • 150.75.101.1 - 150.75.101.29
  • LO8 - 650
  • 150.75.101.30 - 150.75.101.254
  • 150.75.102.1 - 150.75.102.254
  • 150.75.103.1 - 150.75.103.171
  • RC2 - 520
  • 150.75.103.172 - 150.75.103.254
  • 150.75.104.1 - 150.75.104.254
  • 150.75.105.1 - 150.75.105.183
  • LO9 - 650
  • 150.75.105.184 - 150.75.105.254
  • 150.75.106.1 - 150.75.106.254
  • 150.75.107.1 - 150.75.107.254
  • 150.75.108.1 - 150.75.108.71
  • LO10 - 650
  • 150.75.108.72 - 150.75.108.254
  • 150.75.109.1 - 150.75.109.254
  • 150.75.110.1 - 150.75.110.213
  • LO11 - 650
  • 150.75.110.214 - 150.75.110.254
  • 150.75.111.1 - 150.75.111.254
  • Subnet - 150.75.112.0 (150.75.112.1 - 150.75.127.254
  • 150.75.112.1 - 150.75.112.254
  • 150.75.113.1 - 1507.75.113.101

The next three questions relate to voice communications. Note that this topic was not covered in the class, but it is included to encourage self-learning, research, and analysis.

MyCo wants to know the impacts of putting Voice over IP with IP Phones. So, the same IP infrastructure (LAN-WAN) will carry voice as well. Since most other technologies are getting out of favor, it is decided that the intra-building network will be Ethernet LAN based.

Q5. For VOIP, first you need to consider the codec to use. Although there are many voice codecs, MyCo wants the safest bet and suggests that you design with the most known and oldest codec G.711 since they are very concerned about the voice quality with VoIP. Calculate the voice payload from G.711 codecs with 20ms. frames along with the RTP, UDP, IP, and Ethernet overhead to measure the bandwidth per call with G.711.

Q6. Now, you need to calculate the bandwidth required for supporting VoIP from each location based on the number of people at each location but considering that not everyone is going to call at the same time. Assume that no more than 25% of people are on the phone at any particular time at any location. That will give you the total bandwidth required from each location based on the number of people at each location and the required bandwidth per VoIP call that you calculated from Q5.

Q7. The second point to consider is that from each location, some calls are internal to that site and some are going to outside locations. Again, as an approximation, MyCo telecom people suggests to use a 50-50 rule (50% internal, 50% going out) for the LOs and 70-30 (70% internal, 30% going out) for the HQ and RC buildings. Given this, calculate bandwidth needed for voice traffic from each location going to other locations. The bandwidth needed for voice calls within each location is not needed because all locations must have broadband connectivity for internal communications.

Finally, answer the following two questions relating to the voice and data converged network over the same IP infrastructure that you designed.

Q8. Suggest physical technology, devices, and protocol choice for network design considering the 14 location (LAN/MAN/WAN), the addressing scheme you devised from question above, and the applications requirements.

Q9. State how the different IP-QoS needs for controling traffic, data and voice applications can be supported in your technology choice from Q7. Describe the specific IP-QoS schemes - the protocols and how they will be used to support the different applications.