Introduction to Networking Monitoring and Management
اسلاید 1: Introduction to Networking Monitoring and ManagementAfNOG 2010 Network Monitoring and Management Tutorial
اسلاید 2: Part I: OverviewCore concepts presented:What is network monitoringWhat is network managementGetting startedWhy network managementAttack detectionConsolidating the dataThe big picture
اسلاید 3: What is network monitoring?Anyone have some ideas?Monitoring an active communications network in order to diagnose problems and gather statistics for administration and fine tuning.The term network monitoring describes the use of a system that constantly monitors a computer network for slow or failing components and that notifies the network administrator in case of outages via email, pager or other alarms. It is a subset of the functions involved in network management.
اسلاید 4: What is network management? Refers to the broad subject of managing computer networks. There exists a wide variety of software and hardware products that help network system administrators manage a network. Network management covers a wide area, including: - Security: Ensuring that the network is protected from unauthorized users. - Performance: Eliminating bottlenecks in the network. - Reliability: Making sure the network is available to users and responding to hardware and software malfunctions.
اسلاید 5: System & Service monitoringReachability, availabilityResource measurement/monitoringCapacity planning, availabilityPerformance monitoring (RTT, throughput)Statistics & Accounting/MeteringFault Management (Intrusion Detection)Fault detection, troubleshooting, and trackingTicketing systems, help deskChange management and configuration monitoringWhat is network management?
اسلاید 6: Make sure that the network is up and running. Thus, we need to monitor it:Deliver projected SLAs (Service Level Agreements)Depends on policyWhat does your management expect?What do your users expect?What do your customers expect?What does the rest of the Internet expect?Is 24x7 good enough?Theres no such thing as 100% uptime (as we’ll see) Getting started
اسلاید 7: What does it take to deliver 99.9 % uptime?30.5 x 24 = 762 hours a month(762 – (762 x .999)) x 60 = 45 minutes only 45 minutes of downtime a month!Need to shutdown 1 hour / week?(762 - 4) / 762 x 100 = 99.4 %Remember to take planned maintenance into account in your calculations, and inform your users/customers if they are included/excluded in the SLAHow is availability measured?In the core? End-to-end? From the Internet?Getting started: “Uptime”
اسلاید 8: Getting started: BaseliningWhat is normal for your network?If you’ve never measured or monitored your network you need to know things like:Load on linksJitter between endpointsPercent usage of resourcesAmount of “noise”:Network scansDropped dataReported errors or failures
اسلاید 9: Know when to upgradeIs your bandwidth usage too high?Where is your traffic going?Do you need to get a faster line, or more providers?Is the equipment too old?Keep an audit trace of changesRecord all changesMakes it easier to find cause of problems due to upgrades and configuration changesKeep a history of your network operationsUsing a ticket system let you keep a history of events.Allows you to defend yourself and verify what happenedWhy network management?
اسلاید 10: AccountingTrack usage of resourcesBill customers according to usageKnow when you have problemsStay ahead of your users! Makes you look good.Monitoring software can generate tickets and auto- matically notify staff of issues.TrendsAll of this information can be used to view trends across your network.This is part of baselining, capacity planning and attack detection.Why network management?
اسلاید 11: Trends and automation allow you to know when you are under attack.The tools in use can help you to mitigate attacks:Flows across network interfacesLoad on specific servers and/or servicesMultiple service failuresAttack Detection
اسلاید 12: Consolidating the dataThe Network Operations Center (NOC)“Where it all happens”Coordination of tasksStatus of network and servicesFielding of network-related incidents and complaintsWhere the tools reside (”NOC server”)Documentation including:Network diagramsdatabase/flat file of each port on each switchNetwork descriptionMuch more as youll see a bit later.
اسلاید 13: - Monitoring- Data collection- Accounting- Capacity planning- Availability (SLAs)- Trends- Detect problems- Change control & monitoring- Improvements- Upgrades- Fix problems- User complaints- Requests- NOC Tools- Ticket systemTicketTicketTicketTicketTicketNotificationsThe big picture
اسلاید 14: PerformanceCricketIFPFMflowcmrtgnetflowNfSenntoppmacctrrdtoolSmokePingSNMP/Perl/pingTicketingRT, Trac, RedmineNet ManagementBig BrotherBig SisterCactiHypericMuninNagios*NetdiscoNetdot OpenNMSSysmonZabbix Change MgmtMercurialRancid (routers)RCSSubversionSecurity/NIDSNessusOSSECPreludeSamhainSNORTUntangleA few Open Source solutions…
اسلاید 15: Questions??
اسلاید 16: Part II: Details Some details on the core concepts:Network documentationDiagnostic toolsMonitoring toolsPerformance toolsActive and passive toolsSNMPTicket systemsConfiguration and change management
اسلاید 17: Maybe you’ve asked, “How do you keep track of it all?”...Document, document, document…Documentation
اسلاید 18: Basics, such as documenting your switches...What is each port connected to?Can be simple text file with one line for every port in a switch:health-switch1, port 1, Room 29 – Director’s officehealth-switch1, port 2, Room 43 – Receptionisthealth-switch1, port 3, Room 100 – Classroomhealth-switch1, port 4, Room 105 – Professors Office…..health-switch1, port 25, uplink to health-backboneThis information might be available to your network staff, help desk staff, via a wiki, software interface, etc.Remember to label your ports!Documentation
اسلاید 19: Nice…Documentation: Labeling
اسلاید 20: Network DocumentationMore automation might be needed. An automated network documentation system is something to consider.You can write local scripts to do this.You can consider some automated documentation systems.You’ll probably end up doing both.
اسلاید 21: Automated SystemsThere are quite a few automated network documentation systems. Each tends to do something different: IPplan: http://iptrack.sourceforge.net/Netdisco: http://netdisco.org/Netdot: https://netdot.uoregon.edu/
اسلاید 22: IPplan: From the IPplan web page:“IPplan is a free (GPL), web based, multilingual, TCP IP address management (IPAM) software and tracking tool written in php 4, simplifying the administration of your IP address space. IPplan goes beyond TCPIP address management including DNS administration, configuration file management, circuit management (customizable via templates) and storing of hardware information (customizable via templates).”Lots of screenshots: http://iptrack.sourceforge.net/doku.php?id=screenshots
اسلاید 23: Netdisco: Project launched 2003. Version 1.0 released October 2009.Some popular uses of Netdisco:Locate a machine on the network by MAC or IP and show the switch port it lives at. Turn Off a switch port while leaving an audit trail. Admins log why a port was shut down. Inventory your network hardware by model, vendor, switch-card, firmware and operating system. Report on IP address and switch port usage: historical and current. Pretty pictures of your network.
اسلاید 24: Netdot: Includes functionality of IPplan and Netdisco and more. Core functionality includes:Device discovery via SNMP Layer2 topology discovery and graphs, using: CDP/LLDP Spanning Tree Protocol Switch forwarding tables Router point-to-point subnets IPv4 and IPv6 address space management (IPAM) Address space visualization DNS/DHCP config management IP and MAC address tracking Continued
اسلاید 25: Netdot: Functionality continued:Cable plant (sites, fiber, copper, closets, circuits...) Contacts (departments, providers, vendors, etc.) Export scripts for various tools (Nagios, Sysmon, RANCID, Cacti, etc)I.E., how we could automate node creation in Cacti!Multi-level user access: Admin, Operator, User It draws pretty pictures of your network
اسلاید 26: Documentation: Diagrams
اسلاید 27: Windows Diagramming SoftwareVisio: http://office.microsoft.com/en-us/visio/FX100487861033.aspx Ezdraw: http://www.edrawsoft.com/Open Source Diagramming SoftwareDia: http://live.gnome.org/DiaCisco reference icons: http://www.cisco.com/web/about/ac50/ac47/2.htmlNagios Exchange: http://www.nagiosexchange.org/Diagramming Software
اسلاید 28: Three kinds of tools Diagnostic tools – used to test connectivity, ascertain that a location is reachable, or a device is up – usually active tools Monitoring tools – tools running in the background (”daemons” or services), which collect events, but can also initiate their own probes (using diagnostic tools), and recording the output, in a scheduled fashion. Performance tools – tell us how our network is handling traffic flow.Network monitoring systems & tools
اسلاید 29: Performance ToolsKey is to look at each router interface (probably don’t need to look at switch ports).Two common tools:Netflow/NfSen:http://nfsen.sourceforge.net/MRTG: http://oss.oetiker.ch/mrtg/MRTG = “Multi Router Traffic Grapher”Network monitoring systems & tools
اسلاید 30: Active toolsPing – test connectivity to a hostTraceroute – show path to a hostMTR – combination of ping + tracerouteSNMP collectors (polling)Passive toolslog monitoring, SNMP trap receivers, NetFlowAutomated toolsSmokePing – record and graph latency to a set of hosts, using ICMP (Ping) or other protocolsMRTG/RRD – record and graph bandwidth usage on a switch port or network link, at regular intervalsNetwork monitoring systems & tools
اسلاید 31: Network & Service Monitoring toolsNagios – server and service monitorCan monitor pretty much anythingHTTP, SMTP, DNS, Disk space, CPU usage, ...Easy to write new plugins (extensions)Basic scripting skills are required to develop simple monitoring jobs – Perl, Shell scripts, php, etc...Many good Open Source toolsZabbix, ZenOSS, Hyperic, OpenNMS ...Use them to monitor reachability and latency in your networkParent-child dependency mechanisms are very useful!Network monitoring systems & tools
اسلاید 32: Monitor your critical Network ServicesDNS/Web/EmailRadius/LDAP/SQLSSH to routersHow will you be notified?Dont forget log collection!Every network device (and UNIX and Windows servers as well) can report system events using syslogYou MUST collect and monitor your logs!Not doing so is one of the most common mistakes when doing network monitoringNetwork monitoring systems & tools
اسلاید 33: SNMP – Simple Network Management Protocol Industry standard, hundreds of tools exist to exploit itPresent on any decent network equipmentNetwork throughput, errors, CPU load, temperature, ...UNIX and Windows implement this as wellDisk space, running processes, ... SSH and telnetIt is also possible to use scripting to automate monitoring of hosts and servicesNetwork management protocols
اسلاید 34: Net SNMP tool sethttp://net-snmp.sourceforge.net/Very simple to build simple toolsOne that builds snapshots of which IP is used by which Ethernet addressAnother that builds shapshots of which Ethernet addresses exist on which port on which switch.Query remote RAID array for state.Query server, switches and routers for temperatures.Etc…SNMP tools
اسلاید 35: Traffic accounting and analysisWhat is your network used for, and how muchUseful for Quality of Service, detecting abuses, and billing (metering)Dedicated protocol: NetFlowIdentify traffic ”flows”: protocol, source, destination, bytesDifferent tools exist to process the informationFlowtools, flowcNFSenMany more: http://www.networkuptime.com/tools/netflow/Statistics and accounting tools
اسلاید 36: Is the problem transient?Overload, temporary resource shortageIs the problem permanent?Equipment failure, link downHow do you detect an error?Monitoring!Customer complaintsA ticket system is essentialOpen ticket to track an event (planned or failure)Define dispatch/escalation rulesWho handles the problem?Who gets it next if no one is available?Fault and problem management
اسلاید 37: Why are they important?Track all events, failures and issuesFocal point for helpdesk communicationUse it to track all communicationsBoth internal and externalEvents originating from the outside:customer complaintsEvents originating from the inside:System outages (direct or indirect)Planned maintenances or upgrades – Remember to notify your customers!Ticketing systems
اسلاید 38: Use ticket system to follow each case, including internal communication between techniciansEach case is assigned a case numberEach case goes through a similar life cycle:NewOpen...ResolvedClosedTicketing systems
اسلاید 39: Workflow: Ticket System Helpdesk Tech Eqpt ---------------------------------------------------------------- T T T T query | | | | from ---->| | | | customer |--- request --->| | | <- ack. -- | | | | | |<-- comm --> | | | | |- fix issue -> eqpt | |<- report fix -| | customer <-|<-- respond ----| | | | | | |Ticketing systems
اسلاید 40: rt (request tracker)Heavily used worldwide. A classic ticketing system that can be customized to your location.Somewhat difficult to install and configure.Handles large-scale operations.tracA hybrid system that includes a wiki and project management features.Ticketing system is not as robust as rt, but works well.Often used for ”trac”king group projects.redmineLike trac, but more robust. Harder to installTicketing systems: examples
اسلاید 41: These are systems that observe all of your network traffic and report when it sees specific kinds of problems, such as:hosts that are infected or are acting as spamming sources.A few tools:SNORT - a commonly used open source tool: http://www.snort.org/Prelude – Security Information Management System https://dev.prelude-technologies.com/Samhain – Centralized HIDS http://la-samhna.de/samhain/Nessus - scan for vulnerabilities: http://www.nessus.org/download/Network Intrusion Detection Systems (NIDS)
اسلاید 42: Record changes to equipment configuration using revision control (also for configuration files)Inventory management (equipment, IPs, interfaces)Use versioning controlAs simple as: ”cp named.conf named.conf.20070827-01”For plain configuration files:CVS, Subversion (SVN)MercurialFor routers:RANCIDConfiguration mgmt & monitoring
اسلاید 43: Traditionally, used for source code (programs)Works well for any text-based configuration filesAlso for binary files, but less easy to see differencesFor network equipment:RANCID (Automatic Cisco configuration retrieval and archiving, also for other equipment types)Built-in to Project Management Software like:TracRedmineAnd, many other wiki products. Excellent for documenting your network.Configuration mgmt & monitoring
اسلاید 44: - Monitoring- Data collection- Accounting- Capacity planning- Availability (SLAs)- Trends- Detect problems- Change control & monitoring- Improvements- Upgrades- Fix problems- User complaints- Requests- NOC Tools- Ticket systemTicketTicketTicketTicketTicketNotificationsThe big picture revisited
اسلاید 45: Questions?
نقد و بررسی ها
هیچ نظری برای این پاورپوینت نوشته نشده است.