You are on page 1of 15

Telephone Network

Characteristics: Reliable - does what is expected of it Dependable - always there when you need it (remember 911?) Good quality (connection) - hearing each other well Reasons: Good planning, design, and implementation Good operation and management of network

Regional Center Class 1 switch

Regional Center Class 1 switch

To other Regional centers Sectional centers Primary centers Toll centers End offices To other Primary centers Toll centers End offices To other Class 4 toll points End offices

Sectional Center Class 2 switch

Sectional Center Class 2 switch

Primary Center Class 3 switch

Primary Center Class 3 switch

Toll Center Class 4 switch

Toll Center Class 4 switch

End Office Class 5 switch

End Office Class 5 switch Legend: Loop Direct T runk Toll-Connecting Trunk

Voice

Voice

Toll Trunk

Figu re 1.1 Te le ph one Ne two rk M od e l

Notice the hierarchy of switches Primary and secondary routes programmed Automatic routing Where is the most likely failure? Use of Operations Systems to ensure QoS

Operations Systems / NOC


Monitor telephone network parameters S/N ratio, transmission loss, call blockage, etc. Real-time management of network Trunk (logical entity between switches) maintenance system measures loss and S/N. Trunks not meeting QoS are removed before customer notices poor quality Traffic measurement systems measure call blockage. Additional switch planned to keep the call blockage below acceptable level Operations systems are distributed at central offices Network management done centrally from Network Operations Center (NOC)

Data and Telecommunication Network


Data communication network Terminal Terminal Host

Modem

Modem

Modem

Loop

Loop

Loop

Voice

Voice

Telecommunication network

Figur e 1.3 Data and Te le communicatio n Ne tworks

Computer data is carried over long distance by telephone (telecommunication network) Output of telephone is analog and output of computers is digital Modem is used to modulate and demodulate computer data to analog format and back Clear distinction between the two networks is getting fuzzier with modern multimedia networks

Architecture, Protocols and Standards

Communication architecture Modeling of communication systems, comprising functional components and operations interfaces between them Communication protocols Operational procedures intra- and inter-modules Communication standards Agreement between manufacturers on protocols of communication equipment on physical characteristics and operational procedures

User A Peer-Protocol Interface Application Layers Transport Layers

User Z

Application Layers Transport Layers

Physical Medium (a) Dire ct Communicatio n be twe e n End Syste ms System A Intermediate system System Z

User A Peer-Protocol Interface Application Layers Transport Layer Transport Layers Conversion Physical Medium Physical Medium

User Z

Application Layers

Transport Layers

(b ) Communicatio n be twe e n End Syste ms v ia an Inte rme diate Syste m

Figur e 1.11 Basic Communication Arch ite ctur e

Inter-layer interface: user and service provider Peer-layer protocol interface Analogy of hearing-impaired student Role of intermediate systems Gateway: Router with protocol conversion as gateway to an autonomous network or subnet

OSI Reference Model


User / Application program Layer 7 Layer 6 Layer 5 Layer 4 Layer 3 Layer 2 Layer 1 Application Presentation Session Transport Network Data link Physical

Physical medium

Figur e 1.12 OSI Pr oto col Laye rs

Importance of the knowledge of layer structure in NM

Application Protocols
OSI User Internet User VT FTAM MOTIS CMIP Presentation Layer SNMP Transport Layer SMTP FTP TELNET Terminal Application File Transfer Mail / Message Transfer Management Application

Figur e 1.19 Application Sp e cific Protoco ls in ISO and Inte rne t M ode ls

Internet user Telnet


File Transfer Protocol

OSI user Virtual Terminal


File Transfer Access & Mgmt

Simple Mail Transfer Protocol

Message-oriented Text Interchange Standard

Simple Network Common Management Management Protocol Information Protocol

NM Case Histories
The case of the Footprint Case of the crashing bridge
R epeater R epeater Bridge R epeater R epeater

ISP
Backup Serv er Mail Serv er

(a) M ulti-Se gme nt Bus LAN with Single Por t Bridge Conn e ctio n

R epeater

R epeater Bridge

R epeater

R epeater

ISP
Backup Serv er Mail Serv er

(b ) Dual M ulti-Se gme nt Bus LANs with Two -por t Bridge Conn e ctio n

Backup Serv er

Mail Serv er

H ub

H ub Bridge

H ub

ISP
(c) M ulti-Se gme nt Hub Co nfigur ation Figur e 1.20 Case History 2: Ne twork Co nfigur ation Ev olution

Common Network Problems


Loss of connectivity Duplicate IP address Intermittent problems Network configuration issues Non-problems Performance problems

Challenges of IT Managers
Reliability Non-real time problems Rapid technological advance Managing client/server environment Scalability Troubleshooting tools and systems Trouble prediction Standardization of operations - NMS helps Centralized management vs sneaker-net

Network Management
Network Management Network Provisioning Planning Design Network Operations Fault Management / Service Restoration Configuration Management Performance Management / T raffic Management Network Installation Security Management Network Repairs Accounting Management Reports Management Inventory Management Data Gathering & Analyses Facilities Installation & Maintenance Routine Tests Network Network Maintenance Fault Management Trouble Ticket Administration

Figure 1.21 Network Management Functional Groupings

OAM&P Operations Administration Maintenance Provisioning

NM Functional Flow Chart


Network Users

Management Decision New Technology

Configuration Data TT Restoration

Performance & Traffic Data

Engineering Group - Netw ork Planning & Design

Operations Group NOC - Netw ork Operations

I & M Group -Netw ork Installation & Maintenance

Fault TT

Installation

Figure 1.22. Ne twork M anage me nt Functional Flow Chart

NM Components
NMS

Network Agent

Network Agent

Network Objects

Network Objects

Figure 1.24 Ne twork M anage me nt Compone nts

Status and Future Trends

Status: SNMP management Limited CMIP management Operations systems Polled systems Future trends: Object-oriented approach Service and policy management Business management Web-based management

You might also like