Networking

Introduction

The major issue of administrator in big organization is hardware management. The work force of any organization includes hardware, if management of hardware not done properly then the work force may effect badly. Companies are investing lot of money on hardware management but they still not getting good results. Why? Because they do not automate it, if they automate it there will be less chances of error.

Inventory management is one of the main issues of mature industry. We also solve this problem by introducing auto registry. This system will register the workstation automatically as it plugged in to the network. If configuration of any hardware changes it will update it after the authentication of the administrator.

If the location of workstation is changed then administrator can update the system description, contact information etc. from server.

This report covers all the phases involved in the development of this software. Explaining each separately, chapter wise. Consists of 7 chapters, covering different aspects of the project.

Analysis and designing are considered the major phases in the development of any software. If not done properly, can result in a bad product and non conformance to requirements. Analysis and designing is given proper attention to avoid major bugs in later stages of development. Chapter 2 of this report highlights project planning done through data collection and various other techniques and designing steps for developing the software.

This is followed by chapter 3, which explains aims and objective followed by analysis phase in chapter 4. Another important area that is usually not paid attention to is feasibility analysis in terms of technical and operational feasibility has been covered in chapter 5.

Chapter 6 gives the task break up in implementing the software and explains each. Every software / product is incomplete with out thorough testing. Chapter 7 of this report explains the various important pieces of the software, which were tested, their expected and actual results. Conclusion and future work in the end terminates the report.

References in the end give the reader, a list of websites, books and people referred in completing this report / product. The report has been written in a form, which would help the reader of technical or non technical background in clearly understanding the software and also as a guide in further enhancing its features.

1.2 Background of Snmp

The background study that has been carried out for proper analysis of SNMP (Simple Network Management Protocol) is as follows.

1.2.1 SNMP Overview

The Simple Network Management Protocol (SNMP) was introduced in 1988 to meet the growing need for a standard for managing internet protocol (IP).SNMP provides its user with a "simple" set of operations that allows these devices to be managed remotely. Many kinds of devices support SNMP including routers, witches, servers, workstations, printers, modem racks and uninterruptible power supplies (UPSs). The way you can use SNMP range from the mundane to the exotic: it's fairly simple to use SNMP to monitor the health of your routers, switches and other pieces of network hardwares, but you can also use it to control your network devices and even send pages or take other automatic action if problem arise.

SNMP usually associated with managing routers, but it's important to understand that it can be used to manage many types of devices. While SNMP predecessor, the Simple Gateway Management Protocol (SGMP) was developed to manage Internet routers, Snmp can be used to manage UNIX systems, Windows systems, printers, modem racks, power supplies, and more. Any device running software that allows the retrieval of SNMP information can be managed. This includes not only physical devices but also software, such as web servers and databases1.

Another aspect of network management is network monitoring; that is, monitoring an entire network as opposed to individual routers, hosts, and other devices. Remote Network Monitoring (RMON) was developed to help us understand how the network itself is functioning, as well as how individual devices on the network are affecting the network as a whole. It can be used to monitor not only LAN traffic, but WAN interfaces as well.

1.2.2 Before and After SNMP

Let us say that you have a network of 100 machines running various operating systems. Several machines are file servers, a few others are print servers, another is running software that verifies credit card transactions (presumably from a web-based ordering system), and the rest are personal workstations. In the actual network going. A T1 circuit connects the company to the global internet, and there is a private connection to the credit card verification system.

What happens when one of the file servers crashes? If it happens in the middle of the workweek, it is likely that the people using it will notice and the appropriate administrator will be called to fix it. But what if it happens after everyone has gone home. Including the administrators, or over the weekend?

What if the private connection to the credit card verification system goes down at 10 p.m. on Friday and isn't restored until Monday morning? If the problem was faulty hardware and could have been fixed by swapping out a card or replacing a router, thousands of dollars in web site sales could have been lost for no reason. Likewise, if the T1 circuit to the internet goes down. It could aversely affect the amount of sales generated by individuals accessing your web site and placing orders.

These are obviously serious problems - problems that can conceivably affect the survival of your business. This is where SNMP comes in. Instead of waiting for someone to notice for fixing the problem (which may not happen until Monday morning, if the problem occurs over the weekend), SNMP allows you to monitor your network constantly, even when you are not there. For example, it will notice if the number of bad packets coming through one of your router's interfaces is gradually increasing, suggestion that the router is about to fail. You can arrange to be notified automatically when failure seems imminent, so you can fix the router before it actually breaks. You can also arrange to be notified if the credit card processor appears to get hung - you may even be able to fix it from home. Moreover, if nothing goes wrong, you can return to the office on Monday morning knowing there will not be any surprises1.

There might