EEE 582 Telecom Network management

1. EEE 582Telecom Network management Introduction Instructors: Vikas Singh

2. 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 Vikas Singh, CSIS Dept. BITS Pilani

3. 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 Vikas Singh, CSIS Dept. BITS Pilani

4. Course Plan Vikas Singh, CSIS Dept. BITS Pilani Contd…

5. Evaluation Scheme Vikas Singh, CSIS Dept. BITS Pilani

6. Chapter 1 Data Communications and NM Overview Vikas Singh, CSIS Dept. BITS Pilani

7. Question • What is a network? • What is Network Management? • Why do we need Network Management? • What is the goal of network management? Vikas Singh, CSIS Dept. BITS Pilani

8. Network Management What 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 Vikas Singh, CSIS Dept. BITS Pilani

9. 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 Vikas Singh, CSIS Dept. BITS Pilani

10. 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 Vikas Singh, CSIS Dept. BITS Pilani

11. Chapter 1 Outline • 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 Vikas Singh, CSIS Dept. BITS Pilani

12. Chapter 1 Telephone Network • 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 Vikas Singh, CSIS Dept. BITS Pilani

13. Telephone Network Model (1.1) • 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 Vikas Singh, CSIS Dept. BITS Pilani

14. 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) Vikas Singh, CSIS Dept. BITS Pilani

15. Information Transmission • May be transmitted as: • Circuit switched mode • Message switched mode • Packet switched mode Vikas Singh, CSIS Dept. BITS Pilani

16. 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 Vikas Singh, CSIS Dept. BITS Pilani

17. Data and Telecommunication Network (1.2) PSTN • 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 Vikas Singh, CSIS Dept. BITS Pilani

18. IBM SNA Architecture • 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 Vikas Singh, CSIS Dept. BITS Pilani

19. Vikas Singh, CSIS Dept. BITS Pilani

20. DCE with LAN (section 1.3) 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 ? Vikas Singh, CSIS Dept. BITS Pilani

21. LAN-WAN Network • Notes • 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 Vikas Singh, CSIS Dept. BITS Pilani

22. Client/Server Model Request Response • 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 ? Vikas Singh, CSIS Dept. BITS Pilani

23. Client/Server Examples Vikas Singh, CSIS Dept. BITS Pilani

24. 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 Vikas Singh, CSIS Dept. BITS Pilani

25. Internet Architecture Application Voice Over IP FTP SMTP HTTP SNMP Others TELNET Transport UDP TCP Network ARP & RARP IP ICMP Ethernet Link Level X.25 PPP PMPP Vikas Singh, CSIS Dept. BITS Pilani

26. Internet Protocol Layers ISO/OSI Layered Model for data communications TCP/IP Model for data communications APPLICATION APPLICATION FTP ,SMTP, Telnet, HTTP, SNMP PRESENTATION SESSION TCP: Transport TRANSPORT IP: Internet Protocol INTER NET IEEE 802 X.25 INTRA DATA LINK PHYSICAL HARDWARE TCP/IP AND OSI: Functional Positioning of Layers Vikas Singh, CSIS Dept. BITS Pilani

27. 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 Vikas Singh, CSIS Dept. BITS Pilani

28. Workstation Mail Server (Joe) Workstation LAN A LAN B Bridge / Bridge / Router Router Domain Name Bridge / Server Router LAN C Gateway Internet Gateway LAN X Bridge / Router Bridge / Bridge / Router Router LAN Z LAN Y Workstation PC (Sally) Mail Server Figure 1.9 Internet Configuration Internet Configuration Private TCP/IP Network Also called Intranet Private TCP/IP Network Also called Intranet Vikas Singh, CSIS Dept. BITS Pilani

29. Internet Configuration Asha’s Workstation Mail Server LAN A LAN B Intranet Domain name: bits-pilani.ac.in B/R B/R Domain Name server B/R LAN C Gateway1 Internet consists of multiple domains Internet Gateway LAN abc B/R Mail Server B/R LAN x Asha’s email: Asha@bits-pilani.ac.in Anand@dest.com Anand’s workstation Vikas Singh, CSIS Dept. BITS Pilani

30. 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 Vikas Singh, CSIS Dept. BITS Pilani

31. Autonomous SystemsInternet Routing Architecture Autonomous System A Stub AS Autonomous System B R R R R R R R R R R R R Autonomous System C Autonomous System D R R R R R R R R R R R R R Border Router: also called gateway router Multi-homed AS (Transit AS for AS B) R Interior Router Vikas Singh, CSIS Dept. BITS Pilani

32. 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? Vikas Singh, CSIS Dept. BITS Pilani

33. Communication Architecture • 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 Vikas Singh, CSIS Dept. BITS Pilani

34. OSI Reference Model • Importance of the knowledge of layer structure in NM Vikas Singh, CSIS Dept. BITS Pilani

35. OSI Layers and Services Vikas Singh, CSIS Dept. BITS Pilani

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

37. Gateway Communications to a Proprietary Subnet • cc:mail from a station in Novel IPX network to an Internet station with SMTP e-mail Vikas Singh, CSIS Dept. BITS Pilani 1-21

38. SNA, OSI, and Internet • 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 Vikas Singh, CSIS Dept. BITS Pilani 1-22

39. Application Protocols Internet user OSI user Telnet Virtual Terminal File TransferProtocol File Transfer Access & Mgmt Simple Mail Transfer Message-oriented Text Protocol Interchange Standard Simple Network Common ManagementManagement Protocol Information Protocol Vikas Singh, CSIS Dept. BITS Pilani

40. NM Case Histories • The case of the Footprint (topology) • Case of the crashing bridge Vikas Singh, CSIS Dept. BITS Pilani

41. Common Network Problems • Loss of connectivity • Duplicate IP address • (address management) • Intermittent problems • Network configuration issues • Non-problems • Performance problems Vikas Singh, CSIS Dept. BITS Pilani

42. 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” Vikas Singh, CSIS Dept. BITS Pilani

43. Network Management System Functionality • OAM&P • Operations • Administration • Maintenance • Provisioning Vikas Singh, CSIS Dept. BITS Pilani

44. Network Management Vikas Singh, CSIS Dept. BITS Pilani

45. NM Functional Flow Chart Vikas Singh, CSIS Dept. BITS Pilani 1-28

46. 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. Vikas Singh, CSIS Dept. BITS Pilani

47. Network Management architecture(functional) Common management messages The common management messages consist of management information data (such as the type, id, and status of managed objects..) Vendor A Vendor B 1. The common messages: management and information data Exchange of monitoring data 2. Management controls Vikas Singh, CSIS Dept. BITS Pilani

48. Application Services objects objects Management Protocol Vendor B Vendor A objects objects Transport Protocols Services and protocols Application services: management related applications, such as configuration management, fault management Management protocols are SNMP and CMIP - CMIP is complex and not used very much Vikas Singh, CSIS Dept. BITS Pilani

49. NM Components Same Domain NMS: Manages multiple network elements, via Network agents. Each Network element could have multiple objects. Note the Hierarchy Vikas Singh, CSIS Dept. BITS Pilani

50. Interoperability Domain A Domain B 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 • Message exchange between NMSs managing different domains Vikas Singh, CSIS Dept. BITS Pilani