Tuesday, November 10, 2015

Fwd: Nagios XI 5.2.1 Now Available




Upgrade to Nagios XI 5.2.1 Now
Nagios XI 5.2.1 is now available. This release provides increased stability, and fixes for every reported bug.
Nagios XI 5.2.1 is now available. This release provides increased stability, and fixes for every reported bug.
To view a full list of changes included in this release, you may reference the changelog. Need help upgrading? Upgrade your XI installation to the latest release using the following instructions listed here
 
We greatly appreciate the feedback that the Nagios community continues to provide. If there is a feature you would like to see in a future release of Nagios XI, be sure to share your ideas with our tech team in our Nagios Ideas Forum.

Want to learn more about the features and capabilities of Nagios XI? 
Attend one of our upcoming webinars. Register Now

Forward this email



This email was sent to fanky@dayaciptamandiri.com by nagios@nagios.com |  


Nagios Enterprises | 1295 Bandana Blvd N | Suite 165 | Saint Paul | MN | 55108



--

Fanky Christian  Director  PT. DAYA CIPTA MANDIRI SOLUSI  Graha Utaka26  Jl. Utan Kayu Raya No.26A  Jakarta Timur, Indonesia, 13120    Telp: 62-21-2962-2097  Fax: 62-21-2962-2098  Support: 62-881-8867333    mobile: 62-812-1057533 / 0881-8857333   skype: fankych1211  web: www.dayaciptamandiri.com    Data Center & Structure Cabling  [Raised Floor Nortex, Intessa, MIRA, ZTFloor]  [UTP & FO - Netviel, TE-AMP, Panduit]  [PAC & AC - GEA Denco, Daikin]  [Environment Monitoring - AKCP]  [Build, Moving, Renovation, Re-cabling Services]    Enterprise Solutions  [ManageEngine, WebNMS, PRTG, Nagios, Netgain ]  [SendQuick, OZEKI-NG ]  [Firewall & VPN - WatchGuard, Draytek]  [Application Delivery - GraphOn]  [Database & App Builder - Navicat, PHPRunner]    Managed Services  [Data Center Management] [Structure Cabling System Maintenance]  [Monitoring Network][Monitoring EMS][Maintenance SMS Gateway]

Saturday, October 31, 2015

Monitoring Data Center

Monitoring datacenter performance - a synergy of server performance (both physical & virtual), application performance, and sufficient bandwidth, is a great challenge. The challenge rises multifold when disparate monitoring tools are used.
Whenever an end user reports slow access to an application, the issue could be with the server or bandwidth or application itself. To find out the exact issue you have to poke your head into multiple monitors and look out every nook and corner, right from server performance to bandwidth bottlenecks to application performance. You will not find any correlation between the data provided by the tools. By the time you organize the data and hunt down the issue, the application would have gone down completely.

Monitor your Datacenter Performance from OpManager's unified web console

ManageEngine OpManager offers an integrated approach towards datacenter monitoring that helps you proactively monitor physical & virtual servers, applications and bandwidth to the core; yet manage their faults from a single console. OpManager offers a single alarm console where all the issues irrespective of the type whether it is an application, server or bandwidth, are raised. This makes it easy for the technicians to pick up the alarms in real-time, drill down to the exact issue and start troubleshooting it before the end user feels the impact.
OpManager offers:
  • In-depth physical and virtual server performance monitoring
  • Real-time application monitoring by integrating Applications Manager
  • Flow-based traffic monitoring with NetFlow plug-in
  • Datacenter environment monitoring

Physical and virtual server monitoring

OpManager out-of-the-box includes support for the widely used servers such as Windows, Linux, Solaris, VMware, Hyper-V, and much more. It offers dedicated dashboards for the worst performing Hosts and VMs that need immediate attention. More.

In-depth Application Monitoring

OpManager monitors the performance of mission critical applications such as Oracle, JBoss, Tomcat, WebLogic, WebSphere, SilverStream, GlassFish, and much more by integrating ManageEngine Applications Manager. You can customize the tabs and load Applications Manager's web client in OpManager web client.

Flow-based bandwidth monitoring

OpManager's NetFlow Plug-in leverages flow-based network traffic analysis to show you how exactly your bandwidth is being utilized through interface - specific reports on which user, application, source, destination, conversation, etc. is occupying bandwidth. More.

Datacenter environment monitoring

Temperature is also a very critical parameter in datacenter monitoring. OpManager monitors temperature of servers and routers. You can configure thresholds and monitor them proactively. We integrate with AKCP (www.akcp.com) sensors to gain more powerfull sensors













Contact Us for detail : Office 62-21-29622097/98, HP:08121057533, email: askme@dayaciptamandiri.com

Saturday, September 19, 2015

Monitoring suhu ruangan melalui NMS




With PRTG Network Monitor you can set up sensors that constantly monitor the availability and performance of important servers and other equipment in the server room.
Furthermore, it is possible to closely monitor environmental factors such as temperature and humidity. Environmental monitoring is an important issue to protect your equipment from damage that is caused by high temperatures, humidity, or other external influences. If something uncommon is detected, PRTG can notify you in several ways (please see Notifications in the user manual).
An extensive monitoring takes place on two levels: On the one hand, you can obtain measurements directly from the servers and on the other hand, you should also consider environmental values measured in your server room.

Monitoring Servers

With more than 150 sensor types, PRTG can obtain many different measurements from the devices in your network, including uptime, bandwidth usage, and performance values.
Additionally, in order to avoid system failures, you can easily monitor servers and other devices to avoid system errors due to overheating and similar health factors. In PRTG there are already some System Health sensors available for various device types, including the following ones:
With these sensor types you can monitor, for example, the current temperature of a device, its thermal status, cooling status, fan status, and many more, depending on the available measurement components. For this concern, PRTG uses the Simple Network Management Protocol (SNMP) or Windows Management Instrumentation (WMI) to get these values.

Monitoring Servers – Steps to Go

You can monitor the system health of your servers the following way:
  • Add the desired device, for example, your HP ProLiant server, to PRTG (e.g., via the button Add Device on a group’s details page). 
  • Then add a corresponding System Health sensor to this device (e.g., via Add Sensor on the device’s details page). 
  • The channels showing the desired information will be created automatically at run-time, depending on the available measurements reported by your devices, for example, temperatures.
PRTG will begin to monitor the selected device a few seconds later. With PRTG’s pre-defined limits, for example, for temperatures, you will get warnings immediately if a critical threshold is breached. Of course, you can set limits according to your preferences.

Monitoring the Server Room or Data Center

It is not only possible to monitor a server itself. There are also a lot of environmental monitoring possibilities out there. With specific SNMP-enabled hardware sensors in combination with PRTG you can even monitor factors like temperature of environment, humidity, water leaks and floods, fire and smoke, brightness, open and closed doors or windows, as well as other potentially harmful data center conditions. In general, they all work the same way together with PRTG: using SNMP. 
Following are listed some hardware devices for environmental monitoring which we have tested successfully in our labs:
All of these vendors offer physical sensors which can provide data about their environment. Connected to some kind of SNMP-enabled “management box” these sensors become network-enabled.
The manufacturers usually provide Management Information Base (MIB) files for their devices. Basically, a MIB is a text file defining all searchable SNMP objects of a certain device. It includes at least one Object Identifier (OID) defining an unique address and name, and gives further information on the respective object. With our MIB Importer you can import the MIBs of the measurement devices into PRTG. 

Monitoring Server Room – Steps to Go

To use one of the devices listed above for environmental monitoring with PRTG, do the following:
  • Make sure you have converted the needed MIBs to OIDLIB files and saved them in the snmplibs sub folder of your PRTG program directory
In the context menu of a group or probe, choose Add Device… to add a device to PRTG which represents your measurement device: 
  • Type in a suitable name (e.g., PCMessure) and use the device’s IP address in the settings. You can leave the other settings unchanged. 
  • Then click on Add Sensor on the device’s details page and select the sensor SNMP Library (to find it easier, filter for SNMP as used technology) with Add This
  • A popup will appear where available library files are listed. Choose the library that you have created from the MIB and confirm with Ok
  • Then choose the sensors you want to monitor by clicking on the corresponding check boxes and confirm it. PRTG will usually create several sensors, one for each individual OID.
Now you are able to monitor the environment of your devices, for example, in your server room. PRTG will start to monitor the sensors of your measurement device immediately and will alert you if it is necessary.

See Also

Monday, August 17, 2015

Panel Listrik dengan Pintu Proteksi

Sering kali kita lihat Panel Listrik di tempat umum tidak terproteksi. Gunakan panel pintu tambahan seperti ini untuk menjaga panel agar tidak disentuh oleh tangan jahil.

Rak 6U dari Rittal

Rak 6U dari Rittal dengan harga khusus.

Rak untuk Colocation

Rak khusus untuk Colocation dari Rittal

10 Prinsip Desain Data Center Google


Google has long pushed the envelope of data center infrastructure design, particularly when it comes to renewable energy, efficient cooling, new power electronics and innovative building layouts. And according to Joe Kava, vice president of Google’s data centers, Google’s data center strategy roughly follows Google’s original 10 core defining principles that the company’s founders wrote out when it was still very young.
Kava laid out these tenants, and connected them to Google’s data center design strategy, during the Green Grid Forum in Santa Clara, Calif. on Tuesday:
1). Focus on the users and all else will follow: Google’s audience is global, so it’s not surprising that the search giant is looking to build data centers across the globe to serve different regions of the world. By placing servers as close to users as possible, Google cuts down on the time it takes for users to use its tools and do search queries. Kava said Google processes 1 billion search queries across its global users per month. Picking locations, and constructing data centers, is ultimately a UX issue for Google.
Google's data center in Lenoir
Google’s data center in Lenoir
2). It’s best to do one thing really, really well: Google by some guesses has built as many as 40 data centers, so it’s safe to say that Google has the process of finding a location and building a facility down pat. Over the years, the company has included in its criteria things like finding a good local workforce and accessing a robust electric grid as key qualifications. More recently, Google has increased the importance of greener issues like finding a location where the utility offers a significant amount of renewable energy.
3). You can be serious without a suit: Even though Google doesn’t care about how data centers look from the outside, it aims to bring a piece of the alternative Google culture from its HQ to its server farms. Kava showed a slide of a colorful recreation room at a data center to emphasize the company’s “work hard, play hard” philosophy.
4). The need for information crosses all borders: This philosophy relates to at least two aspects of Google’s data center operations. First the move to putting data in the cloud makes it easier for users to access data wherever they are. Second, Google is looking to be transparent about the metrics for its data centers. Given the importance of energy in designing and running data centers, Google has opted to make public some of its internal energy consumption data.
5). You don’t need to be at your desk to get answers: Google searches for interesting and unusual solutions for some its data centers across the globe, and far outside of its Silicon Valley roots. For example, Kava highlighted its data center in Finland that uses the cold outside air and sea water to cool its servers. The data center is inside a former paper mill, and Kava noted that Google has re-used pumps and other electrical equipment from the mill to operate its servers. It’s a highly unique design and one of the only ones like it in the world.
Google data center
6). Faster is better than slow: In Google’s philosophy, the term efficiency doesn’t just refer to how Google wants to use electricity to power servers. How quickly Google designs and builds data centers is equally important, Kava said. He pointed to a data center in Georgia that took 16 months rather than 2-3 years as an example of how the company has created a set of standards for designing and building data centers.
7). Great just isn’t good enough: This rule has to do with setting higher goals, and Kava used it to describe how Google also allows room for customizing data center designs to make better use of local resources. For example, the company relies on the cold outside air instead of a chiller to cool its data center in Dublin, Ireland.
8). There is always more information out there: Google is currently on the fifth generation of its data center designs, but Google still continues to learn and improve its process. Sometimes that means that Google has to learn techniques and skills outside of its core competency. The need to cool servers and reduce wasteful energy consumption has forced Google to develop an expertise in designing systems to transfer and use energy more efficiently. In addition, to make the most use of the indoor space of its data centers, Google has designed the layout of its servers to maximize the effectiveness of cooling systems.
GoogleDataCenter1
9). You can make money without doing evil: Reusing waste water is a good example of something that Google can do for both economic and eco reasons. In Belgium, Google has built its water treatment plant to take water from a canal nearby suitable for industrial use. The company also uses treated wastewater for its data center in Georgia.
10. Democracy on the web works: O.K. this one is a bit of a stretch. Yes, democracy does work, indeed, Kava said, but it’s hard to draw a connection between this last rule and Google’s data centers.