SNMP for Diagnostics and Troubleshooting Network Problems - Research Paper Example

Advanced Communication Technologies A SNMP for diagnostics and troubleshooting network problems Abdulla Al Doseri 77108741 In order to manage, diagnose, and to troubleshoot network issues using SNMP protocols, this study involved the SNMP analysis program, the OpenNMS to carry out diagnosis and troubleshooting primary experiment. Data collection was carried out through the use of a laptop computer from which screenshots of results and analysis outputs were collected. By considering the role played by SNMP agents, Managed devices, SNMP Manager, and MIB. The results from observation of executing of commands showed that files that do not have a proper set of properties such as extension, descriptive properties, and those out of an event’s limitation standard return error messages blacking the operations from continuing further. Additionally, it was observed that created MIB sets can be added to a data collection group as an alternative protocol of enhancing performance of the network in terms of signal strength and quality. Table of Contents INTRODUCTION Many are instances when communication networks are faced with various problems among them being performance lagging, insecurity, and possible loss of connectivity among devices. In this case, communication amongst different devices depends highly on the connectivity, speed, and quality signal. In this case, it is a major concern that various networks are used primarily for commercial purposes such as the data service providers who all users data packets for accessing internet. On the other hand, telecommunication companies are on the increase with devices claiming to have high end connectivity capabilities. On the other hand, as a marketing strategy, telecommunications companies promise their customers high speeds and strong signals in order to attract them to their companies. However, how can the devices, the signals, and the data allowance be tested for authenticity? This activity can be monitored and analyzed through the use of SNMP properties as well as troubleshooting areas within the users reach (Borek, et.al. 2004). While information transfer through networks depends on speed to save time, it also depends on quality to ensure the receiver or the purpose it served without flaws such as poor decoding of the information. However, while the transfer of information will depend on signal quality and network stability, five areas are of concern to ensure that communication is flawless. The user or the consumer of the information represents the first element in the communication setting. The channel of transfer as well as the servers that store or process the data represent the second and the third elements respectively. The fourth and fifth elements include the network itself as well as the sources of the information that is fed into the network. While these areas complete the virtual communication entity, two areas affect performance, stability, and quality of signals handled and sent through the network. These areas include the data channels transmitting information from a server to the end user and vice versa while on the other hand, the server and the source of information within the network present the security issue to the network. This report features the steps and strategies used in diagnosis of problems and troubleshooting of network problems using SNMP in OpenNMS. LITERATURE REVIEW SNMP Manager The Prime responsibility of SNMP manager is for polling network devices which belong to the same network and also to fix the value of concrete variables in MIB for the SNMP agents employed in it (Pentland, 1995). Observing of polling agents can prepare to initiate automatically or by manual startup and this still does not terminate the managed devices from responding to all polls. The SNMP agents have some manager queries (O’Neill, Castellani, and Tolmie, 2005) Managed Devices A managed device for the SNMP agent has the responsibility to monitor and manage the network on which SNMP agent is stored for management. Managed devices collect and store management, data and make this data available to the Network Managing System (NMS) using SNMP (Farrel et al., 2009). SNMP Agent The SNMP agent informs the SNMP manager with the help of Tracks. Managed devices, for example, workstations and other network devices SNMP agents, are provided with the means of sending notifications called SNMP track when they perceive the issues. For instance, when one or more client pre-defined limits are surpassed. In the event of receiving these notifications, the SNMP manager can be set to respond by executing one or more activities, including administration warning, event logging, system shutdown and so forth. The SNMP Agent also acts as a proxy for devices that are not SNMP managed (Farrel, 2009). Management Information Base (MIB) Each SNMP agent keeps an up to date database representing the managed device statistics. The database is used by the SNMP manager to request an agent for particular data and further interprets the data as required by the Network Management System (NMS. This regularly accessed database between the Agent and the Manager is called the MIB. Typically, these MIB contains a standard set of facts and control values characterized for hardware resources on a network. SNMP likewise permits the augmentation of these standard values distinctive to a specific agent through the utilization of private MIBs. Explicitly put, MIB documents are a series of inquiries that an ‘SNMP’ Manager goes through with the agent. These agents gather this information and store it as characterized in the MIB as OIDs (Farrel, 2009). SNMP Configurations and Uses SNMP is a standard for the management of devices over an Internet Protocol Networks. However, while networking is the primary use of the SNMP in the measurement and testing of signal strength and quality, the SNMP protocol also monitor hardware and software within the corporate marketplace (ManageEngine, 2015) The protocol is made up of three components names SNMP Manager, Agent, and Managed Device. The application of the SNMP Manager is to monitor solutions. In the corporate world, the manufacturing industry, as well as in the construction industry, solutions are part of decisions and challenges faced. In this case, whether a company seeks to change manufacturing protocols, software coding approaches, or implementation of total quality management systems; the SNMP Manager provides clients or change implementers with information regarding the applicability of solutions, magnitude of effects, and compatibility with corresponding changes in other areas (Hsiao, Chen, Sun, and Chen, 2013; Lovy, et al. 2006). Secondly, the SNMP Agent is responsible for the collection of management information. Management information within a network can be envisioned from two perspectives. Management information can be monitored or implemented. For the implementing entity, management information acts as life log (where information regarding changes over a period of time or changes happening within the active existence of an entity). From the monitoring entity, management information can be used to fix bugs, problems, and challenges as the information is stored upon every implementation stage. With reference to issues such network failure over an IP platform such as a data modem, the SNMP Agent (most communication devices that use IP protocols to communicate act as Agents as management information is collected in each) can be used to collect the log changes’ information while at the same time providing reference to conflicting areas that may prevent a task from executing as expected (Harrington, 2002). Lastly, the SNMP Managed Device component entails the devices that registers as a network device any type of device with the capability of connecting to an IP or a SNMP Agent. Managed Device is a component of the SNMP in that it involves the client side devices which make use of the IP dependent communication devices. In this case, the assessment of signal strength, quality, and the network performance in general can be performed through the use of a user client with access to SNMP components such as the OpenNMS. OpenNMS provides access to the IP protocols as well as the SNMP components. In this report, a lab experiment involving the use of OpenNMS is reported based on the requirements of a computer system as well as the access and reconfiguration of SNMP events and groups’ properties to enhance or interfere with SNMP performance metrics (ZOSCommserver, 2013). SNMP is made up of OIDs and MIBs which are components identified as object Identifier, and Management Information Base respectively. The role and function of the OIDs is to provide information about the manufacturer and it is defined in the MIBs. It is also scalar (non-directional) and unique since it can also be presented in tabular form or list of dotted integers. MIB on the other hand is a collection of OIDs and provides definitions of the OIDs (Veinott, Olson, Olson and Fu, 1999). . While devices with IP and SNMP protocols are classified as SNMP Agent, the SNMP protocol function in devices such as computers connected to a network, connected mobile devices, as well as other products is not accessible be default. In order to enable SNMP in a computing platform such as laptop or a desktop computer running Windows 7 or later, the control panel and the programs and features function facilitate the operation. While no particular program handles SNMP in terms of starting or stopping, the add/remove function in Windows 7 or later enables a user to turn SNMP on and off. However, since the above-mentioned approach is not efficient in terms of conserving time, user clients such as Observer, OpenNMS and MNS Browser are among alternatives that can be used to access, monitor, configure, add, or remove SNMP features or components (MacFaden, Partain, & Tackabury, 2013). Network Monitoring Network monitoring is an important component of managing a network. Network monitoring can be proficient by having several instruments that can either be a part of your NMS or a part of the separate service program. Network monitoring tools are applied to study the structure and characteristics of the network and, to have a record of its configured network. The purpose of this monitoring is to analyze the role of device resources, network performance as well as a network outage. Network monitoring tools can monitor all the important factors of the network. They achieve cross-device analysis of cumulative multiple network devices into a single user interface (Stoll, Tashman, Edwards, and Spafford, 2008). Network discovery What and why all these devices are applied in a network? If you are well known and well aware of all the devices are and their proper working that makes up all your network and you can say “Knowing what is passing on inside your network: is only useful in this prospect. If a trouble occurred on the network because of a wrong and not proper fitted device, then it cannot be articulated that it’s an easy task to diagnose the issue. Following this information, it can be pointed that network discovery tools are used to scan a network for known devices within the network. The network discovers tools log the location and it’s believed device type and can, and then report the information to the management (Farrel, 2009). Attack identification and simulation If changes occurred in a network’s functionality due to some external elements will be improvised for fending off that factory once it happens it’s not guaranteed that the management would know about it. Attack credentials and simulation tools enable the administrator to recognize and categorize when typical network attacks occur, such include broadcast storms, replay attacks, cache poisoning, and thus alone. Attack documentation tools such as network incursion security systems and network intrusion detection schemes can be complicated to set up and be able to due to the dominance of false positives and false negatives such systems can create (Luff, Heath, Hindmarsh, & Oyama, 2003) SNMP tracking SNMP is an attractive and well-received protocol working for network management. SNMP is used for compiling information and configuring different devices which are used in the network, such as printers, hosts, switches, hubs and routers on an Internet Protocol (IP) network. Microsoft Windows Server 2003 that is the main who provides SNMP agent software, which can further communicate with third-party SNMP management program to monitor the prestige of succeeded devices and their application as well (Griswold, 2006). If we communicated about SNMP and SNMP tracks, then SNMP tracking tools have a different use than those in your NMS. SNMP Track can perform two tasks first is to receive, analyze and display low-level information from the SNMP enabled devices that can help in troubleshooting and the second task is to analysis the NMS outside. SNMP tracks are editing tools that are applied to the editing of existing templates to modify NMS response when SNMP tracks take place (Shields, 2007). SNMP Monitoring SNMP monitoring responsibility is to collect performance information from network devices like bridges, routers, and hubs etc., which are being added to the standard statistical results, in parliamentary procedure to identify network anomalies and hold ups. Availability of SNMP monitoring depends on the monitored device. The duty of the router is to provide the counters of all packets, speed, and their messages count as well as the error rates, etc. On the other side in some applications the SNMP connector has the responsibility to count connection size, their throughput as well as memory heap size and a lot more. This screenshot of SNMP Monitor picker shows how to create SNMP monitors by specifying an OID or loading an MIB (Poole, Chetty, and Edwards, 2008; Shehan, and Edwards, 2007). METHODOLOGY Equipment/Requirements In order to use SNMP to diagnose and troubleshoot problems associated with network communications such as over an IP address, a computer laptop with internal RAM of 3 GM and processor speeds of 1.6 for each core or a dual core and internal memory of 500GB were among the primary components needed for the experiment. A network modem or a smartphone with tethering capability was used instead of a wired connection. Non-physical tools required include OpenNMS computer program version 16. In addition, Java runtime JDK version 9.4, .Net Framework 3.5 and 4.0, and C++ were required system plugins that would enable the installation of the OpenNMS as well as ensuring that commands and tasks execute flawlessly. Last but not least, power access to power the computer system and internet browser such as Explorer version 8 or later were required enablers to ensure that the experiment can be carried out in a real-life situation. Procedure The computer system and a Wi-Fi hotspot enabled phone were powered on while the computer Wi-Fi accessibility function was switched on. On the other hand, the hotspot enabled smartphone (phone) had the hotspot function enabled to provide Wi-Fi access to the computer. After installation of the browser (in this case Google Chrome), the computer was connected to the Wi-Fi upon which the browser was used to download all software requirements listed earlier. From the run command, opennms. bat was a function entered to start the SNMP protocol as well as configure OpenNMS. The link from the directory in which OpenNMS was posted on the address bar on the browser so that it can provide access to the SNMP components. This approach results in a webpage like access to the system components upon which the password, admin, and the username, admin, were used to provide authentication that the operation had administrator privileges. The screenshots that follow showcase the different approached used in the operation as they relate to standard diagnosis and troubleshooting approaches when using OpenNMS to configure SNMP. The screenshots do not show a tutorial but rather present the steps as well as the considerations that were performed during the experiment. As a disclaimer, the steps herein portrayed as well as the procedures are not intended for commercial use or academic tutoring as the specificity of equipment used as well as the versions of software used do change gradually. Additionally, the connectivity devices used are not configured to show specific processes such as speed of connection from an idle state to a browsing state for the computer as well as variations in heat and signal strength of the GSM supported smartphone. OUTPUT ANALYSIS AND DISCUSSION Screenshot 1: SNMP Initiation In the web-supported version 16 of OpenNMS the procedure of mounting new command lines is based on the number or predefined or existing MIB files. As earlier pointed out, the MIB is a collection of OIDs and therefore stores information under the Manager component of the SNMP. On the other hand, in order to showcase whether an MIB file is supported by the compiling feature of the OpenNMS in the assessment of SNMP, the upload MIB function on the application window enabled the user to upload any MIB file that may have been complied before or one that pre-exists within the system. In order to access the above window portrayed as a screenshot required the user to configure the application under the admin tab from which the databases for MIB are created. Under the SNMP MIB Compiler window link on the home screen takes the user to the above window. From the window, it is shown that already compiled MIB and text format files are shown under the compiled tab. However, in order to test whether any of the compiled files, current or preexisting, is executable; the upload MIB tab allows the selection of a file from a directory. The default directory for MIB files from the operation is registered under the primary folder where the OpenNMS database is created, in a folder named shared. Although this folder was observed to change from one user to another, a search on the ‘My Computer’ folder specifying the file extension provided an easier approach to accessing the target files. Screenshot 2: MIB Compiling From screenshot 1, screenshot 2 shows the folder in which the complied MIB files are or can be found within a default settings’ configuration. In this case, since the observation was made that the directory folder changes from one system to another based on installation, one method of identifying whether the file was the target file included the extension .mib to suggest that it was a management information base file. After identifying the parent folder containing the target file through the dialog window shown in screenshot 2, the open button returned the user to the original OpenNMS window where a reference log registered showing the path that open file can be traced with. Upon opening, the file was listed under the pending tab on the bottom left of the window. At this stage, there are three options observed which entrained edit, delete, compile. The dropdown menu showing edit, delete, and compile provides room for a user to configure the file in terms of properties and other details, deleting the file from the pending list, and checking whether the file is compatible by executing the command (Tolmie, Crabtree, Rodden, Greenhalgh, and Benford, 2007). Screenshot 3: MIB Compilation reference log The above screenshot shows the reference log for changes taking place within the task. The reference log, however, does not only show whether an MIB file is executable, it also shows that that the file did or did not result to an error or it does not resemble an existing complied file. As earlier noted that after the location of a MIB file, the file is moved to the pending list, a contrary outcome after compilation takes the complied file to the compiled list. However, when executing this procedure, two observation are made relating to the diagnosis and troubleshooting of network systems using the OpenNMS program. Firstly, any MIB file or any file registered under the pending list may run or block the operation from moving any further. This result is anticipated under the condition that the uploaded file is not an MIB file and does not contain any valid OIDs’ definitions. Thus, files with file extensions such as .txt, .doc, or another other besides .mib or .xls block the operation. The resulting errors, as well as successful executions are registered under the reference log. In the current model, errors were rectified in preliminary tests such that the reference log during the actual experiment indicates an error free operation based in right selection of procedures. Secondly, it is observed that the compilation on any OID may incorporate bugs as well as input errors. Based on the source code of the information comprised in the MIB, the edit function enables parts of the code to be changed by either omission, commission, or altering of the codes. In this case, if the error message us shown, the SNMP components associated with the handling of an MIB containing OIDs, are regarded as faulty or containing an error. Based in this approach, the error message in this stage shows signs of system or network problems. Additionally, since the primary purpose of running the operation is to diagnose the system of network configurations, the error message is a clear indication of the need to troubleshoot the systems. Screenshot 4: Events Created The movement of the MIB file, IF-MIB, from the pending list to the compiled list shows that the file is ready for unpacking or it is compatible with the system and/or SNMP configurations. From the compiled list, two options are at disposal. These options include the configuration or the assessment of events and SNMP collection data. The events tab redirected to the list of events created when compilation was done. By the placement of the computer cursor and clicking on either of the listed events; the output in this case was the creation of two events, the various properties of the event can be edited. The editing function allows a user to change various components of the event such as the class of protocols, the number of events, and the type of protocols used among various other details. Based on the number of SNMP protocols one indents to create in order to fix any listed error or performance issue, the changing of event properties enables the configurations to either adapt a more stable form or a less performing state. The switching from single to mask in the editing window of the events enables the toggling between single event and multiple in the analysis operation of possible system and network configurations errors or issues (OpenNMS, 2012). Screenshot 5: Event Details When considering the editing of event information, the window on screenshot 5 confirms that the event has all required properties configured properly to a default setting or to a custom setting. However, to change the output, the editing feature provides the user with the ability to change the name of the event especially in cases where different operations are executed as part of a long-term systems’ and network diagnosis exercise. The extension detail labeled LinkDown is an equivalent of downlink where the performance metrics of incoming data packets are registered. The interval for SNMP diagnosis can be adjusted from the above editing window. However, while in the need to configure and resolve problems, the exercise itself have a structured challenge that can complicate the matter. When SNMP analysis is configured to run very regularly, this approach is capable of raising issues within the SNMP Agent and or/ the Managed Device. The frequency of checks increases the performance output of the device and consumes processor speed as well as the internal RAM’s capacity to handle the multiple commands and requested queued at any given stage of the operation. Screenshot 6: Event Detail Customization Whether the merit of running a SNMP analysis is to diagnose or to troubleshoot identified issues within the target system, the properties of every management information base’s list of events can be reconfigured from one state to another. For instance, screenshot 6 shows event details starting from element name (note, the details are handful and some do not appear within the screenshot window) and element value. These properties can be changed if diagnosis of the system show poor performing SNMP protocol. Screenshot 7: Event List In cases where the SNMP analysis involves numerous events per MIB or various MIBs containing limited or multiple events, the monitoring of all the details can be hectic. However, based on the use interface of the OpenNMS shows interactive tabs from which as user is able to move back and forth from a variety of functions. For instance, in order to open two events from a couple of events registered under LinkDown and LinkUP categories; when the event selection window closes, the events tab on the browser provides an easy access of all the available events. Based on the protocols changed under the editing window, a results window under the event’s tab shows the registration of the executed events. If the changes applied in the reconfiguration stages are not compatible with the even limitations, the event may fail or register as normal. The event registration ensures that the operation can refer to the processes as well as the specific changes made in any of the customizable fields of the event at hand. Screenshot 8: Group Collection In order to assess and diagnose any areas that may be problematic within a database, it is considered SNMP group collection is accessed by opting for the second option after compilation of the MIB file. In addition, the data collection group involved the properties of any respective compiled MIB. Within the browser when accessing the MIB file, IF-MIB, a number of options are provided in tabular form. Under every tab, the components of the collection group are shown and can be edited to change properties. Resource Types, MIB group, and System Definitions are three tabs providing editing options (Charles et.al. 2003). Screenshot 9: Group Properties’ Reference Log Upon the alteration of group properties, the reference log registered the modifications indicating the validity of the executed file (Twidale, and Ruhleder, 2004). However, since a file with a similar name was compiled before, screenshot 9 shows a WARN sign to indicate that the operation repeated or reinstated an existing file. In order to configure the events in the MIB file confirmed in the lasted reference log entry, the manage configuration function is used to locate the event as indicated in screenshot 11 below. Screenshot 10: Management of Event Configuration Based on what needed to be edited or restored by selecting the event configuration, the admin tab enables the use to return to the home screen from which the access of SNMP and Data Collections groups are assessed from. Since the entire period the exercise has been primarily focused on creating troubleshooting profile to enhance the network performance metrics, the compiled MIB, IF-MIB, is therefore added to the ‘includes list’ for the default SNMP collection group. Screenshot 11 and 12 show the user interface outputs as well as the destination of the IF-MIB data collection group. Screenshot 11: SNMP Collection Details Screenshot 12: Reconfiguration of SNMP Properties CONCLUSION For management, diagnosis, and to troubleshooting of network issues using SNMP protocols, this study involved the OpenNMS to use SNMP protocols in the primary experiment. By considering the role played by SNMP agents, Managed devices, SNMP Manager, and MIB, the results from observation of executing of commands drove to the conclusion that MIB files that do not have a proper set of properties such as extension, descriptive properties, and those outside an event’s limitation returned error messages blocking the analysis from moving forward. Additionally, the study confirms that MIB sets can be added to a data collection group as an alternative protocol to the enhancement of the network’s performance based on signal strength and quality. References Borek, M. et.al. (2004), “System and method for troubleshooting, maintaining and repairing network devices”, Application number US 10/620,349 Charles et.al. (2003). Network-based remote diagnostic facility. Application number US 09/435, 252, 2003 Farrel, A, (2009). Network Management Know It All. Elsevier Store. pp. 62-64.100-102 Griswold, E. (2006), “Problem determination method suitable for use when a filter blocks SNMP access to network components”, Application number US 10/214,542, 2006 Harrington, D. (2002). An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks. n.p Hsiao, W., Chen. Y., Sun. S., and Chen.M. (2013). A Cooperative Botnet Profiling and Detection in Virtualized Environment. IEEE Conference on Communications and Network Security (CNS). Available online from: http://www.zabbix.com/documentation/1.8/manual/auto-discovery Lovy, D., et.al. (2006). Method and apparatus for identifying problems in computer networks. Application number US 10/108,962, 2006 Luff, P., Heath, H., & Hindmarsh, K. & Oyama, K. (2003). Fractured Ecologies: Creating Environments for Collaboration. Human–Computer Interaction, vol. 18, pp. 51–84. MacFaden, D. Partain, J., & W. Tackabury, S. (2013). Configuring Networks and Devices with Simple Network Management Protocol (SNMP). n.p. ManageEngine. (2015). SNMP Operations and Troubleshooting SNMP. Accessed online on May 31, 2015 from https://www.youtube.com/watch?v=gVnSD-9Z5l8 O’Neill, J., Castellani, A., and Tolmie, P. (2005): Representations Can Be Good Enough. Springer: Paris, France. OpenNMS. (2012). OpenNMS User Interface for Events Configuration and SNMP Performance Metrics. Accessed online on May 31, 2015 from https://www.youtube.com/watch?v=mRf9dKX2vyQ Pentland, B. (1995). Read Me What It Says on Your Screen: The Interpretive Problem of Technical Service Work. Technology Studies, vol. 2(1), pp. 50–79. Poole, E., Chetty, E., and Edwards, W (2008). More Than Meets the Eye: Transforming the User Experience of Home Network Management. ACM: Cape Town, South Africa. Shehan, E. and Edwards, W (2007). Home Networking and HCI: What Hath God Wrought? In Proceedings of the ACM Conference on Human Factors in Computing Systems. San Jose, CA, USA, April 28–May 3, pp. 547–556. Stoll, J., Tashman, C., Edwards, W. and Spafford, K. (2008). Sesame: Informing User Security Decisions with System Visualization. ACM: Florence, Italy. Tolmie, P., Crabtree, A., Rodden, T., Greenhalgh, C. and Benford, S. (2007). Making the Home Network at Home: Digital Housekeeping. Springer: Limerick, Ireland. Twidale, M. and Ruhleder, K. (2004). Where am I and Who am I? Issues in Collaborative Technical Help? ACM: Chicago, IL, USA, pp. 378–387. Veinott, E.S., Olson, G., Olson and Fu, X. (1999). Video Helps Remote Work: Speakers Who Need to Negotiate Common Ground Benefit from Seeing Each Other. ACM: Pittsburgh, PA, USA, pp. 302–309. ZOSCommserver. (2013). NMP Concepts and Principles. Accessed online on May 31, 2015 from https://www.youtube.com/watch?v=RD8hnhGCFcY Read More