A secure remote console permits you to remotely manage devices using a web browser.
All administrator actions on a device are recorded.
Types of Protocols
The following table shows the types of supported protocols:
| Protocol Type (Service Type) | Connector Type | Supported Console | Port Number | IP Address |
|---|---|---|---|---|
| Remote Desktop Protocol (RDP) | Agent/Gateway | Browser | 3389 | Local host IP address 127.0.0.1 |
| Secure Shell (SSH) | Agent/Gateway | Browser | 22 | IP address of target device |
| Secure Shell with Public Key (SSHPUBLICKEY) | Gateway | Browser | 22 | IP address of target device |
| Telnet (TELNET) | Agent/Gateway | Browser | 23 | IP address of target device |
Locations to launch consoles
You can launch a browser console from the following locations:
- Infrastructure page on each device
- Infrastructure page on multiple devices
- Device Details page
- Alert Details page
- Incident page
- Service Desk page
- Management Profile page
- Gateway Profiles page
- Topology page
FAQs
How to verify the connection status for both agent and gateway?
The connection status of agent and gateway needs to be in the active status. To test connection status, from the installed agent or gateway verify the access to:
- OpsRamp server
- Browser DNS names or IP addresses
- Telnet IP port
How to add credentials for different consoles?
For the Console types, SSH, Telnet, and RDP, you need to create credentials. To add a credential, navigate to Infrastructure, Devices, Target Device, Credentials, click Add, and select Type (RDP, Telnet, or SSH).
The following table describes the credentials needed for the different protocols:
| Console Type | Credential Usage | Details |
|---|---|---|
| SSH | Username and Password | Enter username and password |
| SSH with certificate | Certificate | Use the key/certificate |
| Telnet | Username and Password | Enter username and password |
| RDP | Username and Password | Enter username and password with options related to NLA login with or without domain or computer name. |
How long are the console recording activity files stored?
Console recording activities are stored for 180 days from the date of recording.
I am unable to launch the RDP console even after adding RDP console on the device.
Enable the RDP console on the device. If the console is not enabled, try again.
Does console recording has any limit on file size?
There is no file size limitation for console recordings.
What is the size of a console recording?
The file size can be large for RDP recordings. Text-based operations (such as in Secure Shell and Telnet recordings) may have much smaller file sizes.
What is the recommended size for data transfer?
Data size ranging between 250 MB and 450 MB is the recommended size for data transfers.
What is the automatic disconnect time for the open remote session?
It is highly recommended not to leave a session open. Open sessions are associated with the time-out for a user platform login.
Can I paste a URL in a different browser or tab of the same browser?
No, a URL cannot be pasted neither in a different browser nor in a different tab of the same browser. A browser session is active in the browser tab first opened. Any attempt to open in a different browser or tab, disconnects the remote connection. This is a security precaution.
How do I save the commands executed on a terminal of a remote device?
Browser consoles do not offer a direct way to save the executed commands to a file. Use the clipboard to select text from the terminal and save it to a file.
What are the underlying protocols used in transferring files/data in a browser consoles?
A browser console uses Websockets with HTTP upload.
What are the audit recording formats of browser consoles?
The audit recordings are converted to M4V format.
Is RDP with NLA (Network level authentication) supported for console access?
Based on the preferences of the target machine, RDP with NLA is supported.