Operating an OS 2200, UNIX, or Linux system through a console window on your Operations Sentinel workstation works the same as if you were actually using the keyboard and monitor attached to that system. The console window provides all keystrokes, function keys, and menus available for the console.
In Operations mode, you can open a console window by right-clicking the icon representing an OS 2200, UNIX, or Linux system or an OS 2200 console in a topology, or the row representing such a system or console in a table. You can also right-click an alert in the details pane provided the alert applies to an OS 2200, UNIX, or Linux system. In both Administration and Operations mode, you can open a console window from the Applications menu in the main Operations Sentinel Console window.
Notes:
The Monitor property must be True to open a UNIX or Linux console window, but does not affect opening an OS 2200 console window. See your Operations Sentinel administrator if you need to change the value of the Monitor property.
You cannot open a console window for a UNIX or Linux system configured for ping monitoring.
Operations Sentinel Console opens an empty window instead of a console window when the system or console is not communicating with the Operations Sentinel server. This reflects one of these situations:
An error condition exists with the system or console. The icon for the system or console in the topology indicates an inactive state or an alert.
The system is defined incorrectly.
Each time you open a console window, Operations Sentinel writes a message to the SP-EXTAPP log. This message includes the system name, the time you opened the session, your Windows login, and the process id (pid) of Operations Sentinel Console.
Console Window Guidelines
For MCP systems, the operator's display terminal (ODT) serves as the system console. In Operations Sentinel, a remote ODT is configured as a terminal session.
For UNIX or Linux systems, the following guidelines apply when you use a console window from a Operations Sentinel workstation:
Do not use the stty command to modify any of the console terminal characteristics. This information is not communicated to the terminal emulator and might cause an incompatibility between the emulator and the console device driver.
Editing activities (such as vi and ed) from the emulated console window are strongly discouraged, particularly when an SP-AMS database is active. Editing actions or displays might inadvertently match a pattern and produce undesirable system results. Use terminal sessions for such activities.
For a Windows system, a remote desktop takes the place of a console window.