|
|
How can I use my CMS to access Managed Console Servers and their Managed Devices?
The CMS appliances (i.e. the VCMS virtual appliance or the CMS6100 physical appliance) provide a selection of pathways for accessing remote Managed Console Servers (and their attached Managed Devices):
- SDT Connector access points are embedded in many of the CMS "Monitor" screens. So with a "point-n-click" you can download a pre-configured SDT Connector applet to run on your client PC. This will connect specific target applications on your client PC to the Managed Console Servers or Managed Devices. This connection is proxied via the CMS
- The CMS has browser proxy facilities, with a web browser run in the CMS. This enables you to monitor and manage Managed Console Servers and Managed Devices from any location
- Using the CMS you may also schedule batch commands to run on one or more Managed Console Servers
Running an SDT Connection from your client PC
Many of the hosts displayed on the Monitor:Services or Monitor:Host screens have a Connect, Manage Power, View Status or View Logs button in the Status Information.
- Click on this button and you will be connected to the relevant screen on that Managed Device or Managed Console Server
- Your browser will download a configured SDT Connector Java application from the CMS and it will run on your computer. This SDT Connector is preconfigured with the gateway details (that being the Managed Console Server, proxied through the CMS ) and the host details (which will be one of the Managed Devices attached to the Managed Console Server, or the Managed Console Server itself)
- SDT Connector will then log you into the SSH server embedded in the Managed Console Server, using the credentials of the user currently logged in to the CMS. Then, if appropriate, it will SSH tunnel connect you through to the target Managed Device
- Lastly SDT Connector will automatically load and run the appropriate application (service) on your computer that is needed to connect to the appropriate Managed Device or Managed Console Server screen. This service could be a text-based console tool (such as SSH, telnet, SoL) or a browser/graphical/network tools (such as VNC, RDP, HTTPS, HTTP, X11, VMware, DRAC, iLO).
For more details refer to the User Manual
Running a proxy browser on the CMS
Again the CMS provides a simple path for accessing Managed Console Servers and their Managed Devices.
- Click Manage -> Access Console Servers. The Managed Console Servers that the current user has access to are listed under Access to Managed Console Servers. If the current user has 'user' or 'admin' group access on a console server, they are deemed to have access to that console server
- In the Management Console column click Browse via CMS. This connection is proxied via CMS, so the console server is still accessible even if firewalled, failed over to a private connection or otherwise inaccessible from the WAN. When browsing via a proxied connection, the following message is display in the Management Console header:
This Console Server is being accessed via CMS. Click here to return to CMS
- You can also click Connect in the Command Line Shell & Managed Devices column to start an SDT Connector session via CMS to the console server. This downloads a configured SDT Connector (as described in the previous section) and launches a command line shell session to the console server.
Using CMS to schedule batch commands to run on Managed Console Servers
Using CMS you may schedule batch commands to run on one or more Managed Console Servers.
- Select Manage: Command Console Servers to display the list of Managed Console Servers that can be commanded by the current user. These are the console servers on which the current user has 'admin' group privileges
- Select the Managed Console Server(s) to command
- Select the Command to schedule:
- Reboot: Soft reboot the selected console servers
- Shutdown: Halt the selected console servers. After being shut down, manual intervention in the form of a physical power cycle is required before the console server becomes available again
- Firmware Upgrade: Perform a firmware upgrade, loading firmware from a given http:// URL, e.g. http://www.opengear.com/firmware/acm500x-x.y.z.flash
- Modify User: Specify the Username to modify, the Modification to apply. Currently supported Modifications are Lock Account and Unlock Account where Lock Account prevents a user from logging in to the console server itself, or accessing Managed Devices using SDT Connector via the console server. Use Unlock Account to undo this modification.
- Click Schedule Command. The results of the schedule commands are displayed under Monitor: Services in the Status Information of the Managed Console Server's Console server command
|
