Network Architect's Handbook E-Book

Alim H. Ali

• Herausgeber: Packt Publishing
• Kategorie: Fachliteratur
• Sprache: Englisch

Seitenzahl: 552

Veröffentlichungsjahr: 2024

Beschreibung

Becoming a network architect is challenging—it demands hands-on engineering skills, collaboration with internal teams and C-Suite stakeholders, as well as adeptly managing external entities like vendors and service providers. The author taps into his extensive background in IT and security to help you gain a detailed understanding of the network architect's role and guide you in evolving into an effective network architect within an organization, fostering seamless communication with leadership teams and other stakeholders.
Starting with a clear definition of the network architect’s role, this book lays out a roadmap and discusses the attributes and mindset for success. You’ll explore network architect design, physical infrastructure routing and switching, and network services such as DNS, MLAG, and service insertion. You’ll also gain insights into the necessary skills and typical daily challenges faced by network architects. And to thoroughly prepare you to advance in your career, this handbook covers certifications and associated training for maintaining relevance in an organization, along with common interview questions for a network architect's position.
By the end of this book, you’ll be armed with essential concepts, techniques, and newfound skills to pursue a career as a network architect.

Leseprobe

Network Architect’s Handbook

An expert-led journey to building a successful career as a network architect

Alim H. Ali (CCIE 2x: #36988, CISSP, GCP/AWS Professional Architect and Security)

Network Architect’s Handbook

Copyright © 2024 Packt Publishing

All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews.

Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing or its dealers and distributors, will be held liable for any damages caused or alleged to have been caused directly or indirectly by this book.

Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information.

Group Product Manager: Pavan Ramchandani

Publishing Product Manager: Prachi Sawant

Senior Editor: Sayali Pingale

Technical Editor: Arjun Varma

Copy Editor: Safis Editing

Project Manager: Neil Dmello

Proofreader: Safis Editing

Indexer: Subalakshmi Govindhan

Production Designer: Ponraj Dhandapani

Marketing Coordinator: Dhruvil Dudakiya

First published: February 2024

Production reference: 1120124

Published by Packt Publishing Ltd.

Grosvenor House

11 St Paul’s Square

Birmingham

B3 1RB, UK

ISBN 978-1-83763-783-6

www.packtpub.com

To my beloved daughter, Alisha,

As I pen these words, I reflect on the journey of writing my first book—this journey was far more challenging and rewarding than I ever anticipated. This achievement, my dear Alisha, would have remained an unfulfilled dream without your presence in my life.

Your light, my child, has been the guiding star in my darkest nights and the warm sunshine in my brightest days. It is your spirit that has given me the strength to move forward, and your unwavering belief in me that has driven me to pursue my dreams. All of which I do for you.

From the moment you entered this world, you have been my greatest source of inspiration. Your existence has pushed me to be better than I ever thought possible. My every effort, my every accomplishment, is a testament to my desire to show you that dreams can be achieved through hard work and determination.

I am beyond grateful and consider myself blessed to have you, Alisha, as my daughter. Your kindness, intelligence, and love enrich my life in ways words can scarcely capture.

This book is as much a part of you as it is of me. It stands as a symbol of our shared journey, of the endless possibilities that lie ahead, and of the enduring love that binds us together.

With all my heart - I love you, Alisha!

– Alim H. Ali

Foreword

Network Architect’s Handbook is a testament to the relentless pursuit of expertise, innovation, and vision in the world of networking. As someone who has had the privilege of knowing Alim both professionally and personally for over two decades, I can attest to the unwavering dedication and ability that he brings to the ever-evolving landscape of technology. At one time, Alim was a student of mine, and I’ve had the pleasure of seeing him consistently achieve new heights in his career. This book is not just a roadmap to becoming a network architect but a profound testament to Alim’s journey—a journey marked by passion, expertise, and an unyielding commitment to excellence.

Within these pages lies an abundance of knowledge gained from Alim’s extensive experience navigating the intricate world of network architecture. From the foundational principles of network protocols to the advanced strategies that define this field, you will find yourself guided by Alim’s expertise, which goes beyond technical mastery. Each chapter is a testament to his practical insights, hard-earned lessons, and the innovative spirit that has propelled him through countless challenges in the pursuit of becoming the network architect he is today.

Alim’s journey from apprentice to expert resonates profoundly throughout this book. It’s a narrative that not only imparts technical knowledge but also encapsulates the mindset, resilience, and passion required to excel in this dynamic domain. For those setting foot on this path or seeking to deepen their understanding, Network Architect’s Handbook stands as an invaluable companion—an ode to perseverance, innovation, and the relentless pursuit of excellence in the world of networking.

Steven Parker

CISSP, Chief Information Security Officer

TBC Corporation

In the constantly evolving and perhaps overly complicated world of enterprise technology, it’s truly a unique opportunity to encounter someone with both deep expertise and an undeniable passion for innovation. I was fortunate enough to experience this when I crossed paths with Alim H. Ali during our respective careers at Hewlett Packard Enterprise (HPE).

This book is a narrative of Alim’s own journey and his profound grasp of enterprise networking. It captures his technical expertise and, more importantly, his visionary approach to leveraging technology for business growth. You will discover a collection of knowledge and insights, all stemming from his real-life experiences. These insights are shared with the kind of clear and compelling voice that I’ve always admired in him.

Alim skillfully explains the evolving role of the network architect in today’s increasingly intricate and sophisticated IT landscape. Drawing from his substantial experience, he guides you through the expansive “network fabric” that has developed over the decades. The book probes into the network architect’s role across different organizational scales, detailing the vital tasks from the planning and designing to the maintenance of network infrastructures.

Furthermore, Alim highlights the essential roles, from entry level to senior level, offering a useful framework for understanding and traversing the route to becoming a network architect. The book goes beyond technical insights. It underscores the strategic operational significance of network architects who are key in shaping IT business units and, eventually, aiding in the success of contemporary enterprises.

In closing, I am confident that this book will serve as a valuable resource, illuminating the path for navigating through the complex landscape of enterprise technology. It is with great pleasure and immense pride that I introduce Alim and his remarkable work.

Russell Ware

CEO and founder, Cloud33and3

Former Solutions Architect Director, Hewlett Packard Enterprise

Contributors

About the author

Alim H. Ali (CCIE 2x #36988, CISSP #34527, CCSI #32568) has a career spanning over 28 years at the forefront of technological innovation. He is a distinguished figure in the IT industry. As a 2xCCIE and CISSP, Alim combines deep technical expertise with visionary leadership, and he currently serves as the CEO of Asancha Corp.

Alim’s academic journey laid the foundation for an illustrious career, starting with a BS in bioengineering from the New York Institute of Technology and an MS in management of technology from New York University. His pursuit of knowledge is ongoing, as he is currently working toward an MBA and a PhD in IT.

Throughout his career, Alim has been a dynamic force across various industry verticals, including oil and gas, global telecoms, financial services, finance, and healthcare. His tenure at Fortune 100 giants such as HP/HPE, VMware, Accenture, and Verizon has identified him as a thought leader, innovator, and visionary in the field.

As an industry technologist at heart, Alim is known for his groundbreaking work in IT networking, cloud and data infrastructure, edge computing, high-performance computing, application modernization, and security adaptation. His visionary approach and relentless pursuit of next-generation IT solutions have positioned him as a key influencer and strategic thinker in the field.

Furthermore, Alim aspires to share his insights and expertise on global platforms such as CNBC, Bloomberg, Fox News, and MSN as a sought-after analyst. His goal is to contribute to broader conversations about technology and business, providing valuable perspectives on emerging trends and innovations.

Above all, Alim is celebrated for his ability to demystify complex technical concepts into strategic business solutions, driving industry progress and shaping the future of technology.

About the reviewer

Ashish Kumar serves as a senior enterprise architect, specializing in AI/ML within the AWS Professional Services organization. His role involves providing support to organizations in conceptualizing and implementing generative AI initiatives, turning visions into reality. Before joining AWS, Ashish was part of the AI team at Change Healthcare, where he contributed to the development of ML models for medical imaging. His extensive experience in the healthcare industry includes several years in various leadership roles. Ashish holds a master’s in data science from the University of Illinois Urbana-Champaign. In his spare time, he likes to unravel the mysteries of the universe, watch sci-fi movies, and get cozy with a good book.

Table of Contents

Preface

Part 1 – Navigating the Architectural Blueprint of Networking

1

Understanding the Network Architect’s Role

What is a network architect?

Solutions architects

Storage architects

Database architects

Enterprise architects

Cloud architects

Technical architects

Chief architects

Network architects

The function of a network architect

Understanding network architecture

Client/server architecture

Peer-to-peer architecture

Hierarchical architecture

Hybrid network architecture

Spine-leaf architecture

Summary

Further reading

2

Network Architect in an Organization

Planning, designing, installing, upgrading, and maintaining network projects

Planning

Design

Installing

Upgrading

Maintenance

Making recommendations to improve the network infrastructure and reduce operational costs

Cost-benefit analysis

Researching new technologies and solutions

Developing a roadmap

Documenting the network process for future use

Summary

3

Roadmap to Becoming a Network Architect

Roles and responsibilities – entry level

Network support technician

Network technician

NOC technician

Roles and responsibilities – mid level

Network administrator

Network engineer

Network security engineer

Roles and responsibilities – senior level

The career path to becoming a network architect

Summary

Part 2 – Crafting the Architectural Mind: Attributes and Mindset of a Network Architect

4

Attributes of a Network Architect

The network architect’s role in the business

Network infrastructure design

Network security

Network management

Network procurement

Technical leadership

Business logistics – the structure

Business financials

Cross Functional Teams (CFTs)

Managing business relationships

Vendors and suppliers

Internal stakeholders

Partners and clients

Industry groups and associations

Regulatory agencies

Summary

5

The Mindset of the Network Architect – the Principles of Design

Principles of network architecting

Hierarchical

Additional design patterns

Scalability

Modularity

Resilience

Performant

Thinking like a CxO

What other industries are doing

Always thinking – innovating, exploring new trends

Summary

Part 3 – Constructing the Core: Building Blocks of a Network Architect

6

Foundations of Network Architecture – Part 1: Route/Switch

Overview of the OSI model

OSI model versus TCP/IP model

Physical infrastructure

Network cabling

Switches and switching concepts

Switching concepts

Switches

Key switching functions

Routers and routing concepts

Routing concepts

Router types

Supporting vendors

Fiber optics

Networking

Security

Virtualization

Server

Summary

Further reading

7

The Foundation of Network Architecture, Part Two – Network Services

Understanding load balancers

Types of load balancers

Network load balancer (NLB)

Global server load balancer (GSLB)

Load balancing algorithms

Which load balancer should you choose?

Exploring DNS

How DNS works

Considerations for DNS design

DHCP

How does DHCP work?

Benefits of DHCP

Key considerations for using DHCP

Network Address Translation (NAT)

How does NAT work?

Types of NAT

NAT considerations

What are ACLs?

Types of ACLs

Understanding firewall rules

What does this mean for a network architect?

Miscellaneous network services

Considerations for a network architect

Summary

Further reading

8

Foundations of Network Automation

Fundamental building blocks of network automation

Network programmability

Understanding the role of SDN

Core principles and components

Impact on organizations

Exploring NFV

Key components of NFV

Benefits of NFV

Scripting and automation languages

The power of automation

Scripting languages

Automation tools

Understanding IaC

What is IaC?

Benefits to a network architect

Summary

Further reading

9

Paradigm Shift to Cloud Computing

What is cloud computing?

Cloud computing models

The need for cloud computing

Benefits of the cloud

Cloud services

Compute services

Storage services

Database services

Networking services

Monitoring services

Security and compliance

Cloud designing and architecting

Designing in the cloud

Architecting in the cloud

Cloud architecture components

What does it mean for a network architect?

Preparing for the paradigm shift

Summary

Further reading

Part 4 – Mastering the Craft: Advancing Your Journey as a Network Architect

10

Preparing for Certifications and Cracking the Job Interview

Network architects’ certification path

Foundational certifications

Professional certifications

Expert certifications

Design expert certifications

Miscellaneous certifications and others

Continued education

Preparing for certifications

Create an environment only used for studying

Remove distractions

Schedule your studying time

Use earplugs, white/brown noise, or focus sounds

Cone of Knowledge

Use a timer

Take breaks

Training and study material

Supplements and rest

How to crack interview questions

Sample questions

Questions

Summary

11

The Skills to Become a Better Network Architect and Overcome Daily Challenges

Interpersonal skills – how to communicate effectively

Communication

Listening

Empathy

Adaptability

Engaging with your team or teams

Role of a network architect across teams

Conflict resolution

Technical disagreements

Project alignment

Procurement and relationship management

Techniques to resolve conflicts

Growing as a leader

How do you become a leader?

Summary

Further reading

12

Additional Information and Recommended Books

Recommended books

Cisco Press

Arista books

Other networking books

Automation and network programming

Methodologies

Virtualization

Security

Cloud computing

Other useful resources

Websites

Blogs

Periodicals

Communities and forums

Training

Summary

Index

Other Books You May Enjoy

Preface

In the expansive realm of integrated technology, a multitude of “architects” shape the digital landscapes of organizations. Among these pivotal roles, the network architect stands as a cornerstone, intricately weaving the fabric of an organization’s IT system. The essence of this role, as the title suggests, is deeply intertwined with the network – the vital backbone that supports and interconnects the various facets of an IT system within an organization.

A network architect is not just a technician but also a visionary, tasked with designing and implementing network architectures that not only cater to the immediate needs but also anticipate the future demands of various business units (BUs) within an organization or a client. This role transcends the mere functionality of networks; it is about creating a system that is resilient, reliable, agile, and flexible, yet simultaneously efficient, cost-effective, and secure.

As you embark on this book’s journey, you will delve into the multifaceted world of IT architects, gaining insights into their different roles and how they collaboratively contribute to the broader IT strategy. We will then zoom into the fundamental characteristics that define a network architect. You will explore the depth of their roles and responsibilities, understanding what it takes to excel in this dynamic and crucial position.

Through the chapters of this book, we will unravel the layers of knowledge and skills essential for a network architect. You will gain a comprehensive understanding of the technological, strategic, and interpersonal competencies required to thrive in this role. The book will guide you through the nuances of network design, the subtleties of balancing technical requirements with business objectives, and the art of envisioning a network that not only supports but also elevates an organization’s goals.

By the end of this book, you will have embarked on a complete journey through the landscape of network architecture. You will possess a thorough understanding of what it takes to build a career as a network architect, equipped with the knowledge and insights to navigate the challenges and seize the opportunities that come with this vital role in the ever-evolving world of IT.

Embrace this journey as we chart the course to becoming a network architect, a role that is not just about connecting devices and data but also about connecting aspirations, strategies, and ultimately, people.

Who this book is for

This book is meticulously crafted for network engineers and network technicians who stand at a pivotal point in their careers, aspiring to ascend to the role of a network architect. If you find yourself with 7 to 10 years of experience in the dynamic realm of IT and technology and are seeking a path to elevate your career, this book is your compass.

The journey to becoming a network architect is both challenging and rewarding, demanding a unique blend of skills, knowledge, and visionary thinking. This book is tailored for professionals who have honed their technical abilities and are now ready to delve into the strategic and design aspects of network architecture.

The expert-led narrative will guide you through the intricate landscape of design concepts, architectural requirements, and the nuanced skills that set a network architect apart. We focus on the pivotal elements that form the backbone of this role:

Design concepts: Understanding the principles of designing robust, scalable, and efficient network systemsArchitectural requirements: Grasping the intricacies of network infrastructure and how to align it with business goalsRelevant experience: Leveraging your years of experience in IT to make informed, strategic decisions in network design and implementationCertifications and advanced education: Identifying the certifications and educational paths that will enrich your expertise and recognition in the fieldExpansion to cloud best practices: Navigating the cloud-centric landscape, where cloud computing and network architecture intersect, creating new opportunities and challenges

However, it is essential to recognize that this book is only a starting point on your journey. It is not intended to be a deep dive into any one particular facet of IT, such as network infrastructure, compute, databases, cloud computing, programming, or similar areas. Instead, this book serves as a guide to aid in translating business and strategic initiatives into technical requirements and solutions, and vice versa. It aims to bridge the gap between the technical and strategic aspects of IT, providing a foundational understanding to help you navigate the complex landscape of network architecture.

Whether you are a seasoned network professional aiming to transition into a more strategic role or a technician ready to take a significant leap forward, this book is designed to be your roadmap. It will not only enhance your understanding of what it takes to be a successful network architect but will also equip you with the knowledge to make that transformation.

Embark on this journey with me as we unravel the essence of network architecture, preparing you to not just meet but exceed the expectations of this pivotal role in the modern IT landscape.

What this book covers

Chapter 1, Understanding the Network Architect’s Role, explains how the network architect has many facets, from understanding network concepts to communication up to, and including, CXO. Network architects are responsible for designing and managing data communication, networks for organizations and/or clients. They must also be forward thinkers to ensure these systems are in line with business outcomes and goals. The network architect is one of many under the IT architect umbrella.

Chapter 2, Network Architect in an Organization, focuses on the roles and responsibilities that come with being a network architect.

Chapter 3, Roadmap to Becoming a Network Architect, introduces you to the roadmap toward becoming a network architect, from being a technician to a senior network engineer. Each role possesses key skills required, as well as responsibilities to move toward a career as a network architect. We will also look at the challenges that are faced in becoming a network architect.

Chapter 4, Attributes of a Network Architect, describes some of the qualities a network architect should obtain and possess. Though network architects are one of many “architects” and professionals in an organization, overlapping skill sets can and do occur with respect to the business. This chapter will introduce those overlapping skill sets.

Chapter 5, The Mindset of the Network Architect – the Principles of Design, goes into the mindset a network architect should have in order to be successful. It starts with the principles of network architecting, reading IT blogs and whitepapers, and reading the WSJ to listen to a company’s earnings report. Attributes are one part, but bringing it all together is the mindset.

Chapter 6, Foundations of Network Architecture – Part 1: Route/Switch, begins with the foundational knowledge and skills necessary to advance into a network architect role and looks at the physical infrastructure (cabling, routers, and switches). Routing and switching are vital for any network to be sustainable. These are the building blocks upon which databases, compute and storage, and applications rely. Having a complete understanding of what is used to build a network is key to any network architect’s success. This chapter is not intended to go into a deep dive on any one topic.

Chapter 7, Foundations of Network Architecture – Part 2: Network Services, describes the network services used to build the extensive network infrastructure companies rely on to support their business endeavors. ACLs, firewall rules, load balancing, and more play a critical role in supporting these endeavors.

Chapter 8, Foundations of Network Automation, discusses how, in the evolving landscape of network architecture, the shift toward automation is not just a trend but a fundamental transformation. Network automation stands at the forefront of this change, offering unprecedented efficiency, agility, and reliability. This chapter delves into the essential building blocks of network automation, laying a solid foundation for those seeking to harness its full potential.

Chapter 9, Paradigm Shift to Cloud Computing, introduces you to a paradigm shift to cloud and cloud technologies that can further aid a network architect’s growth to next-generation IT infrastructure and services. You will learn about the different “as a Service” models, the key cloud providers, and their services, as well as understand private cloud, hybrid cloud, and multi-cloud.

Chapter 10, Preparing for Certifications and Cracking the Job Interview, describes IT certifications that a person who is looking to move into a network architect’s role/position should obtain and how to prepare for those interview questions. There is no silver bullet on this topic. It takes hard work, commitment, and practice, practice, practice.

Chapter 11, The Skills to Become a Better Network Architect and Overcome Daily Challenges, covers how, in the journey to becoming a proficient network architect, technical skills are just one part of the equation. Equally vital are the interpersonal skills that enable you to navigate the complexities of a collaborative work environment. This chapter delves into the essential interpersonal competencies that will not only enhance your role as a network architect but also help you overcome daily challenges effectively.

Chapter 12, Additional Information and Recommended Books, shows how, while this book provides a comprehensive guide to becoming a network architect, the journey of learning and professional development is an ongoing one. To aid you in this continuous pursuit, we have compiled a selection of recommended books and other resources. These materials have been carefully chosen to complement the topics covered in this book and to provide deeper insights into specific areas of network architecture and related fields.

To get the most out of this book

As you embark on the enriching journey outlined in this book to become a network architect, it’s important to approach it with the right mindset and background. This book is crafted for network professionals who bring at least five years of experience in IT, particularly in networking. It’s tailored to readers who already understand networking concepts and technologies and are familiar with the fundamentals of networking solutions as they apply to IT infrastructure. Here are key strategies to help you get the most out of this book, provided that it aligns with your existing knowledge and experience:

Prerequisites for starting: Before delving into the chapters, recognize that this book is intended for those already midway through their IT career journey. It is not designed for individuals just beginning in IT. As a reader, you should have a robust understanding of network protocols, topologies, and a general grasp of IT systems.Set your learning objectives: Clearly define what you wish to achieve with this book. Whether it’s deepening your knowledge of advanced network architecture, refining specific technical skills, or developing leadership qualities within a network team, having specific goals will focus and enhance your learning process.Actively engage with the material: While reading, actively engage with the content. This could involve applying theories to your current work scenarios, participating in discussions with peers, or experimenting with concepts in a lab setting. Active engagement not only reinforces learning but also enhances understanding.Practical application: Try to implement the strategies and techniques discussed in your current role or simulated environments. Applying these concepts in real-world scenarios will solidify your understanding and provide valuable insights into practical challenges and their solutions.Explore additional resources: Utilize the supplementary resources recommended throughout the book. These resources are selected to complement the main content and offer a deeper exploration into specific areas of network architecture.Continuous review and reflection: Regularly reflect on and review the material you’ve covered. This not only ensures a comprehensive understanding of the content but also helps in connecting various concepts together.Maintain a learning mindset: The field of network architecture is dynamic and ever-evolving. Stay open and curious about new technologies, methodologies, and ideas that go beyond this book. Continuous learning is key in the IT field.

By following these steps and keeping in mind the intended audience and prerequisite knowledge, you will be well-equipped to not only grasp the concepts in this book but also to apply them effectively in your career. This book is a step in your ongoing journey of professional development in the field of network architecture.

Conventions used

There are a number of text conventions used throughout this book.

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “Select System info from the Administration panel.”

Tips or important notes

Appear like this.

Get in touch

Feedback from our readers is always welcome.

General feedback: If you have questions about any aspect of this book, email us at [email protected] and mention the book title in the subject of your message.

Errata: Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you have found a mistake in this book, we would be grateful if you would report this to us. Please visit www.packtpub.com/support/errata and fill in the form.

Piracy: If you come across any illegal copies of our works in any form on the internet, we would be grateful if you would provide us with the location address or website name. Please contact us at [email protected] with a link to the material.

If you are interested in becoming an author: If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, please visit authors.packtpub.com.

Share Your Thoughts

Once you’ve read Network Architect’s Handbook, we’d love to hear your thoughts! Please click here to go straight to the Amazon review page for this book and share your feedback.

Your review is important to us and the tech community and will help us make sure we’re delivering excellent quality content.

Download a free PDF copy of this book

Thanks for purchasing this book!

Do you like to read on the go but are unable to carry your print books everywhere?

Is your eBook purchase not compatible with the device of your choice?

Don’t worry, now with every Packt book you get a DRM-free PDF version of that book at no cost.

Read anywhere, any place, on any device. Search, copy, and paste code from your favorite technical books directly into your application.

The perks don’t stop there, you can get exclusive access to discounts, newsletters, and great free content in your inbox daily

Follow these simple steps to get the benefits:

Scan the QR code or visit the link below

https://packt.link/free-ebook/9781837637836

Submit your proof of purchaseThat’s it! We’ll send your free PDF and other benefits to your email directly

Part 1 – Navigating the Architectural Blueprint of Networking

In the ever-evolving world of technology, the role of a network architect has become increasingly pivotal. As we delve into the intricate world of network design and management, it is essential to understand the multifaceted nature of a network architect’s role, its place within an organization, and the path you must undertake to embody this key position. This section serves as the cornerstone to understanding the full scope of responsibilities, skills, and pathways associated with becoming a successful network architect.

This section has the following chapters:

Chapter 1, Understanding the Network Architect’s RoleChapter 2, Network Architect in an OrganizationChapter 3, Roadmap to Becoming a Network Architect

1

Understanding the Network Architect’s Role

Today, the network infrastructure (or fabric as I like to call it) is vast compared to how it was just 23 years ago, and even more sophisticated than when networks were around in the early 1970s. The infrastructure has evolved, and so has the people required to take care of and maintain them. But even in doing so, the role and responsibility have also evolved to be more. Before, the responsibility could have seen one or two people doing everything, such as racking and stacking, cabling, router configurations (as there were no switches at the time), installing hubs, and storage consolidation. Now, there are many roles in an organization that specialize in these varied tasks.

So much emphasis is put on the various roles within an organization when it comes to the IT business unit versus the IT department. Let’s not confuse the two – the IT department is your desktop/laptop support team who can grant you access to various services, while your IT business unit is responsible for making sure that your various lines of business are functional and sustainable to generate revenue for your organization. The latter encompasses the network architect.

In this chapter, we’re going to cover the following main topics:

What is a network architect?The function of a network architectUnderstanding network architecture

Let’s get started!

What is a network architect?

The network architect is vital to an organization’s sustainability within their industry’s vertical. A network architect is one of many architects that an organization has.

Here’s my twist on the definition of the network architect:

“The expertise and skills necessary to design an end-to-end system to meet the criteria set forth, by encompassing best practices, principles, capabilities, and components a well defined network architecture should have, to meet and exceed the expectation of key stakeholders while taking account concerns, constraints, and cost.”

Before diving into what a network architect does in an organization, a brief articulation of other architects that you’ll find in an organization will help to discern the difference from that of a network architect. Each has unique technical skills to address business needs, goals, and complexity. Moreover, there will be some overlap in tasks, deliverables to an organization, responsibilities, and maybe even KPIs.

KPIs

Key Performance Indicators (KPIs) are used to evaluate the success of an organization/team or a particular activity they are engaged in.

Solutions architects

Solution architects evaluate the requirements from the line of business (LoB) and determine what solution(s), whether it be products or services, can be used to meet or fulfill those requirements.

They design, describe, and manage the solution. This includes the networking (fabric) aspects, the storage aspect, database systems, security, and the overall scheme that will be deployed. In some ways, the solutions architect (SA) bridges a business problem and the technology solution. Additionally, the SA outlines each of the desideratum and the phases to make that solution work, after which they must confer with the other architects in the organization to validate the design feasibility.

To some degree, SAs create the overall technical vision for a specific solution to a (specific) business problem. I say to some degree because an organization’s overall IT/technical vision comes from the Chief Technical Officer (CTO).

Storage architects

A storage architect builds central database systems; one such system is a Configuration Management Database (CMDB), which holds the most crucial business information for an organization. Some crucial information includes (but is not limited to) finance, compliance, accounting, and human resources.

They typically design based on the SA’s findings, install new data storage systems using different software and various hardware, liaise with IT experts, and identify storage requirements to meet the needs of business units.

Examples of storage architects’ designs include the following:

FC zoningSAN and vSANNAS, NFS, and SMB shares

Some routine operations can include analyzing data, potential issues, frequency of updates, maintenance, and hardware/software Service Level Agreements (SLAs). Storage architects also need to communicate critical information to clients (internal or external) or an organization’s management team.

The role of a storage architect can vary, depending on the organization itself and what they’re looking for in the architect, but the storage architect’s main task is to design a stable, reliable, and resilient storage architecture.

Database architects

A database architect’s (DBA’s) function is to understand an organization’s main needs for data and its current data infrastructure. DBAs in some respects work closely with storage architects.

After taking the needs of an organization and conversing with the SA (and other stakeholders), the DBA analyzes the organization’s priorities and goals, assesses whether the current data infrastructure is design-feasible, and then determines where changes should and must be made.

They must design the database’s infrastructure to ensure that it’s scalable, secure, reliable, and, like other designs, cost-effective.

Depending on a country’s boundaries and compliances, DBAs must also ensure that a database meets any regulations and standards, especially when dealing with sensitive data.

Enterprise architects

An enterprise architect (EA) is somewhat similar to an SA. While the SA is charged with defining the correct services/infrastructure to meet the BU’s needs, the EA is responsible for the upkeep and maintenance of those services/infrastructure.

They’re also responsible for improving and upgrading enterprise services (e.g., CRMs, HRMs, and PoS systems), software, and hardware.

Like the SA, EAs must have a wide view and scope (vision) of what’s happening within an organization, as well as being abreast of new trends and technologies, and any software services or hardware that might improve business processes.

Cloud architects

As you may have guessed, a cloud architect is involved with cloud computing. Their function is to oversee an organization’s cloud adoption strategy. Cloud architects oversee application architecture and deployment in cloud environments, including the public cloud, private cloud, and hybrid cloud. Additionally, they act as consultants to their organization and also need to stay abreast of the latest trends and issues (https://www.techtarget.com/searchcloudcomputing/definition/cloud-architect).

Cloud architects must understand application owners’ and application developers’ needs and requirements. Then, they must survey how to closely replicate it, if possible, in a cloud-centric environment based on what’s already allocated and consumed on-premises. The premises can be an organization’s leased space, owned property, or IT setup, solely owned by that organization, which would then be migrated.

In all cases, the cloud architect has to determine whether the application (workload) fits into one of Gartner’s five Rs of migrating applications into the cloud (Migrating Applications to the Cloud: Rehost, Refactor, Revise, Rebuild, or Replace?, available athttps://www.gartner.com/en/documents/1485116)

The following diagram is a cloud migration strategy currently used by AWS, based on Gartner’s original five Rs:

Figure 1.1 – AWS’s version of Gartner’s five Rs of cloud migration strategies (source: https://aws.amazon.com/blogs/enterprise-strategy/new-possibilities-seven-strategies-to-accelerate-your-application-migration-to-aws/)

Technical architects

While other architects may be broad(er) in scope, technical architects (TAs) are more specific. They take the most hands-on approach during the execution of IT projects and focus mainly on a single implementation for a specific domain that they’re, technically, inclined for. An example would be a TA who is extremely familiar with SAP, MongoDB, Python, or even Cisco.

Because of this, TAs produce best practice strategies utilized by an organization, which, in most cases, are used by other IT architects during their development and strategy sessions for their own solutions.

Out of all the IT architects, TAs are the closest to an organization’s end user. Thus, they have to ensure that the technology is not only delivered on time but is fully functional for the end user (https://rb.gy/uw31fb).

Chief architects

Depending on the organization, the chief architect (CA) may oversee and coordinate the efforts of other technology-specific architects, including the chief security architect, the chief data architect, the chief mobile architect, and the chief cloud architect.

A CA is primarily a leader and communicator. They need to understand and influence the business strategy and lead the development of an architecture strategy that supports and enables that strategy (https://www.redhat.com/architect/what-is-chief-architect). A CA can also be referred to as an EA, as defined previously.

In addition, there are other architect roles, such as the following:

ApplicationMigrationSecurityAutomationSite Reliability Engineer (SRE)Software

The role of every architect in IT is directly related to the added complexities of information technology, and the need for a strategic top-down approach to the management of shared data and processes.

There can be varying degrees of overlap with some or all of these IT architects in an organization. Many are structured differently when it comes to who owns what, who’s in charge, or who has the last say and signs things off.

Relatively speaking from my experience, this is what I came across from a hierarchy perspective:

Figure 1.2 – The IT architect hierarchy in an organization

As I said before, there are not only overlaps in job function and responsibility but also overlaps when it comes to the roles within an organization, including business-centric, operations-centric, or even vendor and application-centric roles.

In general, the role of an IT architect is to ensure that an organization’s IT systems are aligned with its business objectives and able to support its operations effectively.

Network architects

A network architect is mainly responsible for designing, managing, and implementing an organization’s data communication networks, including the computer networks that support their IT systems, storage networks, and the internet edge. This means the network architect is responsible for the following:

Designing local area networks (LANs), wide area networks (WANs), and intranets for organizationsDesigning the data and storage area networks (SANs)Both the hardware and software components of a networkThe policies and procedures that govern its use

While other IT architects may have a more general focus and be responsible for designing and implementing the overall IT infrastructure of an organization, a network architect must be fully embedded and have the required knowledge of many different network technologies (platforms) related to network routing and switching, networking protocols, network hardware and software, and the latest trends.

The network architect does overlap with the other architects mentioned. They also need to fully understand a business’s operations and its operating model, which is discussed in Chapter 4. It’s prudent to say network architects do not operate in siloes and should be a part of any meeting that requires a change, addition/removal, request, or ideation for an organization’s network (fabric) infrastructure.

Now that we have a general overview of the various architects in an IT organization, let’s talk more in depth about the topic this book is dedicated to, the network architect.

The function of a network architect

The function of a network architect is characterized by their responsibilities, which can vary, depending on the specific organization and the size and complexity of their network. However, some common functions/responsibilities of a network architect might include the following:

Designing and planning the overall architecture of an organization’s network, including its physical and logical layoutSelecting and configuring the hardware and software components that make up the network, such as switches, routers, protocols, and firewall appliancesImplementing and maintaining network security measures to protect against external threats and unauthorized accessEnsuring the network is scalable, agile, flexible, and able to handle growing demands from business unitsMonitoring the performance of the network and identifying and troubleshooting any issues that ariseDeveloping and implementing policies and procedures for the use of the networkCollaborating with other IT professionals, such as system administrators and application developers, to support the overall IT infrastructure of the organization, and other architects to express opinions about design concerns, constraints, and successArticulating business needs to the leadershipManaging vendor relationships and working with external contractors or service providers as neededStaying up to date with the latest technologies and trends in networking and evaluating their potential impact on the organization’s network

A network architect may also be responsible for designing and implementing specific subsystems within a network, such as the data center, the campus network, the metro network, and other private network systems.

In most cases, these responsibilities are completed standalone, meaning without validation or approval from other IT architects. Generally speaking, activities, concerns, or anything similar are brought up during a stand-up or regularly scheduled IT meeting.

In summary, a network architect is responsible for the overall design, implementation, and maintenance of an organization’s computer networks. They play a key role in ensuring that a network is reliable, secure, and able to support the needs of an organization.

Understanding network architecture

Network architecture refers to the overall design of a computer network, along with other auxiliary networks. It includes the hardware, software, and protocols that make up the network, as well as the physical and logical layout of the network and the relationships between the various components.

Network architecture should be designed to support the needs and goals of an organization, taking into account factors such as the size of the network, the types of devices and applications that will be traversed across, the number of end users (consumers), the level of security required, and the availability and performance requirements.

The architecture must be able to support the current organizational needs (from the various lines of businesses, stakeholders, leadership, and end users), be flexible for future growth, meet multiple degrees of SLx (such as SLAs and SLOs), and be agile to support shifts in the market, all the while maintaining a cost balance between CapEx and OpEx.

There are many different approaches to designing network architecture, and the most appropriate one will depend on the specific needs and constraints of an organization. Some common types of network architectures include the following:

Client-server architecture, in which one or more central servers provide services to multiple clientsPeer-to-peer architecture, in which all devices on a network are able to communicate directly with each otherHierarchical architecture, in which a network is divided into multiple layers, each with a specific functionHybrid architecture, in which multiple different architectures are combined in order to meet the needs of an organizationSpine-leaf architecture, to take advantage of high-speed throughput for east–west traffic and a higher level of redundancy

Let’s take a closer look at these architectures.

Client/server architecture

The client/server architecture is a computing model in which the server hosts, delivers, and manages most of the resources and services requested by the client.

Figure 1.3 – An example of a client/server architecture

It’s also known as a networking computing model or client/server network, as all requests and services are delivered over a network. Client/server architecture is a common way to design and implement computer systems. It is used in a wide variety of applications, including web applications, email systems, and database management systems.

These systems can be HR, CMDB, network (fabric) monitoring and logging, or storage systems.

Multiple clients’ requests are made to and from a central server. The server is responsible for handling requests, processing data, and providing a client with the requested information. The client, on the other hand, initiates the request and displays the received data to the user. This architecture is commonly used in distributed computing, where a centralized server manages and distributes data to multiple clients over a network.

The communication between the client and the server typically occurs over a network, such as the internet, and follows a request-response model. Clients make requests to the server for specific services or data, and the server processes those requests and returns the requested information to the clients.

Typically, in a client/server architecture, the client computer is responsible for the user interface. The client computer displays information to the user and accepts input from the user. The server computer is responsible for the data. The server computer stores data and processes data requests from the client computer.

A common example of a client-server architecture, used every day, is a web application. In this case, the client is a web browser (such as Chrome or Firefox) that runs on a user’s computer, and the server is a computer or group of computers that host the web application and store the files and databases that the application uses. The client sends requests to the server (such as to load a web page or submit a form), and the server responds by sending the requested data back to the client.

The following is a request made by a client to reach to load my blog site at www.ahaliblogger.tech.

Figure 1.4 – A DNS request flow to ahaliblogger.tech

In the diagram, a client makes a request to reach ahaliblogger.tech. As the request flows through several DNS servers, an authoritative server responds to the client with the proper information.

Client/server architecture has several advantages over other computing models. One advantage is that it is scalable. The systems can be easily expanded to accommodate more users. Another advantage is that it is reliable. Client/server systems are less likely to fail than other networking computing models.

However, client/server architectures also have some disadvantages. One disadvantage is that it can be complex to design and implement. Another disadvantage is that it can be expensive to maintain.

Peer-to-peer architecture

A peer-to-peer (P2P) network architecture is a type of network in which each computer or device (known as a peer) is able to act as both the client and the server. This means that each peer is able to both request and provide a response to other peers on the network, without the need for a central server or authority to manage the network.

Peer-to-peer networks are often decentralized and self-organizing and can be used for a wide range of applications, including file sharing, online gaming, and distributed computing.

An example of a peer-to-peer network architecture is a BitTorrent file-sharing network.

Figure 1.5 – How BitTorrent works

In this network, clients (peers) share files with each another by breaking the files into small pieces and distributing them across the network. The (BitTorrent) client contacts a “tracker” specified in the .torrentfile (https://www.howtogeek.com/141257/htg-explains-how-does-bittorrent-work/).

Each client is able to download pieces of the file from multiple other peers and can also upload pieces of the file to other peers. This allows the efficient distribution of large files, as the load is distributed among many users rather than relying on a central server.

Hierarchical architecture

Hierarchical network architecture is a type of network design that uses a multi-layered approach to organize and manage network resources. It separates a network into distinct layers, where each layer has a defined function that, in turn, defines its role in the network. These layers are the access layer, the distribution layer, and the core layer.

Figure 1.6 – The three-tier network architecture model

The preceding diagram illustrates each layer in the hierarchical architecture model.

Figure 1.7 – The access layer of the three-tier hierarchical architecture model

The access layer is the point of entry into a network, and it is where end user devices such as computers, servers, printers, VOIP phones, and other IP devices connect. The access layer is responsible for providing basic (and, at times, more complex) connectivity and controlling access to the network.

Figure 1.8 – The distribution layer of the three-tier hierarchical architecture model

The distribution layer is where a network is divided into different segments or VLANs, and it acts as a bridge between the access and core layers. This layer is responsible for routing and filtering traffic, and providing security and Quality of Service (QoS) features.

Figure 1.9 – The core layer of the three-tier hierarchical architecture model

The core layer is the backbone of a network, and it is responsible for the high-speed switching and routing of traffic between different segments of the network. This layer is designed to be highly available and redundant, providing a fast and efficient data transfer throughout the network.

Figure 1.10 – The collapsed core model

The preceding diagram shows a variation of the hierarchical architecture, where the distribution and core layers are combined into what is known as a collapsed layer. In this design, the core and distribution functions are performed within one device (or a pair of devices).

The hierarchical design allows for better scalability, security, and manageability. Separating the different functions into specific layers also allows for better troubleshooting, as the network administrators can easily identify the problem area by looking at the specific layer.

The most common hierarchical architecture used in today’s network is spine/leaf.

Hybrid network architecture

Hybrid network architecture is a type of network architecture that combines elements of two or more different types of network architectures. The most common types of network architectures that are combined in a hybrid network are peer-to-peer (P2P) and client-server (C/S) architectures.

In a hybrid P2P/C/S network, a network is made up of both clients and servers, but the clients also have the ability to act as servers. This allows for network resources to be used more efficiently and can provide a better user experience, as data can be shared and distributed more easily.

For example, a hybrid P2P/C/S network might be used in a file-sharing application, where users can upload and download files from a central server but also share files directly with one another.

Another example would be combining the use of both wired and wireless connections. This allows a more flexible and reliable network – for example, a wireless connection can be used for mobile devices, while a wired connection can be used for more demanding applications such as video conferencing.

Figure 1.11 – An example of hybrid architecture – wireless and wired

A more common approach to hybrid network architecture is distributed computing systems, where a combination of cloud computing and edge computing is used. This allows data processing to take place at the edge of the network, close to the source of the data, while still giving you the ability to offload to the cloud for more processing power and storage.

An example is Tesla’s self-driving car. The car’s sensor constantly monitors certain regions around it, detecting an obstacle or pedestrian in its way, and then the car must be stopped or move around without hitting anything (https://www.geeksforgeeks.org/difference-between-edge-computing-and-fog-computing/). The vehicle must process the data quickly to determine what needs to be done next and also send it to backend systems (cloud or on-premises), where it is put in a data store (i.e., Hadoop clusters or cloud buckets). At this point, the data can be processed for further analysis, such as ETL processing or AI/ML pipelines.

The following diagram illustrates the use of edge devices in hybrid network architecture.

Figure 1.12 – Hybrid architecture – edge computing to cloud computing

Hybrid network architectures can provide the best of both worlds, the flexibility of P2P and the central control of C/S, and it can also allow for more efficient use of resources, better security and scalability, and a better user experience.

Spine-leaf architecture

A spine-leaf network architecture is a type of data center network architecture in which all devices are connected to leaf switches, which, in turn, are connected to spine switches.

The leaf switches provide end devices with access to a network, while the spine switches provide high-speed interconnections between the leaf switches. This architecture creates a flat, non-blocking network that allows efficient communication between devices and provides high redundancy.

Figure 1.13 – Spine-leaf architecture

The architecture can also be easily scaled to support a large number of devices and high throughput. The purpose of this architecture is to provide a cost-effective, scalable, and high-performance solution for modern data centers.

Summary

A network architect falls under the umbrella of the many architects that an organization may have, and it is vital to any organization’s success. The role and function of the network architect are more specific than that of a CA or SA but just as important when understanding the needs and requirements of stakeholders, end users, and leadership within an organization.

The network architecture is just as vital, as it’s the backbone of the entire organization. The design determines its flexibility, capacity to change, ability to introduce newer technologies and decommission older systems, and whether it is agile enough to support market changes in an organization, while simultaneously supporting end user requests for resources and services.

In the next chapter, we’ll dive deeper into the network architect in an organization.

Further reading

Why Networks Are Evolving Toward Leaf-Spine Architectures: https://www.networkcomputing.com/networking/why-networks-are-evolving-toward-leaf-spine-architectures/Multitier architecture: https://en.wikipedia.org/wiki/Multitier_architectureCisco Networking Academy Connecting Networks Companion Guide: Hierarchical Network Design: https://www.ciscopress.com/articles/article.asp?p=2202410&seqNum=4

2

Network Architect in an Organization

This chapter will dive deeper into the function of a network architect in an organization. The position of a network architect within an organization can vary depending on the size and structure of the company. In general, the network architect is often found in the IT department and may report to a manager or director of IT.

In larger organizations, the network architect may be part of a dedicated network architecture team that is responsible for designing, planning, and maintaining the organization’s network infrastructure. In smaller organizations, the network architect position may be standalone or combined with other IT roles.

In some cases, the network architect may also be part of a larger technical architecture team that is responsible for the overall technical direction of the organization. This team may include other types of architects responsible for other areas, such as security, data centers, or software development.

Additionally, network architects may also report to a CTO or CIO who is responsible for the overall technology strategy of the organization.

In this chapter, we’re going to cover the following main topics:

Planning, designing, installing, upgrading, and maintaining network projectsMaking recommendations to move the network to an advanced level and reduce operating costsDocumenting the network process for future uses

Let’s get started!

Planning, designing, installing, upgrading, and maintaining network projects

The purpose of a network architect’s role in planning, designing, installing, and upgrading network projects is to ensure that the organization’s network infrastructure is reliable, efficient, and secure and that it supports the organization’s business needs.

Some projects may be completed within a few weeks, while others may take well over two years just to witness and reap the benefits of cost savings identified from the start. It’s not an easy endeavor to undertake, as a tremendous amount of effort goes into these events. A network architect must be involved from beginning to end and materially participate, to some extent, at all levels.

Let’s break down each event:

Planning: The network architect plans the project by gathering requirements, identifying objectives, and defining the project scope. This helps to ensure that the project is aligned with the organization’s business needs and that all stakeholders are aligned on the project goals.Designing: The network architect designs the new network infrastructure, creating detailed logical and physical diagrams, and specifying the hardware and software that will be used. This helps to ensure that the new network will be efficient, reliable, agile, and secure, to support the organization’s business needs and current requirements.Installing: The network architect oversees the installation of the new network, including the installation and configuration of hardware and software. This helps to ensure that the new network is installed correctly and that it is ready to be used by the organization.Upgrading: The network architect is also responsible for upgrading the network infrastructure as needed, which is essential to keep the network up to date with the latest technologies and security standards and to meet the growth needs of the organization.Maintaining: The network architect maintains the network infrastructure and ensures that it’s running smoothly and efficiently and that it’s able to support the organization’s business needs. This may involve troubleshooting, resolving network issues, compliance checks, auditing, and making changes to the network as needed.

Regardless of which of these events are being performed, questions a network architect should ask are “What is the organization trying to accomplish with this project?” and “What is the intended goal/outcome of this project?”

Let’s take a closer look at these steps.

Planning

A network architect begins the planning process by following these steps:

Defining the project scope: The first step is to define the scope of the project, including the objectives, requirements, and constraints of the project. This involves working with stakeholders to understand their needs and requirements and gathering information about the current network infrastructure. Additional information may come from industry reports, such as Gartner, to provide insight into what other organizations are looking to do.

Example: A high-frequency trading platform has a requirement for low latency to serve its customers with the most accurate financial data possible.

Conducting a network assessment: A network assessment is vital in an IT project because it provides a comprehensive understanding of the current state of the network. It establishes a baseline for activities moving forward from that point in time. The network architect will conduct an assessment of the current network infrastructure, determining network readiness and compliance with industry standards, identifying any issues or bottlenecks that need to be addressed, as well as opportunities for improvement.

Example: Because of the high-frequency trading (HFT) platform’s requirement for low latency, an assessment was done illustrating that the current switching fabric is past its usefulness and cannot support the requirement. A new switching fabric will be needed to support the platform.

Developing a project plan: Based on the information gathered during the project scope definition and network assessment, the network architect will develop a detailed project plan. It provides a roadmap for the project and helps to ensure that the project is completed on time, within budget, and to the desired quality level. A project plan outlines the objectives, scope, deliverables, timeline, budget, and resources required for a project.

This plan will outline milestones, timelines, resource requirements, and any other relevant information to complete the project successfully. The project plan will be used to determine how much funding will be allocated for the project. A well-defined project plan can increase the chances of project success and minimize the impact of unexpected events on the project.

Example: Based on the information gathered about the HFT platform, the project will take about 4 months:

Month 1 – procure new switchesMonth 2 – install, configure, and test new switchesMonth 3 – place new switches into production, cutover, and testMonth 4 – decommission old switching fabricIdentifying risks and constraints: In addition and inclusive in the project plan are identifying the potential risks and constraints that can impede progress, impact current operations, or cause potential outages for an extended period of time. It helps to ensure that the project is completed on time, within budget, and to the desired quality level.