Juniper Networks Design Fundamentals-15 b-R_SG_v1of2

Prévia do material em texto

SH
AR
E
Juniper Networks Design 
Fundamentals
15.b
Student Guide
Volume 1 of 2
US
E 
ON
LY
 —
 D
O 
NO
T 
1133 Innovation Way
Sunnyvale, CA 94089
USA
408-745-2000
www.juniper.net
Worldwide Education ServicesWorldwide Education Services
NA
L 
Course Number: EDU-JUN-JNDFER
IN
T
This document is produced by Juniper Networks, Inc.
This document or any part thereof may not be reproduced or transmitted in any form under penalty of law, without the prior written permission of Juniper Networks Education 
Services. 
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The 
Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service RE
marks are the property of their respective owners.
Juniper Networks Design Fundamentals Student Guide, Revision 15.b
Copyright © 2015 Juniper Networks, Inc. All rights reserved. 
Printed in USA.
Revision History:
Revision 15.a—March 2015.
Revision 15.b—June 2015.
The information in this document is current as of the date listed above.
The information in this document has been carefully verified and is believed to be accurate. Juniper Networks assumes no responsibilities for any inaccuracies that may 
appear in this document. In no event will Juniper Networks be liable for direct, indirect, special, exemplary, incidental, or consequential damages resulting from any defect or 
omission in this document, even if advised of the possibility of such damages.
O 
NO
T 
SH
A
Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
YEAR 2000 NOTICE
Juniper Networks hardware and software products do not suffer from Year 2000 problems and hence are Year 2000 compliant. The Junos operating system has no known 
time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
SOFTWARE LICENSE
The terms and conditions for using Juniper Networks software are described in the software license provided with the software, or to the extent applicable, in an agreement 
executed between you and Juniper Networks, or Juniper Networks agent. By using Juniper Networks software, you indicate that you understand and agree to be bound by its 
license terms and conditions. Generally speaking, the software license restricts the manner in which you are permitted to use the Juniper Networks software, may contain 
prohibitions against certain uses, and may state conditions under which the license is automatically terminated. You should consult the software license for further details.
IN
TE
RN
AL
 U
SE
 O
NL
Y 
—
 D
Contents
Chapter 1: Course Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Chapter 2: Network Design Fundamentals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
A Need for Network Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Knowledge Is King . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
A Proposed Design Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
A Reference Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Chapter 3: Understanding Customer Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
RFP Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Scoping the Design Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Analyzing the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Lab: Understanding Customer Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Chapter 4: Organizing the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Processing the Data and Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Identifying Boundaries and Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Design Proposal Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Chapter 5: Securing the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Why Secure the Network? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Security Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Chapter 6: Creating the Design—Campus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
The Campus Network: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Best Practices and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Architectural Design Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
Lab: Creating the Design—Campus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
Chapter 7: Creating the Design—WAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
The WAN: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Best Practices and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
WAN Design Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Lab: Creating the Design—WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Chapter 8: Creating the Design—Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
The Data Center: An Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Best Practices and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Data Center Design Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Lab: Creating the Design—Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Contents • iiiI
Chapter 9: Business Continuity and Network Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Business Continuity Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
High Availability Design Considerations and Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10
High Availability Offerings and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Acronym List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACR-1
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
iv • Contents www.juniper.netI
Course Overview
This three-day course is designed to cover introductory best practices, theory, and design principles for overall network 
design and will serve as the prerequisite course for other design subject areas — data center, security, and WAN. 
Objectives
After successfully completing this course, you should be able to:
• Provide an overview of network design needs and common business requirements.
• Describe key product groups related to campus, WAN, data center, and security architectures.
• Analyze and interpret common RFP requirements.
• Scope a network design by gathering data and working with key stakeholders.
• Describe ways of processing customer data and design requests.
• Identify boundaries and scope for the design proposal.
• List common considerations when creating a design proposal.
• Provide an overview of network security design and common vulnerabilities.
• List high-level design considerations and best practices for securing the network.
• List the components of the campus network design.
• Describe best practices and design considerations for the campus.
• Describe architectural design options for the campus.
• List the components of the WAN.
• Describe best practices and design considerations for the WAN.
• Describe design options for the WAN.
• List the components of the data center design.
• Describe best practices and design considerations for the data center.
• Describe architectural design options for the data center.
• Define business continuity and its importance in network design.
• Describe high availability design considerations and best practices.
• Provide an overview of high availability offerings and solutions.
• Describe class of service (CoS) design considerations.
• Provide an overview of environmental considerations in network design.
• List design considerations and best practices for managing the network.
• Provide an overview of Juniper Networks and third party options for network management.
• List design considerations and best practices for network automation.
• Provide an overview of automation tools.
• Explain the foundational topics that have been taught throughout the course.
• Create a network design proposal that satisfies customer requirements and business needs.
• Provide an overview of the steps involved in migrating a network.
• Describe best practices used in network migration.
• List the various campus network topographies.
• Describe sample design options for the campus.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Overview • vI
Intended Audience
This course is targeted for Juniper Networks system engineers, partner sales engineers (including Champions), and 
services partners who are interested in learning network design introductory concepts. However, the course is also 
applicable to a general audience of Juniper customers with a desire to learn more about network design. 
Course Level
Juniper Networks Design Fundamentals is an associate-level course. 
Prerequisites
The prerequisites for this course are as follows:
• Understanding of the OSI model and TCP/IP;
• Knowledge of routing architectures and protocols;
• Knowledge of switching architectures and protocols;
• Knowledge of Juniper Networks products and solutions;
• Understanding of infrastructure security principles; and
• Basic knowledge of hypervisors and load balancers.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
vi • Course Overview www.juniper.netI
Course Agenda
Day 1
Chapter 1: Course Introduction
Chapter 2: Network Design Fundamentals
Chapter 3: Understanding Customer Requirements
Lab: Understanding Customer Requirements
Chapter 4: Organizing the Data
Chapter 5: Securing the Network
Day 2
Chapter 6: Creating the Design—Campus
Lab: Creating the Design—Campus
Chapter 7: Creating the Design—WAN
Lab: Creating the Design—WAN
Chapter 8: Creating the Design—Data Center
Lab: Creating the Design—Data Center
Chapter 9: Business Continuity and Network Enhancements
Day 3
Chapter 10: Network Management
Chapter 11: Automation
Lab: Enhancing the Design
Chapter 12: Putting Network Design into Practice
Lab: Final Project
Appendix A: Network Migration Strategies
Appendix B: Sample Campus Designs
Appendix C: Sample Response to RFP
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Agenda • viiI
Document Conventions
CLI and GUI Text
Frequently throughout this course, we refer to text that appears in a command-line interface (CLI) or a graphical user 
interface (GUI). To make the language of these documents easier to read, we distinguish GUI and CLI text from standard 
text according to the following table.
Style Description Usage Example 
Franklin Gothic Normal text. Most of what you read in the Lab Guide and 
Student Guide.
Console text:
GUI text elements:
Select File > Open, and then click 
Configuration.conf in the Filename 
text box.
Input Text Versus Output Text
You will also frequently see cases where you must enter input text yourself. Often these instances will be shown in the 
context of where you must enter them. We use bold style to distinguish text that is input versus text that is simply 
displayed.
Style Description Usage Example
Normal CLI
Normal GUI
No distinguishing variant. Physical interface:fxp0, Enabled
View configuration history by clicking 
Configuration > History.
CLI Input
GUI Input
Text that you must enter.
Select File > Save, and type config.ini 
in the Filename field.
 
Defined and Undefined Syntax Variables
Finally, this course distinguishes between regular text and syntax variables, and it also distinguishes between syntax 
variables where the value is already assigned (defined variables) and syntax variables where you must assign the value 
(undefined variables). Note that these styles can be combined with the input style as well. 
Style Description Usage Example
CLI Variable
GUI Variable
Text where variable value is already 
assigned.
policy my-peers
Click my-peers in the dialog.
CLI Undefined
GUI Undefined
Text where the variable’s value is the 
user’s discretion or text where the 
variable’s value as shown in the lab 
guide might differ from the value the 
user must input according to the lab 
topology.
Type set policy policy-name.
ping 10.0.x.y
Select File > Save, and type filename in 
the Filename field.
Courier New
• Screen captures
• Noncommand-related syntax
• Menu names
• Text field entry
commit complete
Exiting configuration mode 
lab@San_Jose> show route
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
viii • Document Conventions www.juniper.netI
Additional Information
Education Services Offerings
You can obtain information on the latest Education Services offerings, course dates, and class locations from the World 
Wide Web by pointing your Web browser to: http://www.juniper.net/training/education/.
About This Publication
The Juniper Networks Design Fundamentals Student Guide is written and maintained by the Juniper Networks Education 
Services development team. Please send questions and suggestions for improvement to training@juniper.net.
Technical Publications
You can print technical manuals and release notes directly from the Internet in a variety of formats: 
• Go to http://www.juniper.net/techpubs/.
• Locate the specific software or hardware release and title you need, and choose the format in which you 
want to view or print the document.
Documentation sets and CDs are available through your local Juniper Networks sales office or accountrepresentative.
Juniper Networks Support
For technical support, contact Juniper Networks at http://www.juniper.net/customers/support/, or at 1-888-314-JTAC 
(within the United States) or 408-745-2121 (outside the United States).
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Additional Information • ixI
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
x • Additional Information www.juniper.netI
HA
RE
Juniper Networks Design Fundamentals 
Chapter 1: Course Introduction
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
S
IN
T
Juniper Networks Design Fundamentals 
We Will Discuss:
• Objectives and course content information;
• Additional Juniper Networks, Inc. courses; and
• The Juniper Networks Certification Program.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–2 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
Introductions
The slide asks several questions for you to answer during class introductions. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–3I
Juniper Networks Design Fundamentals 
Course Contents: Part 1
The slide lists the topics we discuss in this course.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–4 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
Course Contents: Part 2
The slide lists the remainder of the topics we discuss in this course.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–5I
Juniper Networks Design Fundamentals 
Prerequisites
The slide lists the prerequisites for this course.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–6 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
General Course Administration
The slide documents general aspects of classroom administration.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–7I
Juniper Networks Design Fundamentals 
Training and Study Materials
The slide describes Education Services materials that are available for reference both in the classroom and online.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–8 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
Additional Resources
The slide provides links to additional resources available to assist you in the installation, configuration, and operation of 
Juniper Networks products.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–9I
Juniper Networks Design Fundamentals 
Satisfaction Feedback
Juniper Networks uses an electronic survey system to collect and analyze your comments and feedback. Depending on the 
class you are taking, please complete the survey at the end of the class, or be sure to look for an e-mail about two weeks 
from class completion that directs you to complete an online survey form. (Be sure to provide us with your current e-mail 
address.)
Submitting your feedback entitles you to a certificate of class completion. We thank you in advance for taking the time to 
help us improve our educational offerings.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–10 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
Juniper Networks Education Services Curriculum
Juniper Networks Education Services can help ensure that you have the knowledge and skills to deploy and maintain 
cost-effective, high-performance networks for both enterprise and service provider environments. We have expert training 
staff with deep technical and industry knowledge, providing you with instructor-led hands-on courses in the classroom and 
online, as well as convenient, self-paced eLearning courses.
Courses 
You can access the latest Education Services offerings covering a wide range of platforms at 
http://www.juniper.net/training/technical_education/.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–11I
Juniper Networks Design Fundamentals 
Juniper Networks Certification Program
A Juniper Networks certification is the benchmark of skills and competence on Juniper Networks technologies. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–12 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
Juniper Networks Certification Program Overview
The Juniper Networks Certification Program (JNCP) consists of platform-specific, multitiered tracks that enable participants 
to demonstrate competence with Juniper Networks technology through a combination of written proficiency exams and 
hands-on configuration and troubleshooting exams. Successful candidates demonstrate a thorough understanding of 
Internet and security technologies and Juniper Networks platform configuration and troubleshooting skills. 
The JNCP offers the following features:
• Multiple tracks;
• Multiple certification levels;
• Written proficiency exams; and
• Hands-on configuration and troubleshooting exams.
Each JNCP track has one to four certification levels—Associate-level, Specialist-level, Professional-level, and Expert-level. The 
Associate-level, Specialist-level, and Professional-level exams are computer-based exams composed of multiple choice 
questions administered at Pearson VUE testing centers worldwide. 
Expert-level exams are composed of hands-on lab exercises administered at select Juniper Networks testing centers. Please 
visit the JNCP website at http://www.juniper.net/certification for detailed exam information, exam pricing, and exam 
registration.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–13I
Juniper Networks Design Fundamentals 
Preparing and Studying
The slide lists some options for those interested in preparing for Juniper Networks certification.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–14 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
Junos Genius 
The Junos Genius application takes certification exam preparation to a new level. With Junos Genius you can practice for 
your exam with flashcards, simulate a live exam in a timed challenge, and even build a virtual network with device 
achievements earned by challenging Juniper instructors. Download the app now and Unlock your Genius today!
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–15I
Juniper Networks Design Fundamentals 
Find Us Online
The slide lists some online resources to learn and share information about Juniper Networks.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–16 • Course Introduction www.juniper.netI
Juniper Networks Design Fundamentals 
Any Questions?
If you have any questions or concerns about the class you are attending, we suggest that you voice them now so that your 
instructor can best address your needs during class.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Course Introduction • Chapter 1–17I
Juniper Networks Design Fundamentals 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 1–18 • Course Introduction www.juniper.netI
HA
RE
Juniper Networks Design Fundamentals
Chapter 2: Network Design Fundamentals
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
S
IN
T
Juniper Networks Design Fundamentals
We Will Discuss:
• Network design needs and common business requirements; and
• Key product groups related to campus, WAN, data center, and security architectures.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–2 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
A Need for Network Design
The slide lists the topics we will discuss. We discuss the highlighted topic first.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NOT 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–3I
Juniper Networks Design Fundamentals
You Are the Architect
Imagine the role of a building architect. The process of creating a new building typically goes through various stages of 
planning, designing, and construction. The architect must consider environmental impact, governing laws in the surrounding 
area, building functionality, and aesthetic style. A successful architectural plan can result in a beautiful building that will 
withstand the tests of time. Indeed, some of the oldest buildings in the world not only have withstood the tests of time, they 
have transformed the cities where they were built, and changed the lives of the architects who designed them!
You are a network designer; thus, you are an architect who builds networks. Network architecture is a lot like building 
architecture—you must consider proper planning, design, flow, and construction of the network you are about to design. 
Many of the key elements you must understand are listed on the slide. We will discuss these elements in greater detail 
throughout this content. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–4 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Doing the Research
Before you sit down for your first meeting with the customer, it’s important that you understand who your customer is—
beyond the name or title on the business cards. You must fully research what your customer is doing as a business. What do 
they sell? What is their industry? How are they organized structurally? What sets your customer apart from their 
competitors? As you start to put the pieces of your customer’s puzzle together, you will start to understand what potential 
network designs you can offer that will meet their approval.
Your First Meeting
Your first discussion with the customer should be to understand business requirements and establish goals. Early on, you 
should understand from the customer what their overall goal for the network design project is. What are the benefits and 
risks to designing a new network? What will be considered “success” to key stake holders? Answering these questions early 
is imperative to building a network that suits—and exceeds—the customer’s needs. Consider that business requirements and 
goals might change as you work on your design plan, so the process of establishing goals and understanding business 
requirements is cyclical. We discuss engaging the customer more on the next slide.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–5I
Juniper Networks Design Fundamentals
Engaging with the Customer
Understanding the customer you are designing for takes more than searching the Internet or reading a few publications. You 
likely will not fully understand the customer and what they do without becoming a partner with them—that is to say—seeing 
the company as its leaders see it. You must understand who the stake holders are. How visible is the project to leaders of the 
organization? More importantly, how critical is this project to them? Do you personally view this project as equally important? 
As you work closely with the customer to understand what their overall goal is, you will better know what is required to create 
a successful design that meets or exceeds any goals the customer has. If you know where the risks and consequences are 
should the project fail, you are beginning to understand the customer. If your desire to succeed is based less on how much 
you get paid, but is based more on seeing the customer’s goals as important to you, then you are starting to think like the 
customer. You are partnering with them on the road to building a successful network design.
Engaging with the Customer Requires Back and Forth Communication
In the classic video game Pong, two players simulate a table tennis match and attempt to hit a ball back and forth until the 
opposing player misses the ball. Often, the game might seem to last an eternity because the opposing player is able to 
respond to your attempts to score a point. Engaging the customer will often feel like a game of Pong because there is so 
much “back-and-forth” when creating a design to fit the customer’s needs. However, unlike Pong, there is no attempt in this 
back-and-forth communication to beat the customer by scoring more points than them. Instead, the questions and answers 
that result from the back-and-forth communication should eventually result in 100 percent satisfaction with the network 
design plan. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–6 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Knowledge Is King
The slide highlights the topic we discuss next.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–7I
Juniper Networks Design Fundamentals
What’s in the Tool Bag?
Understanding who the customer is and what type of business they offer is only part of the equation for building a successful 
network. You are the architect and you represent Juniper Networks; thus, you are responsible for knowing what products and 
solutions Juniper Networks can offer. Network design, however, is a team effort. The thought might seem ridiculous, but a 
building architect would never set out to build a skyscraper without any help. You might not be a subject matter expert (SME) 
for every solution that Juniper Networks offers, but as the architect, you will know who the SMEs are and with whom to 
surround yourself in order to make an efficient team. 
Although you will often rely on SMEs for specific recommendations on the design, you are still the lead architect, so you want 
to be very comfortable discussing Juniper Networks’ solutions and specific platforms. We highlight these solutions on the 
next several slides.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–8 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Overview of Junos Devices
While this course does not focus on platform specifics or configuration options for any specific platform, it is important that 
you understand the solution that Juniper Networks offers and how you can incorporate that into your design.
Juniper Networks offers a wide variety of solutions in routing, switching, and security. These devices run the Junos OS; 
meaning, all of the devices shown on the slide run on a single network operating system. The Junos OS offers the power of a 
single operating system that can reduce complexity, achieve operational excellence, and dynamically deliver services with 
lower Total Cost of Ownership (TCO). 
Running devices on a single operating system means that the software for those devices is developed along a single 
software release train and built on one modular software architecture, as depicted in the slide above.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–9I
Juniper Networks Design Fundamentals
Junos Routing Devices
The following are some of the routing devices that run the Junos OS:
• The ACX Series products deliver simplified end-to-end provisioning and support Layer 2 and Layer 3 
functionality with IP/MPLS traffic engineering. The fixed 1 U ACX Series models are environmentally hardened 
and support passive cooling (fan-less design) for outdoor deployments. 
• The LN Series provides high-performance network routing, firewall, and intrusion detection service (IDS) for 
harsh environments, including terrestrial, air, and sea vehicles and remote data aggregation points.
• The M Series multiservice routers provide up to 320 Gbps of aggregate half-duplex throughput. The M Series 
family can be deployed in both high-end enterprise and service-provider environments. Large enterprises deploy 
M Seriesrouters in a number of different roles, including Internet gateway router, WAN connectivity router, 
campus core router, regional backbone and data center routers. In service-provider environments, the M Series 
router operates predominantly as a multiservice edge router, but you can also deploy it in small and medium 
cores, and in peering, route reflector, multicast, mobile, and data-center applications. 
• The T Series core routers provide up to 25.6 Tbps of throughput. The T Series family is ideal for service provider 
environments and is deployed within the core of those networks. 
• The PTX Series packet transport switches provide up to 16 Tbps of throughput in a single chassis. The PTX 
Series family is ideal for the service provider supercore and can readily adapt to today’s rapidly changing traffic 
patterns for video, mobility and cloud-based services. 
Continued on the next page.NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–10 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Junos Routing Devices (contd.)
The following are some more of the routing devices that run the Junos OS:
• The MX Series Ethernet services routers provide up to 34.4 Tbps of aggregate half-duplex throughput today, 
with scalability to 80 Tbps in the future. The MX Series family is targeted for dense dedicated access 
aggregation and provider edge services in medium and large points of presence (POPs). Large enterprise 
environments and service providers can leverage MX Series Ethernet services routers for a variety of network 
functions including Ethernet transport and aggregation, and can use them to offer new Ethernet-based 
services. 
Other devices, such as SRX Series, also provide routing. For more information on all of Juniper’s routing devices, go to 
http://www.juniper.net/us/en/products-services/routing/.
Note
For simplification purposes, we focus primarily 
on the MX Series as a routing device throughout 
the course.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–11I
Juniper Networks Design Fundamentals
Positioning MX Series Devices
The slide lists the different MX Series devices available and where they are typically positioned. MX Series devices are 
typically considered for the network edge. When selecting a routing device for network design, you must consider throughput 
requirements, capacity, scale, and overall performance. 
More information on MX Series devices can be found on the Juniper Website.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–12 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Junos Switching Devices
The following are some of the switching devices that run the Junos OS:
• The EX Series Ethernet switches provide up to 6.2 Tbps of full duplex throughput. The EX Series switches are 
designed for access, aggregation, and core deployments and are well suited for low-density to high-density 
enterprise and data center environments. 
• The QFX Series switches are high-performance, low-latency platforms for top-of-rack or end-of-row installations. 
They can also be deployed as 10 GbE, 40 GbE or100GbE access, spine, core or aggregation devices in Virtual 
Chassis, Virtual Chassis Fabric, Multi-Chassis LAG and Junos Fusion architectures.
• The OCX Series open networking switches provide the Junos OS software with cloud-optimized, open source 
switching hardware built on commercially sourced components, as defined by the industry-recognized Open 
Compute Project (OCP) Foundation. OCX Series switches deliver cost-effective switching for customers that 
require massive-scale cloud deployments. 
For more information on Juniper’s switching devices, go to http://www.juniper.net/us/en/products-services/switching/.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–13I
Juniper Networks Design Fundamentals
Positioning Ethernet Switches
The slide pinpoints where both EX Series and QFX Series devices are typically positioned. EX Series devices can offer 
throughput speeds of up to 240 Gbps per slot (full duplex), where QFX Series devices can offer up to 2.56 Tbps per slot. 
Form factor, density, and economics should be considered when positioning a switching device. 
For specifics on EX Series and QFX Series devices, see the Juniper Website.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–14 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Junos Security Devices
The following is one of the security devices that run the Junos OS:
• The SRX Series services gateways provide up to 120 Gbps of full duplex throughput. The SRX Series family is 
designed to meet the network and security requirements for consolidated data centers, managed services 
deployments, and aggregation of security services in both enterprise and service provider environments. 
For more information on all of Juniper’s switching devices, go to http://www.juniper.net/us/en/products-services/security/. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–15I
Juniper Networks Design Fundamentals
Positioning SRX Series Devices
Juniper hardware platforms cover a broad range to meet the specific needs of any deployment. The SRX platform runs from 
branch office CPE suitable for managed service offerings to Campus platforms and all the way to high end modular systems 
capable of running at up to 2 Tbs for the most demanding enterprise, data center, and service provider deployments. 
For more information on SRX Series devices, see the Juniper Website.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–16 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
vSRX
Virtualization technologies have taken the data center by storm in recent years. Gartner, a technology research company, 
predicts that over 70% of server workloads will be virtualized in just a few short years. Data center virtualization and cloud 
computing technologies enable agility that accelerate the implementation of all kinds of new applications, technologies, and 
features. But this new, faster speed of change brings on new security risks just as quickly.
vSRX can address the security challenges of virtualization.vSRX is a virtual version of the Junos OS, which runs as a virtual 
machine (VM) using either VMware or KVM as the host software. vSRX delivers in a VM the Junos OS and SRX Series 
advanced security for branch SRX Series devices. It protects VM traffic and the virtualized network at the tenant virtual 
network edge. 
For additional, in-depth details on vSRX, go to https://www.juniper.net/us/en/products-services/security/firefly-perimeter/.
vMX
We discussed MX Series edge routers previously. The vMX virtual router is a full-featured carrier-grade router that offers the 
same quality and features of the physical MX Series platform. The vMX provides complete control, forwarding, and 
management planes. vMX support vTrio packet handling and forwarding by compiling the programmable Junos Trio chipset 
microcode for x86 chipsets. 
For additional, in-depth details on the vMX Series, go to 
https://www.juniper.net/us/en/products-services/routing/mx-series/vmx/.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–17I
Juniper Networks Design Fundamentals
Other Key Solutions
There are many products that Juniper Networks, in addition to the Junos OS based platforms we have discussed in this 
content. These solutions should also be included as part of your design proposal:
• Junos Space: Comprehensive network management solution that simplifies and automates management of 
Juniper’s switching, routing, and security devices. For more information on Junos Space, go to http://www.juniper.net/us/en/products-services/network-management/junos-space-platform/.
• Juniper Networks Secure Analytics, (JSA): Security Information and Event Management (SEIM) that 
consolidates large volumes of event data from thousands of both Juniper and non-Juniper devices, endpoints, 
and applications in near real time. For more information on JSA, go to 
http://www.juniper.net/us/en/products-services/security/secure-analytics/.
Partner Solutions
Juniper works with many partners to provide solutions to needs that Juniper cannot necessarily fulfill. Examples of these 
solutions include partnerships to provide secure remote access, network access control, load balancing, and wireless 
access. For more information on some of these partnerships, see the Juniper Website.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–18 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Understanding the Competition
If you are to successfully sell a design plan that incorporates solutions from Juniper Networks, you will need to know your 
competition, what they offer, and how their solution matches up with what you have to offer. In some instances, the customer 
might only be familiar with proprietary systems or protocols due to their experience with a competitor. In these situations, you 
can often counter with a similar solution that Juniper Networks offers, but is compliant with standards that will allow for 
greater scalability in the future. 
In some situations, you will need to build a design around an existing solution from a competitor. You might need to design a 
solution that can live in harmony with other vendors. This means switching from proprietary services to using more 
standardized protocols. In all cases, you should be able to understand and easily explain how your design will respond to 
questions regarding the competition.
Confidence is Key
Regardless of who your customer has worked with in the past, or what equipment is in their current environment, you must 
be able to show total confidence in your network design. Feeling comfortable with your design means that you can provide 
immediate feedback when customers ask questions related to competing services. Do not focus on what your solution can’t 
provide. Likely, there is an alternate solution that your design will provide that can meet any challenge from competing 
products. Customers—and people in general—can be wary of change. Understanding what you do best and focusing on those 
key areas will help the customer gain confidence in your plan. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–19I
Juniper Networks Design Fundamentals
A Proposed Design Methodology
The slide highlights the topic we discuss next.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–20 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Juniper’s Lifecycle Service Approach
Juniper follows a simple lifecycle approach when designing a network for a customer. This approach consists of three main 
phases and is often cyclical through the lifetime of the design:
1. Plan: 
a. Assess the current environment and its ability to satisfy the customer’s business and technology 
requirements. 
b. Design high-level architectural plans, as well as low-level detailed plans of network devices, 
configurations, and interconnections. 
2. Build:
a. Deploy the design in both test and production environments. 
b. Migrate from the existing environment to the new environment. Provide installation and configuration, 
system testing, and system enablement.
3. Operate:
a. Support the customer by focusing on the most effective use of the solution. Provide support for any 
issues and faults, as well as proactive maintenance. 
b. Optimize the network as more systems and users come online, and as system usage increases.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–21I
Juniper Networks Design Fundamentals
Plan Methodology
In this course, we focus primarily on the design—or Plan—phase of the service lifecycle. This phase consists of two main 
sub-phases:
1. Assess the current environment and its ability to satisfy the customer’s business and technology requirements.
a. Identify the technology shortfalls that need to be addressed as well as develop a Core technology 
roadmap that will achieve the customer’s required end-game environment. Evaluate what is necessary 
for migrating successfully from one environment to the other. 
b. Determine the scope of the design project. For example, the customer might need a design as small as a 
network segment, or as large as an entire enterprise network. Is the network a simple upgrade from an 
existing environment, or will you be creating an entirely new network?
c. Perform a data analysis to determine the condition of the current network and what improvements need 
to be made based on customer requirements and scope of the design. How does the business drive the 
data used on the network? How many users access the network internally and externally? 
2. Design high-level architectural plans, as well as low-level detailed plans of network devices, configurations, and 
interconnections. Create a project plan. Evaluate and detail responsibilities, timelines, and dependencies.
a. The High-level design typically is the logical topology that identifies protocols used, network addressing, 
security, and naming conventions. The design also might include WAN and service provider access.
b. The low-level design is the physical design and consists of physical devices that will be used in the 
design, cabling and wiring considerations. Service provider access should be determined by this point.NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–22 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
A Reference Network
The slide highlights the topic we discuss next.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–23I
Juniper Networks Design Fundamentals
Putting It All Together
Throughout this content, we have discussed the importance of knowing who your customer is and what Juniper Networks 
solutions you can use to create a successful network design. The slide, although overly simplified, clearly illustrates where a 
variety of devices might be positioned in the key focus areas, (campus and branch offices, WAN, and the data center). If you 
were to include a high-level diagram in a proposal to a customer such as the one on the slide, you would likely include a more 
detailed physical diagram with product and wiring specifics. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–24 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
We Discussed:
• Network design needs and common business requirements; and
• Key product groups related to campus, WAN, data center, and security architectures.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–25I
Juniper Networks Design Fundamentals
Review Questions
1.
2.
3.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–26 • Network Design Fundamentals www.juniper.netI
Juniper Networks Design Fundamentals
Answers to Review Questions
1.
If you understand your customer, you understand how their business drives the networking needs of the company. You understand 
who the stake holders are and how visible the project is to decision makers within the company. You understand the importance of the 
project and how your design will benefit the company and help them grow their business.
2.
The three main types of devices that run the Junos OS are routing, switching, and security devices.
3.
The threephases of Juniper Network’s lifecycle service approach are Plan, Build, and Operate.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Network Design Fundamentals • Chapter 2–27I
Juniper Networks Design Fundamentals
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 2–28 • Network Design Fundamentals www.juniper.netI
HA
RE
Juniper Networks Design Fundamentals
Chapter 3: Understanding Customer Requirements
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
S
IN
T
Juniper Networks Design Fundamentals
We Will Discuss:
• Analyzing and interpreting common Request for Proposal (RFP) requirements; and 
• Scoping a network design by gathering data and working with key stakeholders.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–2 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
RFP Requirements
The slide lists the topics we will discuss. We discuss the highlighted topic first.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–3I
Juniper Networks Design Fundamentals
Design Methodology: Assess
Juniper Networks believes in a systematic, three phase approach to building networks: Plan, Build, and Operate. In this 
course, we focus primarily on the planning phase of the design. Before any network can be designed, you must first assess 
the customer’s environment. When assessing a customer’s environment, you must determine what the customer 
requirements and scope are for the design project, and you must analyze the data provided to you to build a scalable 
network that will last well into the future. We discuss these steps in detail throughout this content.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–4 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
The Request for Proposal
The RFP is the process the customer typically used to solicit potential vendors for network design proposals. No two RFPs are 
identical, as each customer has unique requirements. The RFP can be very short and concise, or it can contain several 
pages filled with concise requests. As the architect, your job is to ensure you have thoroughly read and understood the RFP. 
Although they can differ in appearance and requirements, every RFP normally includes the following:
• A list of design requirements including business goals, scope, and information on the existing network 
environment. 
• The types of solutions that the design must include, such as wireless, high availability (HA), security, and so 
forth. The wording for these requirements can be generalized or very specific.
• Warranty requirements for the products you offer as well as any legal terms attached to the solution.
Continued on the next page.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–5I
Juniper Networks Design Fundamentals
The Customer Considers Multiple Vendors
In many instances, you are not the only vendor the customer is considering. When the customer first recognizes the need to 
create or update a network, they will usually create the RFP and send it out to multiple vendors, including you. There might 
be a specific format or deadline that you must follow in your response. Be sure to include as much relevant information as 
you can in your response. The customer will use RFP responses to quickly eliminate vendors who do not meet their 
requirements. In many ways, responding to an RFP is like applying for a job. If you apply for a job, but do not represent 
yourself well during the application process, you most likely will not pass the initial screening. When responding to the RFP, 
be timely, thorough, and honest. Respond to the RFP using the customer’s requested format. to avoid eliminating yourself 
from consideration.
In some cases, you might receive a Request for Information, (RFI) rather than an RFP. What is the difference? An RFI can be 
quite broad in scope and typically only covers the technical aspects of the design request. A customer will often send an RFI 
to you to determine if you are capable of providing the services they are looking for. The customer will send you an RFP if they 
want information on pricing and contract information included in the design proposal. Responding to an RFI is a great way to 
throw your name into consideration for a project, while the RFP takes more effort on the part of both parties because you 
would also include details on pricing, warranty, timetables and legal expectations. For the simplicity in this course, we 
identify both the RFI and RFP as the same thing and use the term RFP to describe them.
The next several slides examine various elements of the RFP.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–6 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
RFP Key Elements: Part 1
The RFP can include a variety of elements that describe the company and the business they are in. The business summary 
will likely include a description of the network design project and objectives describing the business and technical goals of 
the new design. The general overview will likely include planning for future growth and an explanation for why the new design 
is required. If any of these key elements are missing from the project description, you should follow up and get more 
information so you can properly respond to the RFP.
Example
The slide illustrates a simple example of what a project description might look like in an RFP. Given the information on the 
slide, what are some of the customer’s primary challenges and goals? This short description gives us at minimum a 
high-level idea of what the customer is looking for. Remember that the RFP typically lists several pages of requested 
information. The project summary is just a small part of the RFP.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–7I
Juniper Networks Design Fundamentals
RFP Key Elements: Part 2
The RFP will typically include several environmental elements, including Layer 1 infrastructure details such as power supply, 
voltage, Power over Ethernet (PoE) requirements, and so forth. A campus-based RFP might include several details about the 
facilities, number of users and types of connections that users will make to connect to the network. In this section of the 
RFP, you begin to understand the scope of the project. For example, the network might be part of a larger Wide Area Network 
(WAN) solution. The environmental requirements might call for connections to a separate data center, or simply require a 
dedicated server room that’s located on site.
Example
The example on the slide describes a need for a centralized server room for data and voice connections. Note that, based on 
the description, the server room layout has not been finalized and might not be ready before your proposal is submitted. 
Sometimes you will not have all of the information you need when you respond to the RFP. Although the architectural design 
of the site is still a work in progress, you can still build a response based on the number of connections, throughput, and 
bandwidth requirements.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–8 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
RFP Key Elements: Part 3
Many of today’s networks are large in scale and complex in nature. Most customers will likely express the requirement that 
their network be easy to maintain and troubleshoot. The customer will likely require compatibility for future expansion and 
new technologies. You should always consider a modular design to support these requirements when responding to the RFP. 
In a modular design, each device has a clearly assigned function.The simplest example of modularity is assigning devices 
based on their function in a hierarchical model. A hierarchical approach allows you to easily troubleshoot and maintain the 
network. You can easily replicate additions to the network by replicating what already exists. We discuss modular design in 
detail later in the course.
Example
In the example on the slide, the customer is not directly asking for a modular design; however, the customer is expecting that 
the business will triple in size over the next 5 years with expansion into several branch offices. The customer will need to 
easily expand the network to accommodate the growth of the business. A modular design will benefit the customer because, 
as more job roles are added and office space is opened, the network can be expanded based on the functions of the existing 
network. There is no need to create something new or rewrite something that already exists.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–9I
Juniper Networks Design Fundamentals
RFP Key Elements: Part 4
Connectivity and throughput requirements vary from site to site. Customers dealing with older infrastructure might prefer 
wireless connections because the cost of running wired connections to each workstation could be too great. Most customers 
will tell you that speed is critical to business success. After all, who wants to work on a slow network? Some information on 
required network speeds might be defined in the RFP, but you might need to provide the customer with a traffic analysis to 
fully understand what equipment is required to support the customer’s goals. This information is typically collected as you 
assess the customer’s existing network environment. We discuss scoping the network in detail later in this content.
Example
The example on the slide provides only a brief explanation of what the customer requires. Providing gigabit wire speeds to 
the desktop and 300 Mbps speeds to wireless devices seems simple enough, but how complex will the network be to provide 
those speeds to all users without performance degradation? Will there be enough bandwidth for all users on the network? 
Do these requirements include remote users working from home or offices with slower network speeds? The answers will 
depend on several factors, including the applications used, services offered, and available resources. As we discussed 
previously, understanding the answers to these questions will require additional research, traffic analysis, and even 
interviews with the customer’s employees. In addition, you should assemble your own team of subject matter experts to 
assist you in responding to the RFP.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–10 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
RFP Key Elements: Part 5
In addition to the obvious speed and throughput requirements most customers expect, you can also expect to see 
requirements for business continuity. What happens to the network if a key device stops responding? Will users continue to 
access the network without interruption? Are certain applications more critical than others and therefore require priority 
during peak times? You will certainly expect to see requirements for network efficiency, quality of service (QoS), and load 
balancing solutions in most RFPs you receive.
Example
The example on the slide is a simple request that high availability (HA) be included in the RFP response. Often, the initial RFP 
will have only high level requests for certain features in the design. Some RFPs will have more specific requests to 
accommodate specific protocols or services that already exist in the network. Your job will be to find out what exactly is 
required so you can respond accordingly without eliminating yourself from consideration.
The RFP might request support for proprietary services used by specific vendors that Juniper Networks does not support. 
Respond to these requests by offering standardized solutions using Juniper Networks devices that can also inter-operate 
with other vendors. Always offer solutions by focusing on what your solution can do rather than what it does not support.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–11I
Juniper Networks Design Fundamentals
Scoping the Design Project
The slide highlights the topic we discuss next.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–12 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
Responding to the RFP
As we discussed previously, every RFP is different. You are likely one of multiple vendors that the customer is considering for 
a design proposal. It is critical that you pay attention to what is defined in the RFP. Your initial response will be critical to keep 
yourself in consideration for getting the design contract. Of course, you are competing with other vendors, so you will want to 
respond in a way that highlights the benefits of choosing your proposal over other vendors. Respond to every applicable 
requirement in the RFP, and use the format specified by the customer. Remember, every customer uses different formats 
and terminology when describing their network, so be sure to use the terminology that the customer understands in your 
response.
An RFP response consists of several elements, but should always include the following:
• Executive Summary—A brief overview of your design proposal that should highlight the benefits of using your 
design.
• Network Topology—High level logical design as well as low level physical design of the proposed network.
• Design Details—Information on the devices, protocols, and technologies included in the proposed design.
• Implementation Plan—A description for how the design will be implemented, as well as timetables for when the 
plan will be ready for operation.
• Training—An education plan for employees as the new network becomes available for use.
• Support—A plan for supporting and servicing the design, once operational.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–13I
Juniper Networks Design Fundamentals
Defining Key Stakeholders
As you begin to work closely with the customer on a network design plan, you’ll want to determine who the key stakeholders 
are in the proposed design. Certainly your design is expected to include several benefits. The benefits of a new network also 
include some level of risk. Remember that networks provide a service for people, and no two people are the same! You must 
get to know the key people, or stakeholders, you are working with so you can build a network that they will embrace. The 
slide lists three tips to help you work with the stakeholders for your customer:
• Understand the corporate structure: Typically you will work closely with a representative or group of 
representatives from the company who are seeking your help; however, those representatives might not have 
final say in the design plan. Who has the final say in accepting or rejecting your design? You must understand 
who the decision makers are, and understand what will make the difference so they accept your design.
• Ask the right people the right questions: Having a clear idea of what the customer wants is important when 
submitting your proposal to the customer. If the customer has spent a lot of time discussing their needs with 
you and you submit a proposal that does not satisfy those needs, your proposal will not be accepted. Be 
proactive in asking questions concerning the existing network what technical requirements are needed to 
create the new network.
• Understand corporate politics: It would be nice if everybody saw things the same way, but when you are dealing 
with people, you will undoubtedlydeal with individuals within the company who do not like your design. 
Corporate politics can play a big part in decision making. Some people might prefer one vendor over Juniper 
Networks despite the obvious benefits that your design provides. Key decision makers might be divided into 
“camps” where no proposal can be agreed upon. Employees might resist your network design if it requires more 
head count or eliminates positions within the company. Be sensitive to the culture within the company you are 
working with as you develop your design proposal. NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–14 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
Gathering Data: Part 1
As you begin to work with the customer more closely, you will need to gather the data necessary to accurately determine 
what you will need for your network design. If networks are all about providing a service for people, why not interact with the 
people you are building the network for? Use questionnaires, surveys, and interviews to interact with your customer’s 
workforce. Find out what is most important to them. How do they use the network to accomplish their daily tasks? You might 
be able to access job aids that describe in detail the daily routines of the customer’s user base. If you can get copies of job 
aids, take them!
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–15I
Juniper Networks Design Fundamentals
Gathering Data: Part 2
When considering a new design for your customer, you take into consideration the customer’s goals, requirements, and 
employee feedback. Consider the role of a police detective who must separate the facts from opinions and false information 
when determining who committed the crime. You must also collect the facts about the customer’s existing environment and 
vision of the future when designing the new network. You must determine the limitations to the current network and what is 
required for the new network to be successful. If the customer can provide utilization and performance reports, along with 
historical trends, you can use that data to help formulate your proposal. If the customer relationship is amicable, you might 
offer performing a traffic flow analysis as part of the proposal. The traffic flow analysis assists you in determining many 
variables—some of which are listed on the slide—that will assist you in understanding what is needed when developing the 
new design. 
If the customer already owns Juniper products, you might be able to use those products to assist in a network analysis. Junos 
devices have several troubleshooting tools that can assist you in traffic flow analysis, such as traceoptions (troubleshooting 
logs), packet capturing, and flow capturing, (J-flows). The information collected from Junos devices can then be sent to 
servers that specialize in Security Information and Event Management, (SIEM). Juniper Networks Secure Analytics (JSA) is a 
great option for SIEM because it can collect and parse out the events and flows from network devices and identify threats 
and assets from the information it collects. JSA supports Junos devices, but also a wide variety of other 3rd party devices 
that likely exist in the customer’s network.
Junos Space Network Director also has several monitoring tools for Junos devices, including visibility and network status, as 
well as traffic statistics, active alarms, and the ability to spot trends that develop over time.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–16 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
Identifying Applications
You should now have a good idea of what applications are used based on the data from traffic analysis and feedback from 
the customer. Keep track of the applications that the customer uses on a spreadsheet or table such as the example on the 
slide. Creating a list of applications not only helps you understand what applications the customer is using and planning to 
use, but helps you prioritize traffic based on criticality. This is important, particularly, for required applications that demand 
large amounts of bandwidth. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–17I
Juniper Networks Design Fundamentals
Understanding Scope
As you assess the company infrastructure, you must understand the entire scope of the design project. A network design 
might seem small initially, with only a few hundred users, but that network has the potential to grow significantly over time. 
Your design must be able to accommodate any foreseeable change in capacity. Designing with modularity in mind will help 
you accommodate any network the customer has asked you to design. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–18 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
Analyzing the Data
The slide highlights the topic we discuss next.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–19I
Juniper Networks Design Fundamentals
Validating the Data
The exhibit on the slide is a simple example of the validation process when developing a network design for your customer. 
You begin by collecting the data from your customer. There likely will be a lot of data to examine and decipher, so the 
question must be asked, Do I understand what is needed? If the answer is no, then you will need to refer back to the 
customer and ask more questions and collect more data. 
This cycle continues until you feel like you do understand what the customer is asking for. You should then determine, Do I 
know how I can help? If the answer is yes, assemble your team of subject matter experts and begin planning your proposal. 
If you don’t know how you can help, you will need to consult with the subject matter experts that will help you answer 
questions and help you with a design. In every case where you do not feel comfortable with a certain concept, you must not 
only consult with individuals who are experts, but truly become the expert yourself. There are not many issues that only come 
up once. Become an expert and you will put yourself ahead of the crowd on future projects.
In many cases, after you validate the data and consult with your team, new questions might arise where you must refer back 
to the customer. At this point, you should ask yourself, Do I need more information? If the answer is yes, then you will again 
find yourself cycling through customer data to fill in the blanks for your RFP response. 
Once you have all the information you need and are your proposal is ready, you can respond to the RFP. We focus on the 
important details of this process on the next few slides.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–20 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
Designing Greenfield Projects
Most design projects involve some sort of upgrade to the existing environment; however, sometimes you’ll get to design a 
network from the ground up. These types of design projects are sometimes referred to as greenfield projects. Greenfield 
projects typically have very little existing equipment or restraints to consider in the design plan. Ideally, a fully optimized 
next-generation network would be designed in greenfield conditions. With that in mind, even greenfield designs will have 
restraints to consider. For example, you might be asked to maximize a network’s potential while dealing with infrastructural 
limitations, such as inadequate server room space or poor rack cooling conditions. Perhaps wiring an older office space for 
wired desktop connections would be cost prohibitive. Be aware of these limitations when formulatingyour responses.
Upgrading Existing Network
Upgrading a customer’s network is the more common approach in network design. There are many factors that contribute to 
a customer’s decision to upgrade rather than complete replace a network. Those factors include timing, training, and cost. 
Certainly, if a customer’s network was designed with modularity in mind the first time, you should be able to add the new 
requests to the existing network without much disruption. In some cases, the customer is happy with the network design but 
the equipment needs to be replaced. Perhaps you must cope with a design that is completely obsolete and must be 
replaced. 
It will be your job to determine the best approach in your response to the customer when bidding for the job, taking into 
consideration all of the data analysis factors that we have described in this content.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–21I
Juniper Networks Design Fundamentals
Creating Equipment Lists
As you assemble the proposal for your customer, you will need to include an equipment list, sometimes referred to as the Bill 
of Materials (BOM) that includes equipment and sub-components needed to create the network design. Depending on the 
complexity of the design, the BOM might be a simple list of equipment needed to complete the proposal, while a more 
complex BOM might be modular—where equipment, services, and cost are broken down and associated with design 
functionality. More complex BOMs can be multi-level—or nested—list s whose parent devices are listed with a set of child 
devices nested in two or more levels of detail. Modular and multi-level BOMs work well when you are sharing your design 
requires a set of requirements that are used for multiple customers or partners.
Understanding the Budget when Setting Price
Hopefully, the customer has clearly specified the budget that you are to work with. It’s important that you understand the 
budget you are working with as you develop your proposal. We all would love to own a fast sports car, but more often than 
not, we have to opt for the car we can afford and save the sports car for a time when we have the money. Some people will 
never be able to afford a sports car, and frankly, they’ll be just fine owning a nice, less expensive sedan. Your job is to come 
up with a design that matches the customer’s needs and budget. Consider that the budget might change over time, so keep 
constant communication with the customer as you work on their design. Consider other costs associated with your design, 
such as additional staffing, as well as testing and training on the new equipment. Do not overlook the possibility that your 
design will either eliminate jobs or require additional headcount. Communicate the possibility of these factors to the 
customer so they can provide further instruction if these additional factors can be figured into the proposal.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–22 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
We Discussed:
• Analyzing and interpreting common RFP requirements; and
• Scoping a network design by gathering data and working with key stakeholders.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–23I
Juniper Networks Design Fundamentals
Review Questions
1.
2.
3.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–24 • Understanding Customer Requirements www.juniper.netI
Juniper Networks Design Fundamentals
Lab: Understanding Customer Requirements
The slide provides the objectives for this lab.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Understanding Customer Requirements • Chapter 3–25I
Juniper Networks Design Fundamentals
Answers to Review Questions
1.
When responding to the RFP, you should always follow the customer’s requested format to demonstrate that you understand what the 
customer is asking and keep yourself in contention when competing with other vendors.
2.
Questionnaires, surveys, interviews, job aids, a list of applications, and a traffic flow analysis are all examples of data you should collect 
from the customer when determining the scope of the design.
3.
Budget, the elimination of jobs, corporate politics and existing infrastructure are all factors that can accept the customer’s acceptance of 
your design plan.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 3–26 • Understanding Customer Requirements www.juniper.netI
HA
RE
Juniper Networks Design Fundamentals
Chapter 4: Organizing the Data
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
S
IN
T
Juniper Networks Design Fundamentals
We Will Discuss:
• Ways of processing customer data and requests;
• Boundaries and scope for the design proposal; and
• Considerations when creating a design proposal.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 4–2 • Organizing the Data www.juniper.netI
Juniper Networks Design Fundamentals
Processing the Data and Requests
The slide highlights the topics we will discuss. We discuss the highlighted topic first.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Organizing the Data • Chapter 4–3I
Juniper Networks Design Fundamentals
Plan Methodology: Data Analysis
The slide is a review of the idealogical flow behind planning a network design for a customer. We focus on data analysis in 
this content.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 4–4 • Organizing the Data www.juniper.netI
Juniper Networks Design Fundamentals
Plan: Organizing the Data
The slide depicts the typical flow that you might follow when planning the initial design. Assuming you have collected all of 
the data you require from the customer, you will have a lot of information to organize! The data you have collected can be 
sorted into three main categories—customer data, customer requirements, and project boundaries. We discussed the types 
of data you collect from the customer in the last chapter. We discuss customer requirements and project boundaries in the 
next several slides. 
Once you have successfully sorted, organized, and processed the data, you should have a good idea as to what the design 
should look like. 
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Organizing the Data • Chapter 4–5I
Juniper Networks Design Fundamentals
Data Analysis
You can typically take the customer data, as well as customer requirements, and organize them into the six main categories 
shown on the slide. The customer requirements will typically be based on a few key focus areas, such as functional areas 
and user groups. We discuss some of the more common customer requirements on the next several slides.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 4–6 • Organizing the Data www.juniper.netI
Juniper Networks Design Fundamentals
Sample Security Requirements
The slide lists some sample security requirements. Can you think of Juniper Networks solutions that could fulfill these 
requirements? List them in the space below.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
www.juniper.net Organizing the Data • Chapter 4–7I
Juniper Networks Design Fundamentals
Sample Availability Requirements
The slide lists some sample availability requirements. Can you think of Juniper Networks solutions that could fulfill these 
requirements? List them in the space below.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D
O 
NO
T 
SH
AR
E
Chapter 4–8 • Organizing the Data www.juniper.netI
Juniper Networks Design Fundamentals
Sample Scalability Requirements
he slide lists some sample scalability requirements. Can you think of Juniper Networks solutions that could fulfill these 
requirements? List them in the space below.
NT
ER
NA
L 
US
E 
ON
LY
 —
 D