Софт-Архив

Snmp Server Windows img-1

Snmp Server Windows

Рейтинг: 4.2/5.0 (1894 проголосовавших)

Категория: Windows: Мониторинг

Описание

Как установить и настроить Службу SNMP на Сервере администрирования?

Как установить и настроить Службу SNMP на Сервере администрирования?

Информация из статьи применима к программе  Kaspersky Administration Kit 8.0

В Kaspersky Administration Kit 8.0 добавлена возможность SNMP-мониторинга за основными параметрами антивирусной защиты корпоративной сети. Благодаря этой возможности администратор может получать информацию о событиях, регистрирующихся в базе Сервера администрирования, непосредственно на свой рабочий компьютер. Эти данные передаются с Сервера администрирования по протоколу SNMP.

Для использования этой возможности необходимо:

  1. На компьютере, где будет установлен Сервер администрирования, установить поддержку Simple Network Management Protocol (SNMP). Служба SNMP  (SNMP Service ) должна быть запущена и корректно настроена.
  • При установке Сервера администрирования установить компонент Агент  SNMP  (на шаге выбора компонентов для установки).

     Установка компонента Агент SNMP  возможна только в том случае, если на данном компьютере уже установлена поддержка протокола SNMP.

  • На рабочем месте администратора, где установлено средство обработки данных, получаемых по SNMP, должны быть корректно настроены и запущены:
    • SNMP Service  (Служба SNMP ).
    • SNMP Trap Service  (Cлужба ловушек SNMP ). Данный сервис отвечает за получение событий по SNMP.

    Данная статья описывает процесс установки и настройки Службы SNMP  на Сервере администрирования.

    Установка поддержки Simple Network Management Protocol  (SNMP) :

    1. Откройте Control Panel>Add or Remove Programs> Add/Remove Windows Components .
  • Выберите Management and Monitoring Tools и нажмите кнопку Details .
  • В открывшемся окне установите флаг Simple Network Management Protocol .

    Для установки Simple Network Management Protocol  вам потребуется установочный диск операционной системы.

    Настройка Службы SNMP на Сервере администрирования:

    1. На Сервере администрирования откройте консоль Services. Для этого в окне Start>Run введите services.msc и нажмите ОК .
  • В списке сервисов найдите SNMP Service  и из его контекстного меню вызовите команду Properties .
  • Перейдите на закладку Traps и выполните следующие настройки:
    • Выберите или добавьте имя сообщества в поле Community name (на примере my_community ).
  • В поле Trap destinations введите имя или IP-адрес компьютера-рабочего места администратора. где установлено средство для обработки получаемых событий.
  • Перейдите на закладку Security  и выполните следующие настройки:
    • Установите флаг Send authentication trap .
    • В поле Accepted community names  добавьте определенное на закладке Traps сообщество и предоставьте ему права READ ONLY и NOTIFY .
    • В нижней части окна установите значение Accept SNMP packets from these hosts и добавьте в поле имя или IP-адрес компьютера-рабочего места администратора. где установлено средство для обработки получаемых событий.
  • Убедитесь, что служба SNMP Service  запущена.

    После установки поддержки протокола SNMP вы можете установить Сервер администрирования с компонентом Агент SNMP . Необходимые для мониторинга mib-файлы будут расположены в папке установки Kaspersky Administration Kit, во вложенной папке SNMP .

  • Другие статьи, обзоры программ, новости

    Установка SNMP в Windows 2000

    Установка SNMP в Windows 2000/XP/2003

    Протокол Simple Network Management Protocol (SNMP) используется в системах сетевого управления для мониторинга сетевых устройствах для оповещения о событиях, которые требуют внимания администратора. Он состоит из набора стандартов по управления сетью, в том числе протокол прикладного уровня(Application Layer protocol), схемы базы данных и набор объектов данных.

    В ОС Windows службы SNMP доступна в виде компонентов Windows, но они не устанавливаются по умолчанию.

    Для установки SNMP в Windows, выполните следующие действия:

    1)                      Нажмите кнопку Пуск — Панель управления

    2)                      Нажмите кнопку «Установка и удаление программ».

    3)                      В левой панели, нажмите кнопку «Добавить / удалить компоненты Windows»

    5)                      Выберите «Simple Network Management Protocol»

    6)                      Вы также можете установить » WMI SNMP Provider «, который позволяет клиентам получать доступ к информации SNMP через интерфейсы WMI (Windows Management Instrumentation)

    7)                      Нажмите кнопку ОК и нажмите кнопку «Далее» и завершите установку.  В процессе установке вам понадобится вставить диск с дистрибутивом Windows в CD-ROM.

    После установки, найдите соответствующие службы в консоли управления службами(services. msc ):

    Запустите “SNMP Service ”, чтобы включить агента SNMP, и службу “SNMP Trap Service ”, чтобы иметь возможность получать SNMP сообщения (SNMP Traps) от других агентов.

    SNMP сообщения (SNMP Trap) – это сообщения, которые передают сервера (в случае возникновения определенного события) с установленным SNMP агентами на сервер системы управления SNMP.

    Итак, вы установили службу SNMP на Windows сервере, и теперь можете использовать ее в качестве SNMP агента или SNMP  сервера для того, чтобы отправлять или получать SNMP информацию от других систем, на которых установлен SNMP агент.

    Как настроить SNMP агент. можно почитать в следующей статье.

    Установка службы SNMP

    Установка службы SNMP

    Обновлено: Январь 2005 г.

    Назначение: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

    Чтобы установить службу SNMP
    1. Откройте мастер компонентов Windows.
  • В списке Компоненты щелкните Средства управления и наблюдения (не устанавливая и не снимая соответствующий флажок) и нажмите кнопку Состав .
  • Установите флажок Протокол SNMP и нажмите кнопку OK .
  • Нажмите кнопку Далее .
      Для выполнения данной процедуры необходимо быть членом группы "Администраторы" на локальном компьютере или получить соответствующие полномочия путем делегирования. Если компьютер присоединен к домену, эту процедуру могут выполнять члены группы "Администраторы домена". По соображениям безопасности для выполнения этой процедуры рекомендуется использовать команду "Запуск от имени".

    Чтобы открыть мастер компонентов Windows, нажмите кнопку Пуск. выберите Панель управления. дважды щелкните Добавить или удалить программы. а затем выберите Добавить или удалить компоненты Windows.

    Некоторым компонентам Windows перед использованием требуется настройка. Если один или несколько таких компонентов были установлены, но не были настроены, при нажатии кнопки Установка компонентов Windows отображается список компонентов, требующих настройки. Для запуска мастера компонентов Windows нажмите кнопку Компоненты .

    После установки SNMP запускается автоматически. Сведения о функциональных различиях

      Сервер может вести себя по-разному в зависимости от версии и выпуска установленной операционной системы, прав и разрешений вашей учетной записи и настроек меню. Для получения дополнительных сведений см. раздел Просмотр справки в Интернете.
  • Enable SNMP in Windows Server 2003

    Enable SNMP in Windows Server 2003

    If you want information on your Windows Server 2003 devices, SNMP is still the way to go. Here's how to enable SNMP in order to inventory your system statistics and send the results to the location of your choice.

    Simple Network Management Protocol (SNMP) continues to dominate when it comes to capturing information about a device and reporting that information back to a central authority. The popular and versatile open source Multi Router Traffic Grapher (MRTG) tool, for example, relies solely on SNMP to capture information from various network devices — including Windows Server 2003 servers — and then displays graphs detailing system parameters.

    1. Go to Start | Control Panel | Add Or Remove Programs.
    2. Choose Add/Remove Windows Components.
    3. In the Windows Components window, scroll down and select Management And Monitoring Tools. Don't put a check mark in the selector box; simply select the entry.
    4. Click Details.
    5. Scroll down and select the check box next to Simple Network Management Protocol.
    6. Click OK to return to the Windows Component window.
    7. Click Next and, if prompted, insert the Windows CD.

    How To Install, Configure and Use SNMP on Sever 2008

    How To Install, Configure and Use SNMP on Sever 2008

    With the release of Server 2008, SNMP (Simple Network Management Protocol) is now supported using IPv6 .

    Prior editions of Windows XP and Windows Server 2003 included SNMP support, but only with IPv4, even if the IPv6 stack was installed. Unfortunately, that means that SNMP management from Server 2008 will not communicate with SNMP services still on Server 2003 regardless of whether IPv6 is implemented on those servers.

    The good news, is that the updated TCP/IP stack in Windows Vista is capable of communicating with the new SNMP implementation.

    Still, the new implementation of SNMP in Windows Server 2008 offers much for the enterprise level systems administrator. Although SNMP Services are no longer installed by default, installing and setting it up is a snap.

    Why Use SNMP Services on Windows Server 2008?

    Many organizations have installed proprietary management systems over the years. These systems often provide more functionality than SNMP does. However, SNMP is both non-proprietary, and interoperable.

    These days, interoperable often means that something works on both Windows and Unix. However, in this case, interoperable means that it works on virtually any connected network device. This includes routers and other networking equipment as well as networked peripherals such as NAS devices and networked printers.

    Couple this wide range with relatively simple setup and the fact that you don’t have to pick and choose which devices to monitor to stay under a monitoring suite license count, and there are many uses for SNMP in most companies.

    Installing SNMP on 2008 Server

    start /w ocsetup SNMP-SC

    Configuring SNMP

    After installing the SNMP service, you configure the SNMP agent properties by right-clicking on the SNMP Service in the Services console and choosing Properties .

    In the Agent tab you can set the usual SNMP attributes like contact, location, and so on.

    The useful monitoring provided by SNMP comes from properly configured traps. Traps are configured via the appropriately named Traps tab. Here you configure the community name and address of the system to receive the traps.

    • Security Tab

    The Security tab is used to lock down the SNMP service to prevent any possible holes for hackers to exploit and to prevent the wrong people from receiving traps from the system. By default, the SNMP agent accepts packets from ALL hosts. This is something that will obviously need to be limited.

    The remaining options should be configured within your enterprise’s security and reporting scheme. Generally, the minimum security you want to use is to at least define the Accepted Community Names. Keep in mind that community names are case sensitive in SNMP.

    • Option Tabs

    Also, after installing SNMP in Server 2008, the SNMP option tabs will not show up until you have logged off and logged back on again. So, you won’t be able to configure anything until after you log back in. This has caused a fair amount of confusion in the field.

    If this is the server that will receive incoming traps, then your work is done at the server. Once the agents are configured, the data will flow back to the SNMP service where it can be used as necessary by administrators.

    Configure SNMP Event Traps in Windows Server 2008

    One nice feature of SNMP services is the ability to turn Windows level events into SNMP traps. This can be useful for many reasons, the most common of which, is the ability to monitor servers via a centralized monitoring station without any additional access rights.

    This concept is particularly useful for environments where servers are monitored overnight or on weekends by lower-level system operators.

    The system that already alerts them when devices (including Windows Servers in some cases) go dark on the network can also alert them to other events which may allow an administrator to head off trouble or to simply get advance notice of a potential situation.

    To translate Windows events into traps, run the evntcmd command. Once configured, the Windows events will trigger traps that are received at the monitoring console.

    There, the traps can be configured with an appropriate response. For example, certain traps could be ignored during business hours on the assumption other administrative tools will be alerting the appropriate admins. But, after hours, or on weekends, such traps might generate an alert that can prompt off-hours operators to take specific actions or to simply call or page the on-call systems administrator.

    A timely alert to building volumes of bad sectors can be the difference between an easy fix, and a rushed full-scale hardware reconfiguration.

    Is SNMP Right For Your Organization?

    Remember that SNMP services are fairly low overhead with all of the real work being split among hundreds or thousands of agents. Additionally, SNMP agents can be configured for installation as part of the unattended install for incoming workstations. In all, SNMP can provide a lot of value for little extra work.

    Ready to test your skills in Windows Communication Foundation? See how they stack up with this assessment from Smarterer. Start this Windows Communication Foundation test now.

    Monitoring Windows Server 2008 R2 with SNMP and Cacti

    Monitoring Windows Server 2008 R2 with SNMP and Cacti

    So you have a new Windows Server 2008 R2 installed and now you’d like to start gathering statistics about how it’s performing.  The SNMP protocol is a great way to get started.  In this tutorial I will install the SNMP agent service on a Windows server and configure it to allow queries from a SNMP based management server.  On the management server I will use a tool named Cacti that can collect this SNMP information and generate graphs from it in a fairly easy way.  I will assume that you have a server with Cacti already set up.  If not, details on how to set up an instance of Cacti on a CentOS Linux server can be found here .

    Install and Configure Windows SNMP Agent

    Okay first of all let’s install the Windows SNMP agent service.

    Under Features open up SNMP Services and check SNMP Service.  Click Next.

    Click Install at the confirmation screen, then click Close when the install is complete.

    Now it is time to configure the SNMP Service.  Back in the Server Manager in the left pane open up Configuration and select Services.  In the middle Services pane scroll down and double click the SNMP Service.

    Click the Agent tab and enter your Contact and Location information.  Click Apply.

    For now we’ll skip any configuration in the Traps tab.  This should only be necessary if you want to configure the SNMP agent to notify our monitoring server of any events without the monitor soliciting the information.

    In the Security tab under Accepted Community Names click Add.

    We’ll only be reading information (and not setting parameters) on the SNMP agent so keep Read Only and type a Community Name.  Using a name other than “public” will help keep unauthorized clients from reading SNMP information from the agent but this is still not completely secure.  Click OK.

    Now click the second Add button under Accept SNMP Packets.

    SNMP Traps in Windows Server - Microsoft Enterprise Networking Team - Site Home - TechNet Blogs

    SNMP Traps in Windows Server

    What is an SNMP Trap?

    It’s nothing but an alert message with abstract information about an event sent from an SNMP agent to its configured SNMP manager. It notifies the administrators about an event that occurred in the SNMP agent. There is separate service called SNMP Trap service which runs in Microsoft operating systems and listens for traps on UDP port 162 by default.

    How to install it?

    When you install the SNMP service on any Microsoft Windows operating system except Windows Vista and Windows Server 2008, the SNMP Trap service is installed along with the SNMP Service. In Windows Vista and Windows Server 2008, the SNMP Trap service is by default installed but set to manual and is thus in a stopped state.

    The SNMP Trap service runs using the Local Service account in Windows. The SNMP Trap service was dependent on the Event Log service up until Windows Server 2003 but since Windows Vista and Windows Server 2008, the SNMP Trap service has been independent.

    I want my SNMP manager to listen for SNMP Traps on a different UDP port. Is this possible?

    Yes, open the file named “Services”, which is located in %systemroot%\system32\drivers\etc.

    Edit the port number on the following line on the file with your customized port numbers.

    snmptrap 162/udp snmp-trap #SNMP trap

    Save the file as it was with no extension. Restart the SNMP Trap service. Run the following command in a Command Prompt: Netstat -ano and you should see the SNMP Trap service listening on the new port number.

    What does “Send Authentication Trap” mean?

    An SNMP agent sends Authentication traps to its configured trap destination List in the following situations:

    • When an SNMP query is sent from an SNMP manager which is not listed in the Permitted Manager's list of SNMP agent.
    • When an SNMP query is sent from an SNMP manager which is listed in the Permitted Manager's list but the community name in the SNMP query doesn't match the agent's community name configured on the security tab of the SNMP agent, like when the community name is misspelled (it is case sensitive).
    • When both of the above conditions are true in a given situation.

    An agent traps all the trap destinations of all the communities, provided these community names are configured in the Security tab of an agent. So if multiple trap destinations are configured with multiple community names, then a trap message is sent to all the destinations of all the communities specified on the trap tab. This happens three times in succession after each access violation. However a trap message to a trap destination will have the community name specified in the SNMP agent for that trap destination.

    Make sure of following things:

    • The name configured in the security tab is case sensitive which means that it should be in the same case as that of the community name that is received in the query. But the community names configured in the trap tab is not case sensitive, meaning for example if a community name called "TEST" is configured in the security tab then the equivalent name "test" can be configured in trap tab for sending traps to the specified trap destinations.
    • The “SNMP Agent Service” is not in a disabled state on the SNMP agent device.
    • UDP Port 162 is open on any firewalls involved. In Windows Vista one exception rule is pre-defined in the firewall configuration settings for SNMP trap, but it is disabled by default. It needs to be enabled.

    How do I test if my SNMP Manager is able to receive SNMP Traps?

    You may have 3 rd party applications which make use of the built-in SNMP trap service to receive traps and then react to the trap. If you find that your SNMP manager application is not receiving traps, first make sure the built in SNMP Trap Service is able to receive traps. If the SNMP Trap service is able to receive traps then it’s the application which is not working the way it should.

    To check the functionality of the built-in SNMP Trap service, do the following:

    1. Create a new folder under any drive (For example: C:\snmputil) on the SNMP Manager machine which is configured to listen for the traps.
    2. Copy the “snmputil.exe” utility to the newly created folder.
    Snmputil.exe is available from the Windows 2000 and Windows Server 2003 Resource Kits.
  • Open up a Command Prompt and change to the directory where you have the snmputil.exe (in our example it is C:\snmputil) and run the following command: “Snmputil trap”.

    You will see the following output:

           snmputil: listening for traps.

               Let the command run and do not close the Command Prompt window.
  • Stop and Restart the SNMP Service on any SNMP Agent which is configured to send traps to the SNMP Manager mentioned in step 1 above.
  • If the test is successful, you should see the below output in the SNMP Manager Command Prompt window on the SNMP manager machine. This will show that traps generated by the agent are being received.

    snmputil: listening for traps.

    Incoming Trap:

    generic = 0

    specific = 0

    enterprise = .iso.org.dod.internet.private.enterprises.microsoft.software.syst

    enterprise = .iso.org.dod.internet.private.enterprises.microsoft.software.syst

  • What Is SNMP: Simple Network Management Protocol (SNMP); Services for Macintosh

    What Is SNMP?

    In this section

    Simple Network Management Protocol (SNMP) is a popular protocol for network management. It is used for collecting information from, and configuring, network devices, such as servers, printers, hubs, switches, and routers on an Internet Protocol (IP) network. Microsoft Windows Server 2003 provides SNMP agent software that works with third-party SNMP management software to monitor the status of managed devices and applications.

    Automating Network Management

    Large networks with hundreds or thousands of nodes are difficult to manage without a large staff to monitor every computer. SNMP, which is widely used in local area networks (LANs), lets you monitor network nodes from a management host. You can monitor network devices such as servers, workstations, printers, routers, bridges, and hubs, as well as services such as Dynamic Host Configuration Protocol (DHCP) or Windows Internet Name Service (WINS).

    Use SNMP management software to monitor any network device on which you install SNMP agent software. The SNMP agent, which is an optional component of Windows Server 2003, interacts with third-party SNMP management software to enable the sharing of network status information between monitored devices and applications and the SNMP management system that monitors them. The following figure shows this process.

    Computer Running SNMP Manager Requests Status Information from Devices Running SNMP Agent

    Using SNMP, you can monitor network performance, audit network usage, detect network faults or inappropriate access, and in some cases configure remote devices. SNMP is designed to be deployed on the largest possible number of network devices, to have minimal impact on the managed nodes, to have minimal transport requirements, and to continue working when most other network applications fail.

    SNMP Background

    Developed in 1988 to provide network-device-monitoring capability for TCP/IP-based networks, SNMP was approved as an Internet standard in 1990 by the Internet Architecture Board (IAB) and has been in wide use since that time. More recently, Internetwork Packet Exchange (IPX)-based networks have added support for SNMP. Currently, most network equipment vendors provide SNMP support in their products.

    Windows Server 2003 supports SNMP versions 1 and 2c, which are based on the industry standards described in the following table.

    Industry Standards for SNMP Versions 1 and 2c