 |
Why Monitoring?
Information technology services, technology platform, IT departments, connectivity and communication lines are increasingly becoming the base and backbone on which companies manage their business and communicate or transact with customers, employees and suppliers. This infrastructure grows and becomes more complex as new services are introduced in order to reach new markets or improve the quality and loyalty of our customers.
Therefore, the level of service, professionalism and openness that is required of employees and information technology platforms that remain is increasing, becoming 100% in most cases, 24 hours a day, 365 days a year. However, the large number of devices, technologies, platforms, languages and interfaces with which they face in day to day increases proportionately. Also, is not enough to act reactively or in response to complaints about lack of service users or customers, but rapid and pro-actively because any downtime of technology platform becomes business downtime and, therefore, it negatively impact the company's sales.
In this scenario, any action or solution designed to monitor the entire technology platform is a rapid return on investment. It is no longer react to calls from users reported problems with the email and internet output, or with complaints from customers and managers cannot transact business through management systems, but to a control and monitoring system that scales detected problems instantly. Thus, downtime is drastically reduced and improved quality of service offered from TI
The solution that meets the requirements specified must be open architecture and must rely on standard protocols. In this way, you can monitor any platform and any manufacturer: communications devices, workstations, servers and critical hosts, network printers, security devices, PLCs, critical applications, etc.
Where is the line? In being connected to the network have an IP address and, if possible, enable the SNMP protocol.
Where monitoring reaches the limit of the solution? Since we rely on standard protocols (TCP / IP and SNMP) will rely on information provided by each manufacturer on their products. This information resides in file-like MIB (Management Information Base) that describe the products that can generate alarms and consultation on performance, product descriptions and availability can be made. For example, a server may be questioned on the use of their processors, the occupation of their records, internal temperature, the transaction load, etc., to a printer, load paper on her or his condition, to a router on the bandwidth used, a switch will request information from each of its active connections, to a backup application, the result of the daily backup.
Does it replace therefore the various tools of administration and management of the different devices? No. Each manufacturer manages its devices through interfaces and even different systems. Hardly a single tool will help users generate, detect intruders, analyze protocols and manage e-mail. However, if it is extremely practical to integrate this monitoring solution so that each device responds to a certain type of action and lead us to the tools and utilities needed to manage or solve the problems identified therein.
Project Scope
The scope of a proposed network management is variable, since variables are the elements to monitor in each case and, moreover, is a living project that evolves at the same time as the network infrastructure evolves. Also, as you reach milestones set at the beginning of the project will set new goals so that every time we get more control and to better manage on our platform.
All projects are carried out, yes, based on the same structure, which is:
After consulting
During this phase are carried out all studies requirements and setting goals for the following:
- Users and Groups-mail
- Responsible for device
- States to control
- Alarms and exceptions
- Monitoring Intervals
- Device Groups
- Links to third-party applications
- Integrating third-party MIBs
- Reports and statistics
- Monitoring Service
- Structure and remote consoles
- Escalation of incidents and Helpdesk system
- Offices
- Hierarchies and technical
- Detection and Tracking System
- Maps and scope of network management
Pre-Configuration
In the second phase of the project we will proceed to prepare the environment to implement the monitoring and management solution. To do this you must meet the following: (each one of the sites)
Inventory of devices (hubs, switches, UPS, Routers, Printers, Firewalls, Servers, Workstations, PLCs, backup systems, Internet services, etc)
- TCP / IP network devices and IP study (IP and routing services)
- SNMP Configuration
- Setting up services: databases and backups
Execution and implementation
Having met the two previous steps, it is time to deploy the solution. First we will implement all the necessary infrastructure elements through the organization. After installing the various applications will proceed to configure and implement each of the concepts defined in paragraph 1 in order to meet the technical and functional requirements defined, first in a test environment and then real.
Documentation and training
After the project is given a dossier final plasma state and configuration of the solution as well as backups of different databases generated. However, a draft Network Management and Monitoring is a live project as stated above. This makes it imperative that the client's technical staff trained in the use and customization of the tool so that, so they can continue to evolve and unfold.
|
