|
|
 |
 |
|
Frequently Asked Questions - Consoleworks
|
 |
|
|
|

|
What is ConsoleWorks?
|
|

|
ConsoleWorks is out-of-band systems management software. It is unique in that it was the first of its kind to make use of web server technology. Because it uses web technology, access to managed devices can now be achieved over most common company networks without requiring personnel to be present in the data center.
|
|

|
Why should I purchase ConsoleWorks?
|
|

|
Distributed, high availability and mission critical systems need constant monitoring and attention to make sure 'up time', and therefore, productivity are maximised. The cost of hardware and human resources required to maintain such an environment increases year on year. However, ConsoleWorks can reduce these costs by integrating your systems and hardware in a generic management policy. ConsoleWorks runs 24x7 without a break. Since it can be configured to engage its automatic actions at any time, it is like having a round-the-clock faithful and dedicated operator. Because it uses out-of-band management, ConsoleWorks provides a user the capability to verify current status using real-time data, troubleshoot machine health even if the operating system is off-nominal, and even restart the machine remotely. ConsoleWorks actions can be configured to notify appropriate personnel for any given situation at any given time using any means available to it. In short, installing ConsoleWorks with an independent console network provides access and support far superior even to being in the data center with a crash cart.
|
|

|
What can ConsoleWorks Manage?
|
|

|
ConsoleWorks can manage: processors, fabric switches, storage controllers, tape libraries, air handlers, HVAC units, clean room environments, security systems, PBXs, bar code scanners, manufacturing machines, electronic valves, and the possibilities are nearly limitless. If it has a SERIAL port ConsoleWorks can manage it.
|
|
|
|

|
What information do I need in order to purchase ConsoleWorks?
|
|

|
There are a few questions that when answered can provide all the information needed to get working with ConsoleWorks. These are: What operating system(s) are you running as a host for console management?
How many ConsoleWorks servers do you plan to deploy?
Do you require redundant ConsoleWorks servers for higher availability?
|
|
|
|

|
How many and what type of devices do you plan to monitor with each ConsoleWorks server?
|
|

|
Note: Please remember that ConsoleWorks can monitor Cisco, Marconi and other network devices, Compaq, SUN, HP and other brands of processors, storage devices such as HSGxx and HSJxx controllers, and generally anything that has a serial port.
With respect to the previous question, TDi has prepared Scan Files for certain types of devices, which greatly reduce efforts in setting up, configuring, and managing these systems. Currently we offer the following Scan Files: Open VMS 7.2, Brocade, Cisco, HSGxx and HSJxx.
|
|
|
|

|
Will you be using Serial, LAT, SYSLOG, Telnet, etc. connections to the devices or terminal servers?
|
|

|
Based on the number of connections needed, are these in one or multiple locations? If multiple locations, will ConsoleWorks be used centrally in one location to monitor all remote sites, or will each location be responsible for monitoring their own devices? When do you expect your environment to grow? What hardware do you plan to purchase within the next 3-6 months? 12 months? (By understanding the growth of the environment, you can demonstrate that buying more licenses now to cover that growth will actually be more cost effective (based on per seat license cost) than having them return 3+ months later to buy more licenses. Licenses for consoles come in 5, 10, 25, 50, 100, and 500 PAK groups PER ConsoleWorks Server.
|
|
|
|
|
|
|
|