DOC PREVIEW
Berkeley COMPSCI 252 - ECHO

This preview shows page 1-2-24-25 out of 25 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 25 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 25 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 25 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 25 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 25 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

ECHOChallengeGoalOverviewPowerPoint PresentationCentralized Control UnitInformation CollectionEchoMe DaemonRouter Connectivity Discovery by SNMPSystem InformationNetwork InformationInformation AnalysisParsing EngineIFACE TablesSlide 15Individual Node AnalysisCollaborative AnalysisInterface to View AnalysisActionSecuritySystem Stat TableTranscripts for SNMP Router DiscoveryPartial Router Connectivity on Millennium Discovered by SNMPConclusionFuture WorkECHOA System Monitoring and Management ToolYitao Duan and Dawey HuangChallengeHow can we manage all these machines?GoalAimed at networked system managementBetter tools for–Discovering system states –Enhancing system availability–Monitoring network and system statistics–Error detection and correction–Fault tolerance for specific network applications (such as web server)OverviewDistributed agents gathering informationCentralized Control Unit (CCU) monitors and analyzes data. Takes control action if neededScript language for automatic decision making Web browser user interfaceSNMP ToolEchoMe DaemonCentralized Control UnitInformation collection–Machine information–Network informationInformation analysis–Individual Machine analysis–Collaborative network analysisAction–System modification–Network routingInformation CollectionTwo approaches investigated–EchoMe Daemons running on hosts and reporting system information to server–SNMP to discover router connectivity and statesDaemon mostly for collecting local information. Much more detailedSNMP for network connectivityEchoMe Daemon1. Automatically discover a node (node reporting stage)–EchoMe Daemon start up as machine boot–Send up OS type/machine info to CCU–Register a session in CCU2. CCU sends to node a monitor program base on node’s OS/Machine type and execute it on the node.3. Monitor program send up information packet periodically to CCU.Router Connectivity Discovery by SNMPRouters implemented SNMPProgram can run on any host within MillenniumGiven a router (can get from local host’s gateway information), query its ipRouteTableTraverse all its neighboring routers, performing the same queryRecursion stops at specified distanceSystem InformationNumber and speed of the CPUs Total physical and swap memory Installed System Clock Uptime Kernel Version Percent CPU user, nice, system and idle One, five and fifteen minute load averages Number of running processes and total number of processes Amount of free, shared, buffered, cached and swap memoryNetwork InformationNetwork Interfaces –/proc/dev or CTL_NET/AF_LINK–SNMP: interface.ifTableARP cache – direct neighbors–/proc/arp or RTF_LLINFO–SNMP: ip.ipNetToMediaTableRoute Table–/proc/route or NET_RT_DUMP–SNMP: ip.ipRouteTableInformation AnalysisCCU  a relational databaseFront end, parsing engineIndividual Node AnalysisCollaborative AnalysisParsing EngineIPACKET is in standard XML formatIPACKET use incremental update, new packet specifies differences from previous packet.Parsing Engine parses the IPACKET into objects and does the insertion to iface accordingly.<ID ??> <DATATYPE>DATA </DATATYPE></ID>IFACE TablesThe client node register an unique nodeid in iface_node_tableIt starts a session for reporting information to CCUEach time, client node reports information by sending up an information packet. (ipacket)CCU process this packet, create an unique statement id from iface_index_table and parse information into each iface_?DATA_table.Individual Node AnalysisClean up iface_?data_table by transferring and categorizing data into each nodes’ own data table.A background process runs on CCU.Examples:–Network statistic overtime table–Network route change reporting–Network usage of nodes. (packets, tcp/udp connection counts)–Node’s system state overtime table–Node’s configuration change tableCollaborative AnalysisGroup up specify information in the iface_?data_tables and ninfo_?data_tables to generate special tables for user viewing/analysis.Examples–Network connectivity graph–Network graph between two node or route–Network snapshot table–All nodes’ current network statistic table–All nodes’ current state tableInterface to View AnalysisWeb interface–Viewable under web browserWeb session–Display analysis–Take action input from userJava Servlet + JSP–Security control–Data Objects map with tables in collaborative analysisActionDaemon capable of receiving and executing binary programs from CCUCommand module issues command in response to certain events–Add pseudo interface to a host–Reroute a host–Initialize new program–Etc.SecurityOpenSSL encryption EchoMe Daemon Run as nobodySystem Modification Program needs to do suexec (ROOT PASSWORD requires)System Stat TableTranscripts for SNMP Router Discovery……Iterating neighbors of 169.229.51.202 ....IP address: 169.229.51.161(A9E533A1)IP address: 169.229.51.233(A9E533E9)IP address: 169.229.51.165(A9E533A5)IP address: 169.229.51.167(A9E533A7)IP address: 169.229.51.168(A9E533A8)IP address: 169.229.50.33(A9E53221)IP address: 169.229.50.129(A9E53281)IP address: 169.229.51.166(A9E533A6)IP address: 169.229.51.169(A9E533A9)IP address: 169.229.51.234(A9E533EA)In getIPRouteTable. nHops = 8Setting target to 169.229.51.234……Partial Router Connectivity on Millennium Discovered by SNMP169.229.48.1169.229.51.226169.229.51.161169.229.51.165128.32.44.10128.32.44.1169.229.51.169169.229.51.233169.229.51.167169.229.51.133169.229.51.198ConclusionInformation collection methods feasibleAutomatic discoveryComprehensive and accurate information about systemNeeds user feedbackFuture WorkMore (or less) features based on user feedbackUser interfaceMore on information analysis and decision makingFully deploy on


View Full Document

Berkeley COMPSCI 252 - ECHO

Documents in this Course
Quiz

Quiz

9 pages

Caches I

Caches I

46 pages

Lecture 6

Lecture 6

36 pages

Lecture 9

Lecture 9

52 pages

Figures

Figures

26 pages

Midterm

Midterm

15 pages

Midterm

Midterm

14 pages

Midterm I

Midterm I

15 pages

Quiz  1

Quiz 1

12 pages

Load more
Download ECHO
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view ECHO and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view ECHO 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?