Arquivo da Categoria ‘Opmanager’

Netrunner Tecnologia migra todos os serviços para a Amazon AWS.

31, agosto, 2014 Sem comentários

Após analisar minuciosamente diversos fornecedores de serviços em Cloud, a equipe técnica da Netrunner Tecnologia escolheu a Amazon AWS como seu principal fornecedor, a decisão foi tomada, após diversos problemas com o antigo fornecedor.

Netrunner Tecnologia x SEP Software x ManageEngine x Amazon AWS

As parcerias fechadas pela Netrunner Tecnologia foram vitais para a decisão.

Entre os diversos problemas enfrentados, estão o atendimento ineficiente da equipe de suporte e a indisponibilidade dos serviços, que só puderam ser detectados, devido a utilização das ferramentas OpManager e Applications Manager da ManageEngine. A Netrunner Tecnologia utiliza essas ferramentas para monitorar seus serviços.

Agora, nossos clientes contam com os serviços do maior fornecedor de Cloud do mundo, com altíssima disponibilidade e qualidade. Além do monitoramento pró ativo das ferramentas da ManageEngine.

A migração rápida e precisa, só foi possível, utilizando a ferramenta de backup da SEP Software, que permitiu a transferência de todos os dados de maneira simples e eficiente.

As opções de Backup e Disaster Recovery da SEP, são utilizadas mundialmente, e permite a rápida restauração de um ambiente perdido, em uma nova infraestrutura, seja ela física ou virtual.

“Essa decisão estratégica visa atender aos nossos clientes com o que há de melhor no mercado, tivemos diversos problemas com o antigo fornecedor, desde falhas no atendimento dos chamados, até indisponibilidade dos serviços, e isto é inaceitável no mundo digital.”, esclarece Rodrigo Miranda, diretor técnico da Netrunner Tecnologia.

Mais informações:
Site Netrunner – SEP Software

Site Netrunner – ManageEngine

Fonte: Blog Netrunner


OpManager versão 10

28, março, 2013 Sem comentários

A nova versão do OpManager conta com várias novas funcionalidades, uma bem importante é o suporte ao IPV6 que em breve deve dar as caras por ai.

Foi adicionado o plugin do nosso querido ApplicationsManager, agora nosso canivete suíço esta completo, além de monitorar todos os devices de nossa infra, também monitoraremos nossas aplicações.

O vCenter/VSphere é o ponto central para monitoração do nosso ambiente virtual.

Não precisamos mais caçar nas MIBs dos fabricantes as informações como temperatura, voltage, power, fan speed, etc. Eles já estão no OpManager muito mais fácil e pratico. Segue lista completa do próprio site do OpManager.

Fiz o upgrade em cliente e esta se comportando bem até agora…


OpManager v10 – Build No. 10000 – March 18th, 2013


New Features

  1. Now OpManager provides support for monitoring IPv6 network devices and servers. After discovery, device templates along with the essential monitors are applied on the IPv6 devices and monitored for performance.
  2. Applications Monitoring plugin for in-depth monitoring of applications such as Oracle, SAP, Sharepoint, Websphere and much more has been added now.
  3. Get granular insight into your VMware environment, as OpManager now monitors VMware ESX/ESXi and VMs through vCenter via vSphere API.
  4. Now OpManager out-of-the-box monitors hardware health such as temperature, voltage, power, fan speed, status of processors, storage, memory, disk arrays, etc. of HP, Dell, Cisco and Juniper devices, via SNMP. OpManager also supports hardware monitoring for ESX hosts via vSphere API.
  5. Failover support for OpManager Central server has been added now. Probe already includes support for failover.
  6. Now raise a ticket with OpManager support along with the support information file, in a single click (Support-> Request Support).
  7. Adding notes to an alarm has been simplified now. In alarms page, now you can add alarm notes by clicking ontem the “Note addition button” present beside each alarm notification. You can also add alarm notes in bulk by selecting the desired alarm notes and clicking on “Add note” button.
  8. In Enterprise Edition, the intelligence to detect build mismatch between Probe and Central has been added.
  9. Time Window option has been added in Schedule Reports page (Issue ID 91998)
  10. Time out and max hops are now supported in TraceRoute in both RestAPI and Workflows.
  11. Search filtering option added in All Devices and All Interfaces page


Customer Issues Fixed: Build 10000


•    MSSQL instance name duplication due to “MSSQLFDLauncher” services is resolved.
•    Issue with backslash character in WMI attributes leading to an error page is fixed now. (Issue ID 93648)
•    Issue with managing URL’s due to license check is fixed now. (Issue Id 93539)
•    Now ‘${IPAddress}’ variable can be used in workflows. (Issue Id 93694)
•    Alarms added via ‘Add Event’ API can be cleared with Rest API. (Support Request Id 4542842)
•    Difference in device count shown in ‘About’ page and ‘Probe’ link under admin tab is fixed.
•    Probe slow down issue is fixed.
•    Issue with “Execute Windows Script” task not responding while executing workflows is fixed. (Issue ID 93738)
•    New filtering parameters are added in Rest API for listing alarms. (Support Request Id 4498614)
•    In IE, the issue with real-time graphs in device snapshot page not showing up is fixed now. (Support Request Id 4521422)
•    Devices by Packet Loss widget was displaying zero packet loss condition in red bar. Now it has been fixed and changed to green color.
•    Issue with false alert getting generated for windows services is fixed.
•    Issue with configuring username in authentication details of mail server has been resolved.
•    Data truncation issue in SysLog email notification due to the presence of angular brackets (< , >) in SysLog message has been resolved now (Issue Id 93569)
•    SysLog alarms are not getting generated when there is a single syslog rule. This issue is fixed. (Issue Id 93524)
•    Issue  with URL monitors not getting updated on consecutive times even when threshold is enabled, is fixed.  (Issue ID 93915)
•    Single quote issue in IE while executing windows script in workflows is fixed now.
•    The issue with multiple thresholds configured in newly created Device Template not getting reflected in central & other probes is fixed now.
•    Issue related to recurring notifications is fixed. (Issue Id 93672)
•    The issue with showing an error Message “Router IOS version may be lower than 12.3″ shown even though the device is of greater IOS is fixed
•    IPSLA link status getting greyed out i.e. unmanaged is fixed
•    In IPSLA, issue with adding IPSLA in French and editing display names is fixed
•    Probe trying to register with Standalone OpManager Edition in enterprise edition is
•    resolved now.
•    During Failover, Unwanted Timers that runs when in standby mode is cancelled and stopped.
•    Multiple syslog rule creation caused by refreshing ‘submit’ page of Syslog addition is fixed.
•    Logo was missing in availability reports. Now logo has been added (Issue ID 93449)
•    Icons to display critical and trouble threshold status in List view page have been added.
•    Now you can also Windows Service monitor by using vendor name instead of type.Services, and URL monitors are allowed for categories
•    For users with full control to a business view, adding WMI monitors option was disabled. This issue has been fixed. (Issue ID 93555)
•    Issue with iPhone alarm page navigation issue is fixed (Issue ID 93515)
•    For printers, even though no alerts are configured when it turns to clear state, alerts are getting raised. This issue has been fixed.  (Issue ID 93614)
•    Average value is shown in threshold alerts for CPU utilization with multiple instances.
•    When editing any Availability and Response report, certain options were missing. This issue has been fixed.
•    Proper icon was not associated for devices from Dell. This issue has been fixed.
•    The status of the Services shown wrongly in Maps –> details view is corrected now (Issue ID 93875)
•    Test Action at times failes  for System Command / Run Program profiles if the Alarm Message contains $ symbol is fixed (Issue Id 94057)
•    Problem Retrieving XML data alert popup while viewing WAN RTT Monitors (Issue Id 93737)
•    Run System Command profile fails for trap, when we select the specific traps in Notification profile. This is fixed now (Support Request Id 4538155)
•    Technician name filter in the alarms page is fixed
•    Unable to  start postgres database in german installation is fixed (issue id  93801)
•    Unable to rediscover the interfaces for the devices discovered as non snmp device and then configuring snmp credentials for the same. (Issue Id 92587)

Fonte: Site Pastelaria Digital

Categories: Opmanager Tags: ,