Archive for the ‘console access server’ Category

The User Directory – A Vital Tool for Managing Console Access Server User Capabilities

Tuesday, March 1st, 2011

In a typical out of band management application, a console access server (http://www.wti.com/c-51-console-access-servers.aspx) is often connected to a variety of different network elements. This type of configuration allows remote access to console port command functions on each connected device, but it also creates a bit of a user management problem, in that you might not want to allow every user to have access to every connected device. A multi-level user directory often provides the best solution for managing multiple console access server users, and making certain that each user can access the devices that they need to access, yet are denied access to devices that belong to other users.

(more…)

The Temperature Alarm – A Vital Component for Any Console Access Server

Tuesday, February 15th, 2011

When managing a remote network equipment site, there are many different factors that a network administrator needs to be aware of. In addition to monitoring events such as power supply abnormalities and device failure, there are also a number of environmental factors that must be closely watched in order to ensure network reliability. The most important environmental factor is rack temperature; when a console access server (http://www.wti.com/c-51-console-access-servers.aspx) includes the ability to monitor rack temperature, this drastically simplifies the task of remote management, by providing administrators with assurance that remote devices are not overheating or being subjected to excessive cold.

(more…)

Using a Console Access Server to Collect Data and Error Messages

Tuesday, February 1st, 2011

Most network devices can be configured to send a wide variety of different types of data via their console ports. In addition to data items that the network device may have collected via monitoring capabilities, many network devices can also generate status messages, error messages, activity reports and other types of data which are then sent out via console port. In many cases, this data is either lost or ignored, but this is actually a waste; data sent out via console port can be an extremely helpful tool for network administrators who need to review error messages and status messages after a significant network event. WTI console access server products (http://www.wti.com/c-51-console-access-servers.aspx) offer an easy way to collect and store this data, providing administrators with the ability to revue recently generated data for diagnostic purposes.

(more…)

Console Access Servers Detect Problems at Remote Network Installations

Tuesday, January 18th, 2011

When a remote network equipment site includes a Console Access Server, network managers can access remote network elements via the console access server and address many network performance issues that might otherwise require a service call to the remote site. Console Access Server units provide a secure, reliable out of band management solution, that enables administrators to communicate with remote network elements, even when the primary network is down or unavailable.

(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…)

Why Does a Console Access Server Need Outbound SSH/Telnet Capability?

Tuesday, December 21st, 2010

When managing a network, it’s always best to have several different ways to access command functions on remote network devices. Efficiently planned network infrastructure should always include an alternate path to allow communication with remote network elements when normal network communication is not available. A console access server that includes outbound SSH/Telnet capabilities provides a secure, reliable means to communicate with remote devices when normal communication channels are either down or impractical.

(more…)