139,99 €
IT infrastructures are now essential in all areas and sectors of human activity; they are the cornerstone of any information system. Thus, it is clear that the greatest of care must be given to their design, implementation, security and supervision in order to ensure optimum functionality and better performance. Within this context, Systems and Network Infrastructure Integration presents the methodological and theoretical principles necessary to successfully carry out an integration project for network and systems infrastructures. This book is aimed at anyone interested in the field of networks in general. In particular, it is intended for students of fields relating to networks and computer systems who are called upon to integrate their knowledge and skills, gained throughout their academic study, into a comprehensive project to set up a complete infrastructure, while respecting the necessary specifications.
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 194
Veröffentlichungsjahr: 2020
Cover
Title Page
Copyright Page
Preface
Introduction to Project Management
1.1. Introduction
1.2. Project management
1.3. Project management methods and tools
1.4. Chapter summary
2 Simulating Network Architectures with GNS3
2.1. Introduction
2.2. Definition
2.3. Introduction to GNS3
2.4. Chapter summary
3 Green IT
3.1. Introduction
3.2. Introduction of concept
3.3. Green IT trigger factors
3.4. Benefits of Green IT
3.5. The lifecycle of ICTs
3.6. Mechanisms and technical solutions for the implementation of a Green IT infrastructure
3.7. Green IT labels and standards
3.8. Some examples of Eco-ICTs
3.9 Chapter summary
4 Design of Network Infrastructures
4.1 Introduction
4.2. The founding principles of networks
4.3. Methods and models of IT network design
4.4. Assessment of needs and choice of equipment
4.5. Chapter summary
5 Network Services
5.1. Introduction
5.2. DHCP service
5.3. DNS service
5.4. LDAP service
5.5. E-mail service
5.6. Web server
5.7. FTP file transfer service
5.8. Chapter summary
6 System and Network Security
6.1. Introduction
6.2. Definitions, challenges and basic concepts
6.3. Threats/attacks
6.4. Security mechanisms
6.5. Security management systems: norms and security policies
6.6. Chapter summary
7 Virtualization and Cloud Computing
7.1. Introduction
7.2. Virtualization
7.3. Cloud computing
7.4. Chapter summary
8 Quality of Service and High Availability
8.1. Introduction
8.2. Quality of service
8.3. High availability
8.4. Chapter summary
9 Monitoring Systems and Networks
9.1. Introduction
9.2. Main concepts of network and service supervision
9.3. Monitoring protocols
9.4. Monitoring tools
9.5. Chapter summary
References
Index
Other titles from ISTE in Information Systems, Web and Pervasive Computing
End User License Agreement
Chapter 1
Table 1.1 Main tools for project management
Table 1.2. Example of a RACI matrix
Chapter 4
Table 4.1. Functions of hardware layers
Table 4.2. Functions of software layers
Table 4.3. Layers of the TCP/IP model
Table 4.4. Functions of layers in the hierarchical model
Chapter 5
Table 5.1. List of main LDAP operations
Chapter 6
Table 6.1. Security means and services
Chapter 7
Table 7.1. Some examples of IaaS, PaaS and SaaS technologies
Chapter 8
Table 8.1. QoS parameters
Table 8.2. QoS parameters for voice and video
Table 8.3. Different priority categories
Table 8.4. Examples of classification criteria
Table 8.5. COS-DSCP correspondence table
Table 8.6. Modified COS-DSCP correspondence table
Table 8.7. Complete COS-DSCP correspondence table
Table 8.8. Rates of availability in nines
Table 8.9. PAgP protocol modes
Table 8.10. LACP protocol modes
Table 8.11. Comparison between HSRP, VRRP and GLBP
Chapter 9
Table 9.1. Typology of SNMP messages
Table 9.2. Plugin return codes
Table 9.3. Examples of free monitoring applications
Chapter 1
Figure 1.1. Facets of a project
Figure 1.2. The main phases of a project
Chapter 2
Figure 2.1.Creation of a new project. For a color version of the figure, se...
Figure 2.2.Description of GNS3 interface. For a color version of the figure...
Figure 2.3.Adding IOS Image. For a color version of the figure, see www.ist...
Figure 2.4.Example of a router image. For a color version of the figure, se...
Figure 2.5.Using the IDLE PC function. For a color version of the figure, s...
Figure 2.8.Adding routers to a topology. For a color version of the figure,...
Figure 2.9.Configuration of a router. For a color version of the figure, se...
Figure 2.10.Connection of two routers. For a color version of the figure, s...
Figure 2.11.Adding a switch. For a color version of the figure, see www.ist...
Figure 2.12.Connection to a switch. For a color version of the figure, see ...
Figure 2.13.Switch configuration. For a color version of the figure, see ww...
Figure 2.15.Creation of a cloud connection. For a color version of the figu...
Figure 2.16.Configuring the cloud. For a color version of the figure, see w...
Figure 2.17.Adding the interface. For a color version of the figure, see ww...
Figure 2.18.Connecting the cloud with the switch. For a color version of th...
Chapter 3
Figure 3.1 Lifecycle of ICT equipment. For a color version of the figure, s...
Figure 3.2 Cool corridor solution. For a color version of the figure, see ww...
Chapter 4
Figure 4.1. Standard network classifications
Figure 4.2. OSI model. For a color version of the figure, see www.iste.co.uk...
Figure 4.3. TCP/IP model
Figure 4.4. OSI model versus TCP/IP model. For a color version of the figure...
Figure 4.5. Network delivery time
Figure 4.6. Hierarchical model. For a color version of the figure, see www.i...
Figure 4.7. Clustering of the distribution and core layers. For a color vers...
Chapter 5
Figure 5.1. Overall functioning of DHCP
Figure 5.2. Stage 1 of the DHCP process
Figure 5.3. Stage 2 of the DHCP process
Figure 5.4. Stage 3 of the DHCP process
Figure 5.5. Stage 4 of the DHCP process
Figure 5.6. A DHCP relay
Figure 5.7. Tree organization of domain names. For a color version of the fi...
Figure 5.8. DNS operating principle. For a color version of the figure, see ...
Figure 5.9. LDAP mode of operation
Figure 5.10. Example of a data tree (DIT)
Figure 5.11. E-mail architecture
Figure 5.12. Virtual web servers
Figure 5.13. Virtual hosting by IP address and ports (Apache)
Figure 5.14. Virtual hosting by names
Figure 5.15. Virtual host by IP and name
Figure 5.16. FTP architecture
Chapter 6
Figure 6.1. Various impacts of security
Figure 6.2. The role of a firewall
Figure 6.3. Demilitarized zone (DMZ)
Figure 6.4. Proxy operating principle
Figure 6.5. IPsec operating modes with AH mechanism. For a color version of ...
Chapter 7
Figure 7.1. Virtualization of servers. For a color version of the figure, se...
Figure 7.2. Categories of virtualization
Figure 7.3. Virtualization by isolation. For a color version of the figure, ...
Figure 7.4. Paravirtualization. For a color version of the figure, see www.i...
Figure 7.5. Complete virtualization. For a color version of the figure, see ...
Figure 7.6. Cloud service models
Figure 7.7. Distribution of responsibility for cloud computing service deliv...
Figure 7.8. Pizza as a Service analogy. For a color version of the figure, s...
Chapter 8
Figure 8.1. General principles of QoS establishment. For a color version of ...
Figure 8.2. Basic principles of RSVP. For a color version of the figure, see...
Figure 8.3. IPv4 header and TOS/DSCP fields. For a color version of the figu...
Figure 8.4. IPv6 header and traffic class field. For a color version of the ...
Figure 8.5. Structure of TOS (Type Of Service) field
Figure 8.6. DSCP (Differentiated Service Code Point) field structure
Figure 8.7. Structure of IEEE 802.1q frame. For a color version of the figur...
Figure 8.8. Topology of our example
Figure 8.9. Examples of the application and corresponding DSCP values. For a...
Figure 8.10. Implementation of a VoIP solution (first architecture)
Figure 8.11. Implementation of a VoIP solution (second architecture)
Figure 8.12. Example of implementation of a VoIP solution
Figure 8.13. Failure of prioritized frame transmission. For a color version ...
Figure 8.14. Successful transmission of prioritized frames
Figure 8.15. Principle of the STP protocol
Figure 8.16. EtherChannel operation
Figure 8.17. Mock LACP and PAgP protocol configurations
Figure 8.18. Mock configuration of the HSRP protocol. For a color version of...
Figure 8.19. Simulation of a Router 1 breakdown. For a color version of the ...
Chapter 9
Figure 9.1. Functionalities of a monitoring system
Figure 9.2. Active monitoring
Figure 9.3. Passive monitoring
Figure 9.4. SNMP requests, responses and alerts
Figure 9.5. MIB structure
Cover
Table of Contents
Begin Reading
iii
iv
ix
x
xi
1
2
3
4
5
6
7
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
27
28
29
30
31
32
33
34
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
113
80
81
82
83
84
85
86
87
88
89
90
91
92
93
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
173
174
175
176
177
179
180
181
182
183
184
185
186
187
188
189
190
191
Series EditorJean-Charles Pomerol
Saida Helali
First published 2020 in Great Britain and the United States by ISTE Ltd and John Wiley & Sons, Inc.
Apart from any fair dealing for the purposes of research or private study, or criticism or review, as permitted under the Copyright, Designs and Patents Act 1988, this publication may only be reproduced, stored or transmitted, in any form or by any means, with the prior permission in writing of the publishers, or in the case of reprographic reproduction in accordance with the terms and licenses issued by the CLA. Enquiries concerning reproduction outside these terms should be sent to the publishers at the undermentioned address:
ISTE Ltd27-37 St George's Road London SW19 4EUUKwww.iste.co.uk
John Wiley & Sons, Inc 111 River Street Hoboken, NJ 07030 USAwww.wiley.com
© ISTE Ltd 2020The rights of Saida Helali to be identified as the author of this work have been asserted by him in accordance with the Copyright, Designs and Patents Act 1988.
Library of Congress Control Number: 2020938682
British Library Cataloguing-in-Publication DataA CIP record for this book is available from the British LibraryISBN 978-1-78630-526-8
This book, a true independent learning tool intended principally for students of network and systems sectors, is a guide to understanding the various facets of a network and systems integration project by learning the underlying concepts and acquiring the skills necessary to implement such projects. It is aimed at helping students acquire technical skills stemming from the analysis of needs, the specification of infrastructure characteristics, the definition of the equipment and components of the resulting networks, and their incorporation into the construction of a complete high-performance infrastructure that will satisfy the needs of a client company. Moreover, the methodological and organizational skills needed to oversee this type of project in terms of various considerations such as cost and deadline are also necessary and will be furnished by this book. This book also addresses the concept of Green IT, in order to raise students' awareness of environmental issues before they begin their professional lives, so that they will take these issues into account during the deployment of IT infrastructures.
The ultimate objective of this book is to enable students to learn how to design and develop network infrastructures for medium-sized and large businesses, and, more specifically, how to analyze needs and subsequently translate them into the design of the topology of a network that is fit for purpose. How do we define need in terms of interconnection equipment? How do we put an optimized addressing scheme in place? How do we determine the technologies, tools and manufacturers best suited to create a high-quality, high-performance network that is highly secure and accessible while being eco-friendly and state-of-the-art at the same time?
This book is made up of nine chapters, set out in two complementary sections adapted for IT network technicians; specifically:
– A methodological and organizational section that will enable students to understand, from the first chapter, the concept of specifications, and how to decipher them and to acquire the knowledge needed to manage an IT project, that is, the corresponding approaches, methods and tools. Indeed, it is vital to plan every stage of the implementation of an IT solution, to be familiar with its principal actors, and to know how to develop an efficient communication plan with regard to deliverables requested, milestone dates, etc.
This section will also provide an overview of the basic concepts of simulation in Chapter 2, and will more specifically introduce the GNS3 tool for the prototyping and testing of IT infrastructures before their on-site deployment. The use of this type of software protects an IT infrastructure integration project team for disrupting the operation of the production network. In addition, GNS3 is highly prized for teaching purposes, particularly in the absence of network hardware.
This section will also present the aspects of the environmental impact of IT infrastructures, or Green IT, with the aim of introducing students to and increasing their awareness of this reduced energy consumption approach in all network infrastructure implementation projects.
– A technological section that will address the purely technical aspects of network infrastructures in an organically laid-out sequence based on the actual process of setup and implementation.
Chapter 4 which begins this section, gives a concise introduction to the main network services generally provided by IT infrastructures.
Chapter 5 The design of these infrastructures is a vital stage in the process of their implementation, which is discussed in Chapter 5.
Chapter 6 is dedicated to the theme of security. Any infrastructure integration project must be sure to implement certain security mechanisms depending on the needs of the client company.
Chapter 7 focuses on virtualization and cloud computing, two interdependent paradigms that are omnipresent in every network infrastructure today.
Concepts dealing with the quality of service (QoS) and high availability increasingly demanded by modern IT infrastructures, in which the types of applications are extremely diverse and performance is more and more of a priority, are discussed in Chapter 8.
The final chapter is dedicated to the supervision of a network infrastructure and its various tools, with the objective of monitoring the infrastructure installed in order to mitigate and possibly prevent technical failures.
Each chapter ends with a mental map in the form of a visual summary of the main points of information discussed, in order to better structure them and facilitate their memorization.
Saida HELALI June 2020
“A little impatience can ruin a great project.”
Confucius
– Understanding the basic principles of project management.
– Learning the principal methods and tools of project management.
– Understanding the usefulness of specifications and how to interpret them.
Managing an IT project is similar to managing any type of project in general. According to Wysocki, a project is a sequence of unique, non-repetitive, complex and connected activities intended to achieve an objective. This must be done within both a specific time frame and a budget, and in compliance with a set of specifications.
An IT project (ITP) requires technical skills (programming, security, networks, architecture, etc.), as well as organizational and communication skills. The objective is to design a reliable, viable and satisfactory IT solution for a client, particularly in terms of agreeing upon deadlines, cost and quality. There are multiple aspects to a project:
– functional: responds to a need;
– technical: complies with clearly defined specifications and limitations;
– organizational: adheres to a predetermined mode of operation (roles, culture, function, resistance to change, etc.);
– temporal: complies with deadlines;
– economic: adheres to a budget.
Figure 1.1.Facets of a project
Project management is an approach based on the application of knowledge, skills, tools, and techniques to project activities aimed at fulfilling the expectations of the parties involved in the project.
Every project can be broken down into phases. Each phase can be further broken down into stages, and these stages into tasks. The main phases of a project are shown in Figure 1.2.
Figure 1.2.The main phases of a project
The initiation phase consists of defining the work to be carried out. It recalls its genesis, usefulness and end goal in answering “why” and “what”
questions. The expected completion date can be set during this phase, and an overall budget can be estimated. A set of specifications must be drawn up at this point.
– The design phase involves the actual definition of the project; it structures, organizes and plans it. Its objective is to prepare and organize the implementation of the elements laid out during the initiation phase.
– The execution phase represents the realization or implementation of the project. Each of the points laid out in the action plan is worked on during this phase, according to the set of specifications.
– The closure phase involves building on recent experience with the goal of ongoing improvement through assessment reports and rigorous documentation.
Project management methodologies enable a project to succeed and comply with the deadlines, budget and resources provided. They help each stage of the project to be completed, from planning to implementation, in the interests of efficiency and profitability.
Principal methodologies include:
a. Classic methods: these methods are most often used in project management. They are referred to as “cascading” because each stage must end by moving on to the next. The major disadvantage of this approach lies in its lack of flexibility with regard to changes.
b. Agile methods: these methods are gaining more and more popularity. They offer more flexibility and control in project management and better fulfill client expectations. Client needs are the cornerstone of agile methods. The client is involved throughout the entire project, which is executed according to an iterative, incremental process. Scrum, the agile method most often used, introduces the concept of sprints, which represent the different stages of the project. Throughout the project, existing functionalities will be continuously improved. It is also possible to add new functionalities if needed. Scrum is based on three roles:
– the product owner, who sets the technical requirements for the product,
– the development team, which develops the project according to the needs specified by the product owner and the scrum master,
– the scrum master, who oversees the realization of these objectives and is responsible for management within the project team. Successful communication with the product owner and the development team lies within the remit of the scrum master.
c. Adaptive methods: these methods adjust themselves to fit variations in projects, especially those that are complex and difficult to manage with a classic approach.
d. Critical path method: this method corresponds to the full set of tasks that must be accomplished in order to complete the project by a predetermined date. These critical tasks must not be subjected to any delay, otherwise the project will fall behind schedule.
e. The PERT method: this method is used to manage sequencing in a project. It involves representing the project in the form of a graph, a network of tasks whose sequencing will enable the achievement of preset objectives.
All of the tasks necessary for the execution of the project are listed and put in a specific order, with their dependence on one another established.
In this method, the stages of a project are represented graphically in a PERT diagram, which establishes the critical path that determines the minimum duration of the project.
f. The PRINCE2 (PRojects IN Controlled Environments, version 2) method: this method is a structured, pragmatic and adaptable project management methodology that can be used for any type of project. It guarantees that projects will be delivered on time, within budget and ensuring risk, advantage and quality management.
g. The Lean Management method: this method is used to provide high-quality work with minimal money, resources and time.
A wide range of tools is available for the management of a project. These are used to increase productivity and efficiency. Thus, it is necessary to know which ones to choose depending on our needs.
Table 1.1 recaps the main tools available for each phase of a project.
Table 1.1Main tools for project management
Initiation (pre-project)
Design
Execution
Closure
Examples of tools
Objective treeRACI matrixSpecifications
ParetoWBSGantt diagramCommunication planRisk management
Collaborative work toolsBrainstormingProblem-solving toolsControl panel
Project review
This is an effective and practical tool for project management created by Henry Gantt in 1917, which remains the most widely used representation tool. It consists of a graphic diagram useful for project planning and gives information and time frames for a project's phases, activities, tasks and resources.
Tasks are put in rows and durations (days, weeks or months) in columns. They are represented by bars whose length is proportional to the estimated duration. These can take place sequentially or partially or entirely simultaneously.
The success of a project relies on the clear and precise definition of the roles and responsibilities of each actor involved. To do this, a RACI matrix is used. In this matrix, activities are laid out in rows and roles in columns. In each cell of the table, the role's responsibility for the activity is indicated, using the letters R, A, C or I.
Table 1.2.Example of a RACI matrix
Role 1
Role 2
...
Role m
Activity 1
R
A
I
C
Activity 2
I
R
I
A
...
A
R
C
I
Activity n
C
R
C
I
It can be used to set out responsibilities in a project or within a company or business.
