EEE 582 Telecom Network management Introduction Instructors: Vikas Singh

EEE 582Telecom Network management

Introduction

Instructors: Vikas Singh

Scope and Objective

• Scope and Objective of the course• The course covers

– management principles, – practices and technologies for managing telecommunication

and computer communication networks and services. – Discuss both theoretical and practical aspects of network

management. – SNMP-based protocols – TMN standards. – Network monitoring tools and systems. – RMON– web-based management. – Assignments

2Vikas Singh, CSIS Dept. BITS Pilani

Text books and Reference

• Text book– Mani Subramanian, Network Management: Principles

and Practice, Addison-Wesley, 2000.• Reference Books

– Sallings, W., SNMP, SNMPv2, SNMPv3, and RMON 1 and 2, Reading, MA: Addison-Wesley, 1998.

– Divakara K. Udupa, TMN Telecommunications Management Network, McGraw-Hill Professional Pub., 1999


Course Plan

Sl. No.

Topic No. of Lectures

Ref. to Text Book

i) Introduction 2 1.1 – 1.3 ii) Overview of networks, protocols and standards 3 1.4, 1.5

iii) Introduction to network management 2 1.8 –1 .11 iv) Network technology:

(a) LAN topologies and standards (b) Network components (c) WANs, transmission technologies, ISDN, and

broadband networks

2 2

1

2.1,2.2

2.3

2.4-2.6 v) Standards, models and languages for network

management 4 Chapter 3

vi) SNMPv1: organization and information models 4 Chapter 4 vii) SNMPv1: Communication and Functional models 3 Chapter 5

viii) SNMPv2: System architecture, protocol and compatibility with SNMPv1

3 6.1, 6.2, 6.5, 6.6

ix) SNMPv3: Architecture, Applications and security models

4 7.3 – 7.8

x) OSI Network and Systems Management 3 Appendix A xi) TMN standards: Functional, Physical and Service

architectures 3 11.1 – 11.7

xii) Network monitoring tools and systems 3 Chapter 12 xiii) RMON: Remote Monitoring 1 8.1 xiv) Web-based management 2 14.1 – 14.5

Total:

------- 42


Evaluation Scheme

Component Duration Weight

Test I 50 minutes. 20%

Test II 50 minutes. 20%

Assignments (Problem solving, reading assignments and Lab work)

Regular 20%

Compre 3 Hrs. 40%


Chapter 1

Data Communications

and

NM Overview


Question

• What is a network?• What is Network Management?• Why do we need Network Management?• What is the goal of network management?


Network ManagementWhat is it?• People and processes that coordinate and

plan• Tools that assist in Reporting, Trouble shooting,

and Performance Analysis• Applications that support a Network Services

Group in getting its job done

Why Network management?

• To keep network up and running• Identify problems before they take the network

down. • Minimize system downtime, thus increasing

productivity


Goal of network Management

• Goal of an NMS system is to ensure that the users of network receive the services with the quality of service they expect– With minimum service interruptions


Why use standards?• Without standards,

• Network Management Systems from different vendors would not be able to work together without additional effort and integration

• One is locked to a single vendor

• Allows interoperability of Network Management Systems from different vendors of different network elements

• Not restricted to single vendor for compatibility and interoperability


OutlineChapter 1

• Analogy of telephone network (section 1.1)

• Data and telecommunication network (1.2)

• Distributed computing environment (1.3)

• Internet and TCP/IP based Networks (1.4)

• Protocols and standards (1.5)

• IT management(1.7)

• Network management Goals , organization and Functions (1.8)

• Network and system management (1.9)

• Current status and future of network management 1.10


Telephone NetworkChapter 1

• Characteristics:• Reliable - does what is expected of it• Dependable - always there when you need

it• Good quality (connection) - hearing each

other well• Reasons:• Good planning, design, and implementation• Good operation and management of

network


Regional CenterClass 1 switch

Sectional CenterClass 2 switch

Primary CenterClass 3 switch

Toll CenterClass 4 switch

End OfficeClass 5 switch

Regional CenterClass 1 switch

Sectional CenterClass 2 switch

Primary CenterClass 3 switch

Toll CenterClass 4 switch

End OfficeClass 5 switch

Voice Voice

To otherRegional centersSectional centersPrimary centersToll centersEnd offices

To otherPrimary centersToll centersEnd offices

To otherClass 4 toll pointsEnd offices

Figure 1.1 Telephone Network Model

Legend:Loop

Direct Trunk

Toll-Connecting Trunk

Toll Trunk

• 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

Telephone Network Model (1.1)


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)


Information Transmission

• May be transmitted as:– Circuit switched mode– Message switched mode– Packet switched mode


Communication Network

Network Communications

Tele-communication network

Typically Circuit switched

Used for voice telecommunication

Also provide other services such as high speed dedicated transmission

Such as E1 in India and higher

Data Communication network

Typically Packet switched

Used for data transmission

May provide connection less or connection oriented services

May also provide VOIP 16Vikas Singh, CSIS Dept. BITS Pilani

Data and Telecommunication Network (1.2)

Terminal

Modem

Voice

Terminal

Modem Modem

Voice

Host

Data communication network

Telecommunication network

Figure 1.3 Data and Telecommunication Networks

Loop Loop Loop

• Computer data is carried over long distance by telephone (telecommunication network)

• Output of telephone is analog and output ofComputers 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

PSTN


IBM SNA Architecture

Mainframe

Communicationscontroller

Communicationscontroller

Clustercontroller

Clustercontroller

Figure 1.5 IBM Systems Network Architecture Model

Workstation Workstation

• IBM System Network Architecture (SNA) is a major step in network architecture

• SNA is based on multitude of (dumb) terminals accessing a mainframe host at a remote location

• SNA architecture is a centralized architecture, and not used any more 18Vikas Singh, CSIS Dept. BITS Pilani


DCE with LAN (section 1.3)

Ethernet

Workstation

Workstation

Host

Host

Workstation

(a) Hosts and Workstations on Local LAN

DCE.. Distributed Computing Environment

• Driving technologies for DCE:• Desktop processor• LAN• LAN - WAN network

• Questions: Why we need a LAN?• What are the advantages of a LAN network• What are the different networks you are familiar with?• Inter-LAN connectivity ?


Notes

LAN A LAN B

LAN C

Bridge /Router

Bridge /Router

Bridge /Router

WANcommunication link

• Major impacts of DCE:• No more monopolistic service provider• No centralized IT controller• Hosts doing specialized function• Client/Server architecture formed the core

of DCE network

LAN-WAN Network


Client Server

Controltransfer

Controltransfer

Figure 1.7 Simple Client-Server Model

• Post office analogy; clerk the server, and the customer the client

• Client always initiates requests• Server always responds• Notice that control is handed over to the receiving

entity.• What other analogies can you think of ?

Request

Response

Client/Server Model


Client/Server Examples

Client A Client Z

Server(a) Server with Multiple Clients

Client(joe.stone)

DomainNameServer

Mail server

(b) Dual Role of Client-Server

Figure 1.8 Client-Server in Distributed Computing Environment

Bridge

to [email protected]


Internet and Protocols• What is Internet

– A network of networks– Public networks peering with each other and

interconnected with each other– Each Network operating independently– A distributed Network– Uses packet switching– Based on TCP/IP protocols– Uses connection less network protocol for routing– Common applications: HTTP (Web browser), SMTP

(Simple mail transfer protocol) and FTP


Internet Architecture

FTP SMTP TELNET HTTP

TCP UDP

IP ICMP ARP & RARP

Ethernet X.25 PPP PMPP

Application

Transport

Network

Link Level

SNMP OthersVoice

Over IP


Internet Protocol Layers

APPLICATION

PRESENTATION

SESSION

TRANSPORT

NETINTER

INTRA

DATA LINK

PHYSICAL

APPLICATIONFTP ,SMTP,Telnet, HTTP, SNMP

TCP: Transport IP: Internet Protocol

IEEE 802X.25

HARDWARE

TCP/IP AND OSI: Functional Positioning of Layers

ISO/OSI Layered Model for data communications

TCP/IP Model for data communications


TCP/IP Based Networks• TCP/IP is a suite of protocols• Internet is based on TCP/IP• IP is Internet protocol at the network layer level• TCP is connection-oriented transport protocol and ensures

end-to-end connection• UDP is connectionless transport protocol and provides

datagram service• Internet e-mail and much of the network mgmt.

messages are based on UDP/IP• ICMP part of TCP/IP suite. An example of • SNMP is application layer protocol


Internet Configuration

LAN A LAN B

LAN C

Bridge /Router

Bridge /Router

Bridge /Router

LAN Y LAN Z

LAN X

Bridge /Router

Bridge /Router

Bridge /Router

Internet

Workstation

Mail Server

Figure 1.9 Internet Configuration

Mail Server

Workstation

Gateway

Gateway

DomainNameServer

Workstation(Joe)

PC (Sally)

Private TCP/IPNetworkAlso called Intranet

Private TCP/IPNetworkAlso called Intranet


Internet Configuration

Domain Name server

LAN BLAN A

Mail Server

B/R B/R

B/R

LAN CGateway1

Internet

Gateway

LAN abcB/R

B/R

LAN x

Mail Server

Asha’sWorkstation

Anand’s workstation

Asha’s email: [email protected]@dest.com

IntranetDomain name: bits-pilani.ac.in

Internet consists of multiple domains


mailto:Asha@b

Notes• Gateway: The Intranet or local network may have a

different set of protocols running as compared to Internet. As an example the client network might be using Novell LAN, which uses XNS protocol. Gateway 1 will provide protocol translation from XNS to TCP/IP


Autonomous SystemsInternet Routing Architecture

RR R

RR

Autonomous System AStub AS

Autonomous System B

RR

R

Autonomous System C

RR R

R

Autonomous System D

Multi-homed ASR Border Router: also called gateway router

R Interior Router(Transit AS for AS B)

R

R RR

R RR

R

RR RR


Architecture, Protocols and Standards

• Communication architecture• Modeling of communication systems, comprising

• functional components and• relationship between those components

• Defined by 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

• Questions: Examples of protocols?• Why do we need Protocols?• Why do we need standards? 32Vikas Singh, CSIS Dept. BITS Pilani

Communication ArchitectureUser A

Application Layers

Transport Layers

User Z

Application Layers

Transport Layers

Physical Medium

Peer-Protocol Interface

(a) Direct Communication between End Systems

User A

Application Layers

Transport Layers

User Z

Application Layers

Transport Layers

Physical Medium

Peer-Protocol Interface

(b) Communication between End Systems via an Intermediate System

Transport Layer

Conversion

Figure 1.11 Basic Communication Architecture

System A Intermediate system System Z

Physical Medium

• Inter-layer interface: user and service provider• Peer-layer protocol interface • Analogy of hearing-impaired student (protocol conversion)• Role of intermediate systems• Gateway: Router with protocol conversion as

gateway to an autonomous network or subnet 33Vikas Singh, CSIS Dept. BITS Pilani

User / Application program

ApplicationLayer 7

PresentationLayer 6

SessionLayer 5

TransportLayer 4

NetworkLayer 3

Data linkLayer 2

PhysicalLayer 1

Physical medium

Figure 1.12 OSI Protocol Layers

• Importance of the knowledge of layer structure in NM

OSI Reference Model


OSI Layers and Services LayerNo.

Layer Name Salient services provided by the layer

1 Physical -Transfers to and gathers from the physical medium rawbit data

-Handles physical and electrical interfaces to thetransmission medium

2 Data link -Consists of two sublayers: Logical link control (LLC) andMedia access control (MAC)

-LLC: Formats the data to go on the medium; performserror control and flow control

-MAC: Controls data transfer to and from LAN; resolvesconflicts with other data on LAN

3 Network Forms the switching / routing layer of the network

4 Transport -Multiplexing and de-multiplexing of messages fromapplications

-Acts as a transparent layer to applications and thusisolates them from the transport system layers

-Makes and breaks connections for connection-orientedcommunications

-Flow control of data in both directions

5 Session -Establishes and clears sessions for applications, andthus minimizes loss of data during large data exchange

6 Presentation -Provides a set of standard protocols so that the displaywould be transparent to syntax of the application

-Data encryption and decryption

7 Application -Provides application specific protocols for each specificapplication and each specific transport protocol system


PDU Communication Model

User A

Application

End System A

Physical Medium

Figure 1.14 PDU Communication Model between End Systems

Presentation

Session

Transport

Network

Data link

Physical

User Z

Application

End System Z

Presentation

Session

Transport

Network

Data link

Physical

UD(A) PCI

(P) PCI (A) PDU

(S) PCI

(N) PCI

(T) PCI

(P) PDU

(S) PDU

(D) PCI

(T) PDU

(N) PDU

UD

(D)PDU Data stream

• What is the relevance of PDU model in NM? 36Vikas Singh, CSIS Dept. BITS Pilani

SNICP

SNDCP

SNDAP

Transport

Data link

SNICP

SNDCP-SN

SNDAP-SN

Transport

Data link-SN

SNDCP-SN

SNDAP-SN

Transport

Data link

SNICP

SNDCP

SNDAP

Physical-SN

Data link-SN

Physical Physical-SNPhysical

Subnetwork MediumNetwork Medium

System A Gateway System N Subnet system N1

N ZA

N1 N2

N3

DTE-N1

DTE-A

A-N-Z Standard NetworkN-N1-N2-N3 Subnetwork under Node N

(a) Network configuration

(b) Protocol Communication

Figure 1.17 Gateway Communication to Proprietary Subnetwork

• cc:mail from a station in Novel IPX network to an Internet station with SMTP e-mail 1-21

Gateway Communications to a Proprietary Subnet


SNA, OSI, and Internet

Application

Presentation

Session

Transport

Network

SNICP

SNDCP

SNDAP

Data Link

Physical

Application SpecificProtocols

TransportConnection-

less: UDPConnection-

oriented: TCP

NetworkIP

Not Specified

Physical

Data Link

Path Control

Transmission Control

Data Flow Control

Presentation Services

End User Application

SNA OSI INTERNET

Figure 1.18 Comparison of OSI, Internet, and SNA Protocol Layer Models

• Similarity between SNA and OSI• Simplicity of Internet; specifies only layers 3 and 4• Integrated application layers over Internet• Commonality of layers 1 and 2 - IEEE standard

1-2238Vikas Singh, CSIS Dept. BITS Pilani

Application Protocols

OSI User

VT

FTAM

MOTIS

CMIP SNMP

SMTP

FTP

TerminalApplication

File Transfer

Mail / MessageTransfer

ManagementApplication

Presentation Layer Transport Layer

TELNET

Internet User

Figure 1.19 Application Specific Protocols in ISO and Internet Models

Internet user OSI userTelnet Virtual Terminal

File Transfer Protocol File Transfer Access & Mgmt

Simple Mail Transfer Message-oriented Text Protocol Interchange Standard

Simple Network Common ManagementManagement Protocol Information Protocol


NM Case Histories• The case of the Footprint (topology)• Case of the crashing bridge

Repeater Repeater Repeater Repeater

Bridge

Mail ServerBackup Server

Repeater Repeater Repeater Repeater

Bridge


Bridge


Hub Hub Hub

(a) Multi-Segment Bus LAN with Single Port Bridge Connection

(b) Dual Multi-Segment Bus LANs with Two-port Bridge Connection

(c) Multi-Segment Hub Configuration

Figure 1.20 Case History 2: Network Configuration Evolution


Common Network Problems

• Loss of connectivity

• Duplicate IP address

• (address management)

• 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 System Functionality

• OAM&P– Operations– Administration – Maintenance– Provisioning


Network ManagementNetwork

Management

NetworkProvisioning

Network Operations

NetworkMaintenance

Planning

Design

Fault Management

Trouble Ticket

Administration

Network Installation

Network Repairs

Facilities Installation

& Maintenance

Routine Network

Tests

Fault Management / Service Restoration

Configuration Management

Performance Management / Traffic Management

Security Management

Accounting Management

Reports Management

Inventory Management

Data Gathering & Analyses

Figure 1.21 Network Management Functional Groupings

•


NM Functional Flow Chart

Engineering Group

- Network Planning &Design

Operations GroupNOC

- Network Operations

I & M Group

-Network Installation &Maintenance

Fault TT

Configuration Data

TT RestorationPerformance & Traffic Data

Installation

Figure 1.22. Network Management Functional Flow Chart

NewTechnology

Network

Users

ManagementDecision

1-2845Vikas Singh, CSIS Dept. BITS Pilani

Network and system management

• System management: Includes the management of entire system, including the applications– If a user can not access a web page or can not send his/her e-mail, it does not matter

to him where the problem is. The problem may be with the user’s client, e-mail server etc. Or the problem may be in TCP/IP protocol.

• Network management: problems in lower layers of the TCP/IP, ISO/OSI architecture. Generally problems with network resources such as hub/switches/routers, or connectivity problems– Usually each NE vendor has its own network management system

• The network management system monitors all the network components, not only a given NE.

• Some examples are HP Ovenview, IBM Netview, Spectrum, Ciscoworks. • The trend is to integrate System and network management systems.


Network Management architecture(functional)

The common management messages consist of management information data (such as the type, id, and status of managed objects..)

Vendor A Vendor B

Common management

messages

1. The common messages: management and information data Exchange of monitoring data2. Management controls


Services and protocols

Vendor A

objects

objects

Vendor B

objects

objects

Application Services

Management Protocol

Transport Protocols

Application services: management related applications, such as configuration management, fault managementManagement protocols are SNMP and CMIP

- CMIP is complex and not used very much


NM Components

NMS

NetworkAgent

NetworkAgent

NetworkObjects

NetworkObjects

Figure 1.24 Network Management Components

NMS: Manages multiple network elements, via Network agents. Each Network element could have multiple objects. Note the Hierarchy

Same Domain


InteroperabilityNMS

Vendor A

NetworkAgent

NetworkAgent

NetworkObjects

NetworkObjects

NMSVendor B

NetworkAgent

NetworkAgent

NetworkObjects

NetworkObjects

Messages

Services & Protocols

• Message exchange between NMSs managing different domains

Two cooperating domains provide some services which are joint. The Communication between the 2 NMSs, allows NMS of Domain A/B, to integrate the Management information from the other domain

Domain A Domain B


Network management protocols

• CMIP (Common Management Information Protocol) for OSI model

• SNMP (Simple Network Management Protocol) for TCP/IP (internet)

• TMN (Telecommunication Management Network) standard for managing telecommunication networks. Issues for managing telecom network are little different, than TCP/IP network, so ITU has come up with TMN framework and architecture


Status and Future Trends

• Status: • SNMP management• Limited CMIP management• Operations systems• Polled systems

• Future trends:• Service and policy management • Business management• Web-based management


Appendix

Internet History

Internet History– Internet is a result of research funded by Defense Advanced Reassert

Projects Agency (DARPA) in the late sixties– This research was directed towards connecting different types of

computers with different interfaces and over different physical links – This technology includes a set of network standards, a set of

procedures/conventions for interconnecting networks and routing traffic among them

– Initially, this technology was used for computer communications between research oriented US Federal Government departments, and research institutes

– Now, this technology is commercially used everywhere in the world, and thousands of ISPs around the world provide Internet service

– Internet in technical terms is a collection of networks that are interconnected by Routers/Gateways


Internet History• 1962: RAND Paul Baran, of the RAND Corporation (a government agency), was

commissioned by the U.S. Air Force to do a study on how it could maintain its command and control over its missiles and bombers, after a nuclear attack. His final proposal was a packet switched network.

• 1968: ARPA awarded the ARPANET contract to BBN. BBN had selected a Honeywell minicomputer as the base on which they would build the switch– Backbones: 50Kbps ARPANET - Hosts: 4

• 1972: he first e-mail program was created by Ray Tomlinson of BBN.The Advanced Research Projects Agency (ARPA) was renamed The Defense Advanced Research Projects Agency (or DARPA)– Backbones: 50Kbps ARPANET - Hosts: 23 – ARPANET was currently using the Network Control Protocol or NCP to

transfer data.This allowed communications between hosts running on the same network.

• 1973: Development began on the protocol later to be called TCP/IP, it was developed by a group headed by Vinton Cerf from Stanford and Bob Kahn from DARPA. This new protocol was to allow diverse computer networks to interconnect and communicate with each other.– Backbones: 50Kbps ARPANET - Hosts: 23+

• 1974: First Use of term Internet by Vint Cerf and Bob Kahn in paper on Transmission Control Protocol.– Backbones: 50Kbps ARPANET - Hosts: 23+


Internet History (Cont’d)• 1983: Internet Activities Board (IAB) was created in 1983.• On January 1st, every machine connected to ARPANET had to use TCP/IP. TCP/IP

became the core Internet protocol and replaced NCP entirely. – The University of Wisconsin created Domain Name System (DNS) – Backbones: 50Kbps ARPANET, 56Kbps CSNET, plus satellite and radio

connections - Hosts: 562 • 1984: Arpanet divided into MILNET and ARPANET. Upgrade to CSNET was

contracted to MCI. New circuits would be T1. IBM would provide advanced routers and Merit would manage the network. New network was to be called NSFNET (National Science Foundation Network), and old lines were to remain called CSNET. – Backbones: 50Kbps ARPANET, 56Kbps CSNET, plus satellite and radio

connections - Hosts: 1024 • 1985: The National Science Foundation began deploying its new T1 lines, which

would be finished by 1988.– Backbones: 50Kbps ARPANET, 56Kbps CSNET, 1.544Mbps (T1) NSFNET, plus

satellite and radio connections - Hosts: 1961• 1986:The Internet Engineering Task Force or IETF was created to serve as a forum for

technical coordination by contractors for DARPA working on ARPANET, US Defense Data Network (DDN), and the Internet core gateway system. – Backbones: 50Kbps ARPANET, 56Kbps CSNET, 1.544Mbps (T1) NSFNET, plus satellite and radio

connections - Hosts: 230856Vikas Singh, CSIS Dept. BITS Pilani

Internet History (Cont’d)• 1987: BITNET and CSNET merged to form the Corporation for Research and

Educational Networking (CREN), another work of the National Science Foundation.– Backbones: 50Kbps ARPANET, 56Kbps CSNET, 1.544Mbps (T1) NSFNET, plus

satellite and radio connections - Hosts: 28,174• 1988: Plans to upgrade the network

– Backbones: 50Kbps ARPANET, 56Kbps CSNET, 1.544Mbps (T1) NSFNET, plus satellite and radio connections - Hosts: 56,000

• 1990: Merit, IBM and MCI formed a not for profit corporation called ANS, Advanced Network & Services, which was to conduct research into high speed networking.– It soon came up with the concept of the T3, a 45 Mbps line. NSF quickly

adopted the new network and by the end of 1991 all of its sites were connected by this new backbone.

While the T3 lines were being constructed, the Department of Defense disbanded the ARPANET and it was replaced by the NSFNET backbone. The original 50Kbs lines of ARPANET were taken out of service.

Tim Berners-Lee and CERN in Geneva implements a hypertext system to provide efficient information access to the members of the international high-energy physics community.

– Backbones: 56Kbps CSNET, 1.544Mbps (T1) NSFNET, plus satellite and radio connections - Hosts: 313,000


Internet History (Cont’d)• 1991: CSN discontinued: The operational costs of CREN are fully met through dues paid by its member organizations. – The NSF established a new network, the National Research and Education Network

(NREN). The purpose of this network is to conduct high speed networking research. It was not to be used as a commercial network, nor was it to be used to send a lot of the data that the Internet now transfers.

– Backbones: Partial 45Mbps (T3) NSFNET, a few private backbones, plus satellite and radio connections - Hosts: 617,000

• 1992: Internet Society is chartered.– World-Wide Web released by CERN.– NSFNET backbone upgraded to T3 (44.736Mbps)– Backbones: 45Mbps (T3) NSFNET, private interconnected backbones consisting mainly

of 56Kbps, 1.544Mbps, plus satellite and radio connections - Hosts: 1,136,000• 1993:InterNIC created by NSF to provide specific Internet services: directory and

database services (by AT&T), registration services (by Network Solutions Inc.), and information services (by General Atomics/CERFnet).Marc Andreessen and NCSA and the University of Illinois develops a graphical user interface to the WWW, called "Mosaic for X".– Backbones: 45Mbps (T3) NSFNET, private interconnected backbones consisting mainly

of 56Kbps, 1.544Mbps, and 45Mpbs lines, plus satellite and radio connections - Hosts: 2,056,000


Internet History (Cont’d)• 1994: No major to the physical network. The most significant thing that happened

was the growth. Many new networks were added to the NSF backbone. Hundreds of thousands of new hosts were added to the INTERNET during this time period.– Pizza Hut offers pizza ordering on its Web page.– First Virtual, the first cyber bank, opens.– ATM (Asynchronous Transmission Mode, 145Mbps) backbone is installed on

NSFNET.– Backbones: 145Mbps (ATM) NSFNET, private interconnected backbones

consisting mainly of 56Kbps, 1.544Mbps, and 45Mpbs lines, plus satellite and radio connections - Hosts: 3,864,000

• 1995: The National Science Foundation announced that as of April 30, 1995 it would no longer allow direct access to the NSF backbone. The National Science Foundation contracted with four companies that would be providers of access to the NSF backbone (Merit). These companies would then sell connections to groups, organizations, and companies.– $50 annual fee is imposed on domains, excluding .edu and .gov domains which

are still funded by the National Science Foundation.– Backbones: 145Mbps (ATM) NSFNET (now private), private interconnected

backbones consisting mainly of 56Kbps, 1.544Mbps, 45Mpbs, 155Mpbs lines in construction, plus satellite and radio connections - Hosts: 6,642,000


Internet History (Cont’d)• 1996: Most Internet traffic is carried by backbones of independent ISPs, including

MCI, AT&T, Sprint, UUNet, BBN planet, ANS, and more.• Currently the Internet Society, the group that controls the INTERNET, is trying to

figure out new TCP/IP to be able to have billions of addresses, rather than the limited system of today. The problem that has arisen is that it is not known how both the old and the new addressing systems will be able to work at the same time during a transition period.

• Backbones: 145Mbps (ATM) NSFNET (now private), private interconnected backbones consisting mainly of 56Kbps, 1.544Mbps, 45Mpbs, and 155Mpbs lines, plus satellite and radio connections - Hosts: over 15,000,000, and growing rapidly

• 1996 to 2005: explosive growth, e-commerce, e-gov, e-verything


A Brief summary of Internet 19

68/

69

ARPANetWith 4 nodes

BB Speed50 Kbps

1972

First e-mail programAgency renamed DARPABB 50Kbps Hosts: 23On the same networkProtocol:NCPHosts on the same network

1973/74

Development began on TCP/IP. First use of the Term Internet By V. CERFBB 50Kbps Hosts: 23+

1976

Dr. Metcalf DevelopedEthernetBackbones: 50Kbps ARPANET, plus satellite and radio connections - Hosts: 111+TCP/IP Experiments

USENETBased on UUCP developed by ATTBITnet by IBM: first store and forward networkApplication: e-mail and list serveBB: same as in 1976

1979

1981

NSF created CSNet for Connecting InstitutionsCSNET and ARPAnet Connectivity proposedBy Cerf. Backbones: 50Kbps ARPANET, 56Kbps CSNET, plus satellite/ radio Hosts: 213

1983

IAB createdIst Jan: TCP/IPHosts: 562

1984

ARPAnet divided Milnet andARPAnetCSNET managed by MCI, and called NSFNetNSFnet backboneWill use T-1Hosts: 1024

1986

IETF createdTo coordinateThe development by various contractorsHosts: 2308


A Brief summary of Internet • 1986 to 1991: Internet Hosts and back bone speeds continued to grow• 1992: Tim Berners-Lee and CERN in Geneva implements a hypertext system to provide efficient

information access to the members of the international high-energy physics community. – Backbones: 56Kbps CSNET, 1.544Mbps (T1) NSFNET, plus satellite and radio connections -

Hosts: 313,000• 1993:InterNIC created by NSF to provide specific Internet services: directory and database services

(by AT&T), registration services (by Network Solutions Inc.), and information services (by General Atomics/CERFnet).Marc Andreessen and NCSA and the University of Illinois develops a graphical user interface to the WWW, called "Mosaic for X".– Backbones: 45Mbps (T3) NSFNET, private interconnected backbones consisting mainly of

56Kbps, 1.544Mbps, and 45Mpbs lines, plus satellite and radio connections - Hosts: 2,056,000• 1994: Pizza Hut offers pizza ordering on its Web page Hosts: 3,864,000• 1995: The National Science Foundation announced that as of April 30, 1995 it would no longer

allow direct access to the NSF backbone. The National Science Foundation contracted with four companies that would be providers of access to the NSF backbone (Merit). These companies would then sell connections to groups, organizations, and companies.– BB speed from 56 kbps to 155 Mbps– Hosts: 6,642,000

• 1996: Most Internet traffic is carried by backbones of independent ISPs, including MCI, AT&T, Sprint, UUNet, BBN planet, ANS, and more– Hosts: over 15,000,000, and growing rapidly

• 1996 to 2006: explosive growth, e-commerce, e-gov, e-verything and all countries

• Lack of address space62Vikas Singh, CSIS Dept. BITS Pilani

Documents

EEE 582 Telecom Network management Introduction Instructors: Vikas Singh