Posts Tagged ‘event log’

Console Server Management and Event Logging

Wednesday, June 8th, 2011

In applications that require management of remote network equipment sites, a good console server management unit needs to do more than merely provide secure out of band access to console port command functions on remote network elements. Often, a console server management unit must also serve as a means to allow network administrators to track events and conditions at remote sites, essentially providing the administrator with a way to examine temperature trends, power events and other important factors at equipment racks that are so remote, that the administrator cannot easily keep track of these conditions in person. In cases like this, a console server management (http://www.wti.com/c-40-console-server-management.aspx) unit that supports the ability to log events and environmental conditions can prove to be an extremely valuable asset.

(more…)

A Console Terminal Server with Event Logging Improves Remote Network Management

Thursday, March 31st, 2011

In many remote network management applications, a console terminal server does more than merely providing remote access to console port command functions. Often, the console terminal server also helps network administrators to keep better track of events and conditions at remote sites without the need to constantly send technicians out to check on the site in person. In addition to providing out of band access to remote network elements, a console terminal server can also monitor and log power interruptions, user activity, temperature trends, alarm events and other significant data concerning a remote network site that can help to give administrators a broader perspective of conditions and trends at a remote site in order to assist in planning for future needs and contingencies.

(more…)

Why is Event Logging an Important Factor in Console Server Management?

Wednesday, March 2nd, 2011

In addition to providing out of band access to console port command functions on remote network elements, a console server management unit can also enable network administrators to be better informed about events and environmental conditions at remote network equipment sites. A console server management unit can monitor rack temperatures, power conditions, communication status and user activity at remote sites, and log and time stamp data for later review.

(more…)

Serial Switch Features for a Comprehensive Out of Band Management Solution

Thursday, February 24th, 2011

A serial switch (http://www.wti.com/c-46-serial-switch.aspx) should be able to more than just provide access to console port command functions on remote network elements. Ideally, a serial switch should also be able to monitor conditions and events at remote network sites and notify network administrators when potential problems are detected. In addition, a serial switch should also be able to report its own status, network conditions and port conditions and log noteworthy events for later review.

(more…)

Alarm and Event Logs Make a Console Terminal Server a Powerful Tool for Out of Band Management

Thursday, January 6th, 2011

When something goes wrong at a remote network equipment site, the most immediate and important task is to correct the problem in order to restore network communication. But once you’ve fixed the problem, you’re still left with an equally important task: finding out exactly why the problem occurred in the first place so you can prevent it from happening again. A console terminal server that includes monitoring, alarm and event logging capabilities provides a valuable tool for diagnosing network problems and helping network administrators to ensure that those problems don’t occur again.

(more…)

A Console Access Server with Environmental Alarms and Event Alarms

Tuesday, January 4th, 2011

When something goes wrong (or even starts to go wrong) at a remote network equipment site, it’s vital for network administrators to know about it as quickly as possible. Environmental factors such as an increase or decrease in rack temperature and significant events, such as failure to respond to a ping command, can be an important indication that all is not right at a remote network facility. The most reliable way to keep informed about environment changes and events is to include a console access server with monitoring capabilities in the design of your remote network equipment sites.

(more…)

Windows Event Viewer Plus

Monday, December 13th, 2010

I haven’t really used the Event log either; not because it’s too complicated and scary … I just haven’t needed to use it yet.

Most Windows users shy away from the powerful Event log thinking that it is too complex and complicated to be of use. The Windows Event Viewer on the other hand can reveal information about errors or alerts that would otherwise be hard to come by, if at all possible.

(more…)

How to Create Desktop Notifications For Windows Events

Tuesday, August 31st, 2010

I haven’t really played around with Windows event logs much, but this article makes me interested …

The Windows event log records all kinds of events automatically in the operating system, from application installs to hardware failures and user permission changes.

Many Windows users on the other hand ignore the event log, mostly because it takes some time to get used to it. The sheer size of the recorded events of a system, and the nimbus of being a tool for system administrator and experts are two additional factors that play a role.

(more…)

Why Does a Console Server Need Event Logging Capabilities?

Wednesday, July 28th, 2010

For data center managers, it’s very important to know exactly what’s going on inside of their equipment racks at all times. If a device fails to respond to a ping command, your IT personnel need to know about it right away; if rack temperatures rise to troublesome levels, they need to know about that right away too. Although a console server with intelligently designed alarm functions, such as WTI’s RSM and TSM series console server products, can help to alert you to relatively major events like failed ping commands and high temperatures, what do you do if you want to know about less noteworthy events such as command activity, temperature trends and previous alarm activity?

(more…)