Step 1: Gather the data traffic information
a. Read through the StadiumCompany case study curriculum.
List the current types of data traffic carried by the StadiumCompany network as well as the types
planned for the future.
b. Refer to the topology diagram and the stadium network diagram information.
List the possible data sources and destinations on the StadiumCompany network. For example, there
is likely to be data communications between the stadium management and the vendor management,
but not between Team A and Team B.
Step 2: Prioritize the data traffic
- List the source, destination, and traffic type that will be assigned the High priority queue.
- List the source, destination, and traffic type that will be assigned the Medium priority queue.
- List the source, destination, and traffic type that will be assigned the Normal priority queue
- List the source, destination, and traffic type that will be assigned the Low priority queue.
Step 3: Finalize the Data Priorities
a. Discuss and review your data priority assignments with another student to ensure that it addresses allnpossible data. Modify your priorities as necessary.
b. Highlight on the StadiumCompany topology diagram the device or devices where data traffic priority policies are likely to be configured.
Step 4: Reflection
Ideally, it may seem that all data traffic should be given a priority and queued accordingly. Consider and
discuss the potential for network performance to be negatively affected if this policy were implemented
everywhere on the network.
Delay data sensitif akan melihat prioritas yang sama sebagai non-delay data sensitif. Suara, video, diberi prioritas yang sama sebagai lalu lintas lainnya, dll