Management Console

From PrgmrWiki
Jump to: navigation, search

When you sign up, you give us an OpenSSH format public key. This key gives you access to simple text-based menu that lets you turn your domain on, off, and allows you to connect to the serial console. If you need help on how to make a key, please refer to Making an ssh key.


Logging in from an OpenSSH Client (Linux, Windows Cygwin) or Terminal (OS X)

To login to the console, use the command

ssh -i <secret key> <hostname>@<hostname>.console.xen.prgmr.com

The hostname is the name assigned to your VPS.

If this is your first time logging in, use the server public key list to verify the server fingerprint based on IP address.

Note for macOS: Beginning with macOS Sierra (June 2016), DSA keys are no longer supported. Use Terminal to generate a new RSA ssh key and upload your new public key to your server.

Logging in via PuTTY Client (Windows only)

If you are unable to connect, please verify your version of PuTTY is up to date (0.64 or newer). You want to be using 0.64 or newer anyway since private keys were not completely wiped from memory before 0.64.

Starting from initial defaults the PuTTY Configuration settings are as follows:

  • "Session:Host Name" needs to be <vpsname>.console.xen.prgmr.com, example "icecream.console.xen.prgmr.com" for a VPS named "icecream"
  • "Session:Connection type" needs to be SSH
  • "Connection/Data: Auto-login username" needs to be <vpsname>, example "icecream" for a VPS named "icecream"
  • "Connection/SSH/Auth:Private key file for authentication" needs to point to the .ppk file associated with the public key used.

Under "Session:Saved Sessions", name this session "Management for <vpsname>.xen.prgmr.com" and save. Click open to connect to the management console.

You may use this registry file as a starting point, however PLEASE open it with a text editor and review it before importing. Use at your own risk.

If this is your first time logging in, use the server public key list to verify the server fingerprint based on IP address.

Using the Console

There are two versions of the console currently in production.

Latest Management Console

At log in, the initial menu for a service named 'nite' is shown below:

Main Menu - nite

Current status:
	nite is not running.

Wiki at http://wiki.prgmr.com
Please contact support@prgmr.com with any issues accessing your machine.

Options:
1. out of band console (press ctrl-] to escape, not resizeable)
2. create/start, opens OOB console (try this if the machine is not running)
3. shutdown (requests clean shutdown, forces off after 4 min)
4. force power off (destroy/hard shutdown)
5. reboot (shutdown + start)
6. set bootloader or rescue mode
7. view/add/remove ssh authorized_keys
8. view/edit reverse dns
9. install new OS image
a. system details

0. Exit
R. refresh

enter selection>

Option 1 accesses the serial console when the VPS is running. Like other serial consoles, often you see nothing until you use ctrl-c or hit return, at which point you should see the normal login prompt

CentOS release 5.2 (Final)
Kernel 2.6.18-53.1.14.el5xen on an i686

nite login: 

To exit the console once at the login screen shown above in most terminals, the escape sequence is ctrl+].

Option 2 starts the VPS if it's not running and opens the serial console.

Option 3 attempts to nicely shut down the VPS. It sends a shutdown request to the server, like briefly pressing the power button of a physical machine. If the system does not shut down within 4 minutes, it will force a shutdown (like Option 4).

Option 4 forces the VPS to shut down, like holding down the power button of a physical machine for several seconds.

Option 5 stops and then starts the VPS. It is like a combination of Options 3 and 2, in that it will force a shutdown after 4 minutes.

Option 6 changes what is used to boot the VPS. This is the option that differs most between different virtualization types (see below).

Option 7 adds or removes ssh keys authorized to access this menu. It will not change the keys within the VPS as we have a policy of not modifying user disk images.

Option 8 modifies reverse DNS, i.e. the DNS name that comes back from typing 'host <myip>' .

Option 9 installs a new OS image. It will repartition and reformat before the install. The currently authorized SSH keys may optionally be added to the root user as part of the install.

Option a brings up a system information panel, as below:

Command result: 
	Virtualization mode: Paravirtualized
	Memory: 128 MiB
	VCPUs: 1
	Total disk: 3 GiB
	IPs: 192.168.0.91
	Last installed OS: Debian Wheezy - 64 bit
	Boot option: PV-GRUB - 64 bit
	Boot arguments: (hd0,0)/boot/grub/menu.lst

Option 0 ends the ssh session.

Option R refreshes this menu.

Option 6

Use these menus to change the way the VPS boots. By default an HVM VPS boots from disk, while a paravirtualized(PV) VPS boots using either PV-GRUB or GRUB2.

Boot options - HVM

In HVM systems, pressing option 6 will bring up the following menu:

Set Boot Options - nite

Configured to boot from disk.

Options:
1. Boot from disk
2. Linux-based Live Rescue
3. Linux netboot installers - install mode
4. Linux netboot installers - rescue mode
5. BSD installers

0. Return to main menu
R. refresh

enter selection>

Boot options - Paravirtualized

In PV systems, pressing option 6 will bring up the following menu:

Set Boot Options - nite

Configured to boot 'PV-GRUB - 64 bit' with arguments '(hd0,0)/boot/grub/menu.lst'

Options:
1. GRUB legacy(pv-grub)
2. GRUB2
3. Linux-based Live Rescue
4. Linux netboot installers - install mode
5. Linux netboot installers - rescue mode
6. BSD netboot installers

0. Return to main menu
R. refresh

enter selection>

Legacy Management Console

Once you log in, you see this menu (here, the VPS is called cnryfield:)

Name                                        ID   Mem VCPUs	State	Time(s)
cnryfield                                  218  1024     1     r-----    1898.8

    Wiki at http://wiki.prgmr.com
    Please contact support@prgmr.com with any issues accessing your machine.

    Options for "cnryfield"
    1. out of band console (press ctrl-] to escape, not resizeable)
    2. create/start, opens OOB console (try this if the machine is not running)
    3. shutdown (requests operating system to shut down)
    4. force power off (destroy/hard shutdown)
    5. reboot (requests operating system to reboot)
    6. swap i386/amd64 bootloaders currently "i386"
    7. view/add/remove ssh authorized_keys
    8. set reverse dns
    9. swap pvgrub/grub2 bootloaders currently "pv-grub"

    0. exit

Option 1 accesses the serial console when the VPS is running. Like other serial consoles, often you see nothing until you use ctrl-c or hit return, at which point you should see the normal login prompt

CentOS release 5.2 (Final)
Kernel 2.6.18-53.1.14.el5xen on an i686

cnryfield login: 

To exit the console once at the login screen shown above in most terminals, the escape sequence is ctrl+].

Option 2 starts the VPS when it's not running.

Option 3 attempts to nicely shut down the VPS, like hitting the power button of a physical machine briefly.

Option 4 forces the VPS to shut down, like holding down the power button of a physical machine for several seconds.

Option 5 requests the VPS to reboot. Note that if your IPs have changed since the last time you started the machine, you will need to do a shutdown (3) or destroy (4) instead of just a reboot.

Option 6 should be used if you are reinstalling your OS and are switching from 32-bit to 64-bit mode. Switching from 64-bit to 32-bit mode is not possible without contacting support.

Option 7 adds or remove ssh keys authorized to access this menu. It will not change the keys on your VPS as we have a policy of not modifying user disk images.

Option 8 allows you to modify reverse DNS, IE the dns name that comes back when you type 'host <myip>' .

Option 9 switches between legacy grub (pv-grub) and grub2.

Option 0 will end the ssh session.