Netdesignmgmt

|

|

½ Ô structured systems analysis and design
process
Network analysis phase
½ Meeting with users to determine the needs and
applications
½ Estimating data traffic on each part of the network
½ Designing circuits needed to support this traffic and
obtains cost estimates
Implementation phase:
½ Building and implementing the network
½ Takes place a year or two later
½ Works well for static and slowly evolving
networks (although costly and time consuming)
Copyright 2005 John Wiley & Sons, Inc 12 - 2

½ ÿorces making the traditional design approach
less appropriate for many of today¶s networks:
Rapidly changing technology of computers, networking
devices and the circuits
½ More powerful devices, much faster circuits
Rapidly growing network traffic
½ Difficulty of estimating demand and growth
Shorter planning periods (3 years)
Dramatic change in the balance of costs
½ Before: Equipment; now: staff
½ Design goal: Minimize the staff time to operate (not
the hardware costs)
E.g., use similar standardized equipment for the ease
of management
u
u|

½ Ô simpler new approach
½ Key concept:
Network that use a few standard components are cheaper
than (in the long run) the networks that use many different
components
½ Start with a few standard components with ample
capacity (without extensive traffic analysis)
Called: narrow and deep (few types of devices, used over
and over)
Result: simpler design process, easily managed network
½ Phases of design
Needs analysis, Technology design, and Cost assessment
Cycles through, refining the outcome of each phase
u
u|

Cycles through all three

phases, refining the
outcome of each phase

-
|

Process of
cycling through
all three design
phases is
repeated until a
final design is
decided on.
|
½ To understand why the network is being built and
what users and applications it will support
To improve poor performance?
To enable new applications?
To upgrade, replace old equipment? or
To standardize equipment (one type, one protocol, etc)
½ Goals differ depending on the network
LÔN and BN (everything owned by the organization)
½ Design over capacity
Little additional cost after the initial cost
MÔN/WÔN (mostly rely on leased circuits)
½ Design under capacity
Lease additional circuits if necessary
u
½ Gain an understanding of the current operations

(applications and messages)
Most projects today involve upgrades and not new
network designs:
½ Ô good understanding of the needs already exist
Provides baselining against future needs
Clear picture of
½ Sequence of operations, processing times,
½ Work volumes
½ Current network
½ Existing cost
½ User/management needs

ð |
½ ðbjectives
Define the geographic scope of the network
Define applications and users that will use the network
½ The goal:
To produce a logical network design that
½ Describes what network elements will be needed to
meet the organization¶s needs
½ Specifies no technologies nor products at this stage
½ ÿocuses on functionality (e.g., high speed access
network)

|
½ Break the network into three conceptual parts
(based on their geographic and logical scope):
Ôccess layer
½ Lies closest to the user; often a LÔN
Distribution layer
½ Connects the access layer to the rest of the network;
often a backbone network
Core layer
½ Connects the different parts of the distribution layer
together; often a WÔN
½ Not all layers present in all networks
Small networks may not have a distribution layer

| |
½ Identify basic technical constraint at each
layer
Examples: If access layer is
½ Ô MÔN; then users need to use dial up lines
½ Ô LÔN; no need to use T1 lines
½ Identify constraints imposed by the
current network infrastructure
Example: adding a new building to an existing
office complex that use 100Base-T
½ Probably choose the same for new building

½ Start with the highest level
Begin by drawing a WÔN connecting locations
½ Next draw individual locations connected
to WÔN
Usually a series of diagrams, one for each
location
½ Gather information and characteristics of
the environment
Legal requirements, regulations, building
codes
M

Dial-up access
More complex, has its own core layer


½ Baselining
Review the applications currently used on the network
and
Identify their location so they can be connected to the
planned network
½ Include applications expected to be added to the
network
Review long and short range plans
½ Ôlso identify the hardware and software
requirements and protocol type for each
application
HTTP over TCP/IP; Windows file access

|
½ Ôssess the number and type of users that
will generate network traffic
Much network traffic comes from Internet use
(i.e., e-mail and WWW)
½ In the past, application systems accounted
for the majority of network traffic
ÿuture network upgrades will require
understanding of the use of new applications
½ Effect of video on network traffic

@

| |
½ Ôssess the traffic generated in each segment (for
each application and user)
Based on an estimate of the relative magnitude of
network needs (i.e. typical vs. high volume)
Can be problematic, but the goal is a relative
understanding of network needs
½ E.g, multimedia applications: high volume
½ ðrganize network requirements into
Mandatory, Desirable, and Wish-list requirements
Enables development of a minimum level containing
mandatory requirements (if cost is a constraint)

ë
|


½ Development of a physical network (or set
of possible designs)
Specify the computers (Clients and servers)
needed to support applications and users
½ New computers
½ Upgrades
Specify circuits and devices (routers,
gateways) to connect the computers

@
½ Specification of the computers needed in terms of
standard units
Ôllocate ³base level´ client computers to ³typical´ users
Ôllocate ³base level´ servers to typical applications
Ôssign ³advanced´ computers to ³high volume´ users
and servers
Beware of the definition for a ³typical´ unit
½ Keeps changing as hardware costs continue to fall,
and capabilities/capacities continue to increase

@
½ Deciding on the fundamental technology and
protocols
e.g., Ethernet, ÔTM, TCP/IP
½ Choosing the capacity each circuit will operate at
e.g., 10 Mbps, 100 Mbps, 1000 Mbps
Requires capacity planning
½ Ôssess current and future ³circuit loading´
Ômount of data to be transmitted on a circuit
ÿocus on either average or peak circuit traffic
Ideal: Peak traffic
½ Estimate size and type of ³standard´ and ³advanced´
circuits for each LÔN, BN, WÔN
Should ³standard´ LÔN circuit be 10Base-T or higher

@
½ Ôverage traffic:
Estimate total characters transmitted per day per circuit
½ Peak traffic
Estimate maximum number of characters transmitted
per two second interval
½ Estimating Message volume
Count messages in a current network and multiply it
with a growth rate
Use analyzers if an existing network
½ Precision not a major concern
Stair step nature of communication circuit (lease
another line, or upgrade to 100Base-T)
Uncertainty to project future needs
@ ð

½ Cost of extra capacity vs. Cost of upgrading a
network
Upgrading costs 50-80% more (than building it right at
the first time)
Majority complains about being under capacity, not over
capacity
½ Most organizations intentionally overbuild
Rapid growth in demand
½ 5-50% annual growth factor, sometimes 100%
Difficulty in accurate prediction
½ Most end up using overcapacity within 3 years
Turnpike effect: when the network is efficient and
provides good service, it becomes heavily used
|

½ Used mostly in the technology design process
½ ÿirst step: Enter a diagram of the existing network
Created from scratch (as required by some tools), or
Discovered automatically (by some tools)
½ ðnce the diagram is complete
Ôdd information about the expected network traffic and
See if the expected level of traffic can be supported
½ May be accomplished through simulation models
½ ðnce simulation is complete
Examine results to see estimated delays and throughput
Change the design if necessary and rerun simulations

½ Ô set of physical network designs
General specifications for the hardware and software
required
Several alternative designs to do cost-benefit analysis
½ The crucial issue:
Design of the network circuits and devices
½ Ô new network designed from scratch
Important to define clients computers with care
½ Ô major part of the total cost

|

Ô switched 10/100Base-T collapsed backbone

@
½ Ôssessment of the costs of various physical
network design alternatives
½ Complex process; many factors; consider:
Circuit costs (leased circuits and purchased cabling)
Internetworking devices (switches and routers)
Hardware costs (servers, hubs, NICs & UPSs)
Software costs (network operating systems, application
software and middleware)
Network management costs including special hardware,
software, and training needed for network management
Test and maintenance costs for monitoring equipment and
supporting onsite repairs
ðperations costs to run the network

½ Ôn RÿP
Issued to potential vendors.
½ Revised set of physical network diagrams
Done after the vendor(s) selected
ÿinal technology design
Selected components (exact products and
costs)
½ Business case
To support the network design
Expressed in terms of business objectives

|
½ Several higher level concepts used to design
network for the best performance
Managed networks
½ Network management software and standards
½ Policy-based management
Network circuits
½ Traffic analysis
½ Service level agreements
Network devices
½ Device latency and device memory
½ Load Balancing
Minimizing network traffic
½ Content caching and content Delivery

|
½ Network that uses managed devices
Managed device: standard devices that can (in addition to
performing its basic functions (switching and routing))
½ Monitors traffic flows,
½ Monitors its status and other devices connected to
½ Records various data on messages it processes
½ Sends these data to manager¶s computer (on a request)
½ Sends alarms if a critical situation detected (such as a
failing device, or unusual increase in traffic)
Problems detected and reported by devices themselves
before problems become serious
½ Requires both hardware and software
Hardware: monitor, collect, transmit
Software: store, organize, analyze
|

½ Device (point) management software
Provide specific information about a device
½ Configuration, traffic, error conditions, etc
½ System management software
aka, enterprise management software
Provide analysis device info to diagnose patterns
½ Prevents alarm storms (for a failure on a circuit,
many connected devices sending alarms)
Software analyze these and correlates them and
generates a single alarm to the manager
½ Ôpplication management software
Monitor applications based on device info
ÿocus on delays and application layer packets
|

½ Ôpplication layer protocols defining type of
information collected and format of control
messages
Simple Network Management Protocol (SNMP)
½ Developed for Internet and LÔNs
½ Components of SNMP
Ôgent: collects device info and responds requests
from the manager
Management Information Base (MIB): database at
device stored by the agent
Network Management Station (NMS): Ôccess MIB,
sends control messages to agent
Common Management Interface Protocol (CMIP)
½ Developed for ðSI type networks
|
½ Remote Monitoring (RMðN)
Enables remote monitoring of SNMP devices
Provide network wide monitoring info to the manager
(rather than device wide info)
½ No need to look at individual devices
½ Reduces network management traffic
Collects info on various layers (data link, network,
application layer)
½ Provides a clear picture of types of traffic
Ôlso collects statistics based on IP addresses
½ Enables manager to observe any host-host traffic
½ Problems with SNMP
Limited functionality; security; vendor extensions
u

½ Enables managers to set priority policies
for traffic (to take effect when congested)
Example:
½ Manager: order processing to have the
highest priority
½ Software: configure devices using QoS
capabilities in ÔTM, TCP/IP, etc to give this
application the highest priority
½ Expected to become more important

| @
½ Play a critical role in designing network
for maximum performance
½ Important to size the circuit and place
them to match the traffic
½ Ôreas of concern:
Circuit loading and capacity planning (already
discussed before)
Traffic analysis, and
especially for
Service level agreements MÔN and WÔN

½ Performed to pinpoint why some circuits are heavily used
½ Example: Toronto-NY circuit overloaded
Immediate reaction: upgrade/add another circuit between Toronto-NY
Reason for the overload: NY-LÔ traffic
Ideal solution: new circuit directly between LÔ and NY

ë

½ Established between organizations and common
carrier and ISPs
½ Specify the exact type of performance that
common carrier will provide
Ôvailability
½ 99% can be down 3.65 days per year with no
penalty
½ 99.9% can be down 8.76 hours per year with no
penalty
Ôlso includes maximum response time and other
parameters
½ Specify penalties if the desired performance is
not provided
|
½ Network devices from different vendors
provide different capabilities
Some faster, some more reliable, etc,.
½ ÿactors important in network performance
Device latency
½ Delay imposed by device in processing
messages
Device memory
½ Size of memory in device
Load Balancing
½ Capability in sharing the network load

|
½ Ônother approach in improving network
performance
½ Ôttempts to move most commonly used
data closer to user reduces traffic
elsewhere
Providing servers with duplicate copies at
points closer to users
½ Ôpproaches in reducing traffic
Content caching
Content delivery

@ @
½ Basic idea: Store other people¶s Web data closer to

your users
Install a content engine (aka, cache engine) close to your
Internet connection
Install special content management software on the router
½ ðperations
Stores requests and responses (mostly static files)
Examines each outgoing request; if it requires a file
already in cache, it responds immediately (without going to
the requested site)
½ Stores contents form most commonly accessed sites (updates
them frequently)
½ Must operate at wire speeds (otherwise degrade performance)
½ Reduces traffic between Internet and ðrganization less
circuits to lease

@
½ Ô special type of Internet service provided by
³content delivery providers (CDPs)´
Ô CDP stores Web files for its client closer to the client¶s
potential users
Ôkamai, a CDP, operates 10,000 servers located near
busiest NÔPs and MÔEs
½ Servers contain most commonly requested web info
for some busiest sites like yahoo.com
½ When a user access a client¶s site, a software in
client¶s server looks for an Ôkamai server (closer to
the user)
½ Ôkamai server sends the static files, the client¶s
server sends the dynamic files of the site

½ Develop strong relationships with only few
vendors
Use a building block approach in designing networks
Use a few common, standardized technologies
everywhere in the network
½ Purchase technologies that will provide strong
network management capabilities
Cost to operate is now much more expensive than the
cost to purchase
½ Use powerful design and management tools
Saves money in the long run

|

½ Network management
Process of operating, monitoring and controlling the
network to ensure that
½ Network working properly (efficient data exchange)
½ Providing value to its users
½ Ô lack of planning and organization
Managers spend their time firefighting (reactive mode)
½ Dealing with breakdowns and immediate problems
½ Main areas of network management function:
Configuration management
Performance and fault management
End user support
Cost management
ð

|

½ Special organizations problems presented by
networking functions
Decentralized
½ Developers, gatherers, and users of data
Centralized
½ Traditional management of voice and data networks
Networks and servers owned and operated by
centralized IT department
½ ÿactors impacting organization of management
functions
Shift to LÔNs and Internet
Integrating LÔNs, WÔNs, and Internet
Integrating voice and data communications
ë|
½ Large scale move from using mainframes and
terminals to PCs, LÔNs and the Internet.
ÿuture of network management:
½ Successful management of multiple clients and
servers over LÔNs, BN,s and Internet
½ ÿocus on integration of organizational networks
and applications. Main problems:
Not all LÔNs use the same architecture
More types of network technology used, the more
complex network management becomes
½ Staff must be familiar with many different types of
devices

ë|!"|
½ Keys integrating them into one organization
Both LÔN/Web and WÔN managers to recognize that they
no longer have power
½ No more independent decision without considering the
impact on other parts
½ Single overall goal that best meets the needs of the
entire organizations
½ Require some managers to compromise on policies that
may not be in the best interest of its own network
Must adopt a written charter to
½ Define its purpose, operational philosophy, and long
range goals
Must develop individual procedures to implement policies

# $
½ Traditional voice and data networks (e.g., PðTS
and LÔNs) handled by separate managers
Voice Communication Manager (ÿacilities department):
½ Supervise telephone switchboard,; coordinate
installation and maintenance of the voice network
Data Communication Manager (IT department):
½ Install own data circuit; install and maintain
computers
½ Benefits of Integrating voice and data
Simplifies the network, and can lower network costs
Eliminates one department
Will likely happen within the next few years

@

½ Major functions:
Management of the network¶s hardware and
software and
Documenting that configuration and
Ensuring that they are updated when there is a
change in the configuration

@

| @
½ Ôdding and deleting user accounts
New user addition
½ Categorized as a member of a group
With corresponding privileges
½ Given a standard login script
Commands to run when user logs in
½ Updating software on client computers
Usually done automatically by Electronic Software
Distribution (ESD) over the network at predefined time
½ Reduces cost of configuration management (long run)
½ Eliminates manual updates for each client
½ Produces accurate documents and reports
½ Being standardized: Desktop Management Interface (DMI)
$

½ Performance management
Ensuring the network is operating as efficiently as
possible
½ ÿault management
Preventing, detecting, and correcting faults in the
network circuits, hardware, and software
½ Both require
Network monitoring
½ Tracking the operation of network circuits and
devices
Determining how heavily circuits and devices are being
used
Ensuring circuits and devices are operating properly
|
½ Done by network management software

½ Involves Network ðperations Centers (NðCs)
Ô centralized place enabling managers to monitor the
network and respond to problems before users complain
½ Collect operational statistics from devices
Physical network statistics
½ Come from modems, multiplexers, and circuits linking
hardware devices
Logical network information:
½ Come from performance measurement systems
User response times, traffic volume on a specific circuit,
the destinations of network packets, and other indices
showing the network¶s service level

@
½ Requires developing a central control process for
problem reporting and troubleshooting
Maintain a central phone number for users to report
problems
Establish a central troubleshooting group
½ ÿunctions include contacting hardware, software
vendors or common carriers
½ Detecting and reporting network problems
By the help desk or NðC; by the user; and
By managed devices
½ Record data on messages processed and send this
info back to a central database
½ Detect its own faulty parts and send alarms

½ Reports that indicate network faults
Ôutomatically produced by software packages
½ Main reasons for trouble tickets
Problem tracking
½ To determine status for correcting problems
Responsible people, schedule, status, resolution, etc
Problem statistics
½ Used to generate various statistical reports (number
of failures per card, circuit, hardware, etc.,)
Problem solving methodology
½ To ensure critical problems get higher priority
Management reports
½ To determine availability, product and vendor
reliability, vendor responsiveness
ë
½ Purpose
To record problems that must be corrected
and keep track of associated statistics
½ Helpful for reviewing problem patterns on
the network
½ Can be used to identify which network
components are the most problematic
½ Example of a trouble log:
37 calls for software problems, 26 calls for
modems, 49 calls for client computers, 2 calls
for common carriers

½ Main performance statistics
Number of packets moved on a circuit and
Response time
½ ÿailure statistics
Ôvailability:
½ Percent of time the network available to users
Number of hours per month the network is available
divided by the total of hours in a month (I.e., 720 hours)
Most networks: 99% to 99.5%
Downtime:
½ Percent of time network is not available

½ Mean time between failures (MTBÿ)
Number of hours or days of continuous operation
Indicates the reliability of a component
½ Mean time to repair (MTTR)
Ôverage number of minutes or hours until the failed
device is operational again
MTTRepair = MTTDiagnose + MTTRespond + MTTÿix
Ôverage number of Ôverage number of Ôverage number of

minutes until the minutes until the minutes until problem
root cause is service or vendor is fixed (shows
diagnosed (shows personnel arrives efficiency of repair
efficiency of NðC) at location people)
ð
½ Daily data about the normal operations
Number of errors per circuit
Volume of transmission per circuit, computer, etc.,
Usage rates; % of capacity used
½ Used to identify devices or circuits that have
higher than average rates (thus may be good
candidate for upgrades)
½ Used for predicting future growth patterns and
failures
May be accomplished by establishing quality control
charts that
½ Tracking network performance against an upper and
a lower limits of a statistics
A @@

½ Solving the problems users encounter
while using the network
½ Main functions within end user support:
Resolving network faults (discussed already)
Resolving user problems
End user Training

-

½ Major sources of problems (with user equipment)
Hardware device failures (easiest to fix)
Lack of user knowledge on proper operation (easier to
fix)
½ Solved by discussing the problem with user and
taking the person through the process step by step
Problems with software, software settings or software
incompatibility (hardest to fix)
½ Could be result of a bug or software not functioning
properly
½ May requires expertise with that specific software
½ May require software upgrades

-

½ Ôssistance requested (by user) form the help
desk
½ Trouble ticket created and maintained by the
trouble log
½ Problem resolved by the receiving staff members
If not resolved, problem is escalated
½ Levels of problem resolution process
Help desk: Resolve about 85% of problems
Staff members with specialized skills specific to the
problem at hand: Brought in when help desk can¶t
solve
Technical specialists with a higher level of training:
Contacted by level 2 to look into harder problems
@

½ ðne of the most challenging areas lately
Traffic growing more rapidly than the budget
ÿorcing managers to provide greater capacity at an ever
lower cost per megabyte

@
½ Total Cost of ðwnership (TCð)
Ô measure of how much it costs per year to keep one
computer operating
Includes cost of
½ Repairs and software/hardware upgrades
½ Support staff (maintain, install, administer, etc)
½ Training and technical support
½ Time ³wasted´ by the user when problems occur
TCð of a Windows computer
½ Tðð HIGH - $8-12,000 per computer per year
½ Main culprit: inclusion of ³wasted´ time
Not commonly accepted

@%@&'
½ Net Cost of ðwnership (NCð)
Ôn alternative to TCð; also called as ³real TCð´
Measures only direct costs
½ Leaving out so-called ³wasted´ time
NCð costs per computer: between $1500-$3500
½ Net management for a 100-user network require an
annual budget of between $150,000 - $350,000
Largest network budget items (with NCð):
½ Personnel cost, accounting for 50-70% of costs
½ WÔN circuits
½ Hardware upgrades and replacement parts
Important message: ÿocus should be on ways to reduce
personnel time, not hardware costs
|
@

| u

½ Difficult to manage
Networks growing rapidly requiring more staff and
more equipment
½ Use charge-back policies to counter increasing
cost
Ôllocate costs associated with the network to specific
users
½ Users must pay for their usage (by moving part of
their budget) to the network group
Ôpplicable to WÔN and mainframe users as a cost
accounting mechanism
Difficult to implement on LÔNs

-
@
½ Develop standard hardware/software configurations
for client computers, servers, and network devices
Easier to diagnose and fix problems; Easier to learn
½ Ôutomate as much of the network management
process as possible
Use of ESD, DHCP and a other network management tools
½ Reduce the cost of installing new hardware/software
Reduce the staff time spent in installing; Work with vendors
½ Centralize help desks
More specialists in one location faster problem resolution
½ Move to thin client architectures
Reduces software and support costs

½ Network management requires
Ô good understanding of networking technologies
Ôn ability to work with end users and management
Ôn understanding of key elements driving network costs
½ Requires special skill to explain the business
value of the networks to senior management
Needed to justify increased cost of management
½ Network management increasing its complexity
New, more intelligent technologies in managing
networks
More reliable, but more expensive and requires new
skills in designing, installing and managing
½ Difficulty in keeping the staff

Netdesignmgmt

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Netdesignmgmt

Transféré par

Droits d'auteur :

Formats disponibles

|  

Cycles through all three

Copyright 2005 John Wiley & Sons, Inc 12 - 5

½ Gain an understanding of the current operations

Copyright 2005 John Wiley & Sons, Inc 12 - 8

Copyright 2005 John Wiley & Sons, Inc 12 - 9

Copyright 2005 John Wiley & Sons, Inc 12 - 10

Copyright 2005 John Wiley & Sons, Inc 12 - 11

More complex, has its own core layer

Copyright 2005 John Wiley & Sons, Inc 12 - 14

Copyright 2005 John Wiley & Sons, Inc 12 - 15

Copyright 2005 John Wiley & Sons, Inc 12 - 16

Copyright 2005 John Wiley & Sons, Inc 12 - 17

Copyright 2005 John Wiley & Sons, Inc 12 - 18

Copyright 2005 John Wiley & Sons, Inc 12 - 19

Copyright 2005 John Wiley & Sons, Inc 12 - 23

Copyright 2005 John Wiley & Sons, Inc 12 - 24

Ô switched 10/100Base-T collapsed backbone

Copyright 2005 John Wiley & Sons, Inc 12 - 26

Copyright 2005 John Wiley & Sons, Inc 12 - 28

Copyright 2005 John Wiley & Sons, Inc 12 - 33

Copyright 2005 John Wiley & Sons, Inc 12 - 34

Copyright 2005 John Wiley & Sons, Inc 12 - 35

Copyright 2005 John Wiley & Sons, Inc 12 - 37

Copyright 2005 John Wiley & Sons, Inc 12 - 38

½ Basic idea: Store other people¶s Web data closer to

Copyright 2005 John Wiley & Sons, Inc 12 - 39

Copyright 2005 John Wiley & Sons, Inc 12 - 41

Copyright 2005 John Wiley & Sons, Inc 12 - 44

Copyright 2005 John Wiley & Sons, Inc 12 - 45

Copyright 2005 John Wiley & Sons, Inc 12 - 46

Copyright 2005 John Wiley & Sons, Inc 12 - 47

½ Done by network management software

Copyright 2005 John Wiley & Sons, Inc 12 - 50

Copyright 2005 John Wiley & Sons, Inc 12 - 54

MTTRepair = MTTDiagnose + MTTRespond + MTTÿix

Ôverage number of Ôverage number of Ôverage number of

Copyright 2005 John Wiley & Sons, Inc 12 - 57

Copyright 2005 John Wiley & Sons, Inc 12 - 58

Copyright 2005 John Wiley & Sons, Inc 12 - 59

Copyright 2005 John Wiley & Sons, Inc 12 - 61

Copyright 2005 John Wiley & Sons, Inc 12 - 62

Copyright 2005 John Wiley & Sons, Inc 12 - 64

Copyright 2005 John Wiley & Sons, Inc 12 - 65

Vous aimerez peut-être aussi

|