AAP – XUMUC Campus

AAP-11 Submittal
In the beginning, I said that your AAP comprise of two parts: One is group project and the other is writing a
paper or RFP. In group you have done most of the work and in this submittal you need to add implementation
plan as described below and rearranged the format as per guide line below (Also, see the text page 25).
In this part it is your choice how you want to work in a group or individually as you would be grading your
group members. Even, you decide, you want to work individually; still you can share your work.
AAP-II: (15% of the grade. It is graded by group members): For this section you will write a paper in the form
of RFP which include:
Executive Summary
Business goals for the project
Scope of the project
Information on existing network
Information on new applications
Technical requirements, including scalability, availability, network performance, security,
manageability, usability, adaptability, and affordability
Design solutions
Logical Diagram
Warranty requirements for products
Environmental or architectural constraints
Training and support requirements
Preliminary schedule with milestones and deliverables
Legal contractual terms and conditions
Estimated Cost
IP address Scheme
Your paper should include responses to all of customer’s RFP and should include logical and physical
component pf the design, information on technologies used in design solution, and proposal to implementing
the design. The following sections describe the format of the paper:
A: Executive Summary (ES)
The executive summary briefly states and emphasizes the major points of the customer’s requirements. The ES
should be no more than one page and should be directed at key decision maker of the project who will decide
whether to accept your design. The ES can have minimum technical information but NO technical details. The
technical information should be summarized and organized in order of the customer’s highest-priority
objectives for the design project. The ES should be organized customer top requirements.
B: Project Goal
This section should state the primary goal for the network design. The goal should be business oriented and
related to an overall objective that organization has to become more successful in core business. Your objective
is to make it clear to decision maker that you understand the primary purpose and importance of the network
design project. Below is an example of project goal was written for an actual design.
“The goal of this project is to develop a wide area network (WAN) that will support new high bandwidth and
low-delay multimedia applications. The new applications are key to the successful implementation of new
1 of 8 3/6/2013 8:02 AM
training programs for the sales force. The newWAN facilitate of increasing sales in the USAby 50% in the
next fiscal year.”
C: Project Scope:
The project scope section provides information on extent of the project, including a summary of departments,
field offices networks that will be affected by the project. The project scope section specifies whether the
project is new network or modifications to an existing network. It indicates whether the design is for a single
network segment, a set of LANs, a building or campus network, or a set of WAN or remote access network,
VoIP, or enhancing security. (Note: Here you can use it your group’s scope of work as it is or change it the way
you want).
D: Design Requirements:
In this section, you provide major business and technical requirements of the network in priority order. In
business goal explain the role network design will play in helping an organization provide better products and
In Technical requirement section explain in general term how propose technical improvement is better than or
meet the customer requirement.
Network Application: This section lists and characterizes the new and existing network applications.
E: Current State of the Network:
This section briefly describes the structure and performance of the network. It should include a high-level
network map that identifies the location of connecting devices, server farm, storage systems, and network
F: Design Solution:
This section includes:
Logical Network topology which include high level one or more drawings to illustrate logical
architecture of the proposed network
Aplan of addressing network segments and devices
Aplan of naming network devices which include routers, workstations, servers, and network segment.
Alist of routing, switching protocols that have been selected to implement design
Recommended Voice over IP solution, and mechanism to implement them
Recommended security mechanisms and products, including a summary of security policies.
Recommended network management processes and products
G: Implementation Plan:
The implementation plan includes your recommendations for deploying the network design. The design
implementation description should be detailed as possible. Implementation of a network design consists of
several phases (buy and install hardware, configure system, test system and so forth). Each phase consists of
several steps, and documentation for each step should contain the following:
Aproject schedule
Plans with vendors or service providers for installation of links, equipment or services
Plan or recommendations for outsourcing the implementation or management of the network
Aplan for communicating the design to end users, network administrators, and management
Atraining plan for network administrators and end users
Aplan for measuring the effectiveness of the design after it has been implemented

Alist of known risks that could delay the project
Afallback plan if the network implementation fails
Apan for evolving the network design as new application requirements goals arise
Below are configuration sample and project schedule templates
ImplementaƟon and Tune HSRP:
Device InformaƟon
Device HSRP IP Address VLAN 3 IP Address VLAN 4 HSRP Address
ASW1 No ——– ——– ——–
ASW2 No ——– ——– ——–
DSW1 Yes
DSW2 Yes
CSW1 No ——– ——– ——–
CSW2 No ——– ——– ——–
Router 1 No ——– ——– ——–
Router 2 No ——– ——– ——–
First Task: Create an implementaƟon and requirement lists
Device ImplementaƟon Requirement List Content
DSW1 HSRP ImplementaƟon Policy
DSW2 HSRP ImplementaƟon Policy
Second Task: Create a High-Level ConfiguraƟon Task
Device High-Level ConfiguraƟon ask InformaƟon Source
DSW1 HSRP on VLAN 3 and VLAN 4
Primary VLAN3 and Sec VLAN4
ImplementaƟon List
DSW2 HSRP on VLAN 3 and VLAN 4
Primary VLAN4 and Sec VLAN3
ImplementaƟon List
Device ImplementaƟon
Values and Items to
VerificaƟon Method

DSW1 1 Interface VLAN3
DSW1 2 IP address
Show interface VLAN 3
DSW1 3 Standby 3 IP
DSW1 4 Standby 3 priority 120
DSW1 5 Standby 3 preempt
DSW1 6 Standby 3 track Port
Channel 31, 30
Show standby
DSW1 7 Standby 3 track Port
Channel 14, 30
DSW1 8 Interface VLAN3
DSW1 9 IP address
Show interface VLAN 4
DSW1 10 Standby 4 IP
DSW1 11 Standby 4 preempt Show standby
DSW2 12 Interface VLAN3
DSW2 13 Standby 3 IP
DSW2 14 Standby 3 preempt Show standby
DSW2 15 Interface VLAN4
DSW2 16 Standby 4 IP
DSW2 17 Standby 4 priority 120
DSW2 18 Standby 4 preempt
DSW2 19 Standby 4 track Port
Channel 31, 30
DSW2 20 Standby 4 track Port
Channel 32, 30
Show standby
Configuring HSRP on VLAN 3
DSW1 (config)# interface VLAN 3
DSW1 (config-if)# ip address
DSW1 (config-if)# standby 3 ip
DSW1 (config-if)# standby 3 priority 120
DSW1 (config-if)# standby 3 preempt
DSW1 (config-if)# standby 3 track Port-channel 31 30
DSW1 (config-if)# standby 3 track Port-channel 32-30
Configuring HSRP on VLAN 4
DSW1 (config)# interface VLAN 4
DSW1 (config-if)# ip address
DSW1 (config-if)# standby 4 ip
DSW1 (config-if)# standby 4 preempt

Configuring HSRP on VLAN 3 DSW2
DSW2 (config)# interface VLAN 3
DSW2 (config-if)# standby 3 ip
DSW2 (config-if)# standby 3 preempt
Configuring HSRP on VLAN 4 DSW2
DSW2 (config)# interface VLAN 4
DSW2 (config-if)# standby 4 IP
DSW2 (config-if)# standby 4 priority 120
DSW2 (config-if)# standby 4 preempt
DSW2 (config-if)# standby 4 track Port-channel 31 30
DSW2 (config-if)# standby 4 track Port-channel 32 30
DSW1# show standby
VLAN63 – Group 63
State is acƟve
Virual IP address is
AcƟve virtual MAC address is 0000.0c07.ac3f (v1 default)
Hello Ɵme 3 sec, hold Ɵme 10 sec
Next hello sent in 1.664 secs
PreempƟon enabled
AcƟve router is local
Standby router is, priority 90 (expires in 11.200 secs)
Priority 120 (configured 120)
Track interface Port-channel 31 state Up decrement 30
Track interface Port-channel 32 state Up decrement 30
Group name is “hsrp-VL63-63” (default)
VLAN64 – Group 64
State is acƟve
Virual IP address is
AcƟve virtual MAC address is 0000.0c07.ac40

Local virtual MAC address is 0000.0c07.ac40 (v1 default)
Hello Ɵme 3 sec, hold Ɵme 10 sec
Next hello sent in 0.688 secs
PreempƟon enabled
AcƟve router is, priority 120 (expires in 9.232 sec)
Standby router is local
Priority 90 (configured 90)
Group name is “hsrp-VL64-64” (default)
Sample Project Schedule Template
Date of
Project Milestone
August 1 Design completed and a beta version of the design document distributed
to key executives, managers, network administrators, and end users
(end users depends on management)
August 15 Comments on the design document due
August 22 Final design document distributed
August 25 Installation of leased lines between all buildings completed by WAN
service provider
August 28-29 Network administrators trained on new system
August 30-31 End users trained on new system
September 6 Pilot implementation completed in Building 1 or head office or branch
September 20 Feedback received on pilot from network administrators and users
September 27 Implementation completed on Buildings 2-5 or floors 1-6
October 10 Feedback received from buildings 2-5 from network administrators and
October 17 Implementation completed in the rest of buildings or floors
Ongoing or
December 31
New system monitored to verify that it meets goals
H: Project Budget
This section should contain the funds the customer needs for equipment purchases, maintenance, and support
agreements, service contracts, software licenses, training, and staffing. The budget can also include consulting
fees and outsourcing expenses.
Appendix K: Budget Report

I: Design Document Appendix
Most design documents include one or more appendixes that present supplemental information about the
design and implementation. Supplemental information can include detailed topology drawings, device
configurations, network addressing and naming details and comprehensive results from the testing of the
network design. You can include business information such as list of contact name, numbers and e-mail
addresses. The appendix can include warranty on devices, legal agreement, and any information which is not
critical for design, but you have noted in your gathering information process.

Use the order calculator below and get started! Contact our live support team for any assistance or inquiry.