IPKVM

We have 3 Belkin F1DE101H IPKVMs:

https://kvm1.johncompanies.com (@ i2b)
https://kvm2.johncompanies.com (@ castle)
https://kvm3.johncompanies.com (@ i2b)

Current Locations:

kvm1: i2b Cab 4 col01224 6/14/14 obc-c.sea-incorporated.com
kvm2: castle Cab 3-5 virt13 9/15/14
kvm3: i2b Cab 8 ? ?

Manual: http://cache-www.belkin.com/support/dl/p75075_f1de101h_man1.pdf

Each kvm is accessed via a web interface. With the KVM you have keyboard/mouse/video virtually in a java applet. You can also mount up ISO images that then appear as a usb CD-ROM drive to the server/os.

The KVMs have 4 cable/plugs: 1 video, 1 USB, and 1 PS/2 keyboard, 1 PS/2 mouse

There are also "monitor" ports on the KVM, allowing someone at the data center to piggy-back on the KVM, seeing what the KVM sees (since the KVM will be occupying all PS2/video ports on the server).

We use these KVMs internally when we need to load/rescue a server, and we also provide them to customers so they may load, rescue, troubleshoot their dedicated servers. We NEVER allow VPS customers to use the KVMs to access the host machine on which their VPS runs.

The location and server to which each KVM is attached is located in a file on mail ~user/kvm This is usually in screen p4 in the mailboxes screen. When we know a KVM is no longer in use, we place a "DONE" after its entry.

There are a handful of options in the KVM we will modify on a regular basis:

KVM Console: this will launch the viewer window- where you may interact with the server as though you were standing in front of it with a monitor/keyboard/mouse

CD-ROM Image: on this screen we setup an ISO image to appear as a local USB drive to the server/OS. The options we provide are: Share host: 69.55.230.10 (castle) or 69.55.229.4 (i2b)
Share name: data
Path to image: the file name of the ISO
User, Password: (leave blank)
Any ISO which you place on backup2:/data2/iso (castle) or backup3:/data/iso (i2b) will be available to the KVM for mounting.

We periodically take this list and publish as http://johncompanies.com/knowledge/isos.html so customers know what is available. However, not all images are available at each location, as noted.

If you or the customer wants to use their own ISO, we can either download that to the backup server or they can make their local CD-ROM drive appear on the server by using Belkin drive redirection software: http://johncompanies.com/knowledge/Drive Redirection 1.0.5 Belkin.exe

Users: each time we allocate the KVM to a new customer, we reset the password for the guest user. You may use anything, but usually we just use the customer's CID: col0xxxx. To change, select 'guest' from the 'Existing users', enter password (and confirm) and click 'Modify'. Note, the guest user has a lower level of access, for instance they cannot change KVM settings, like Keyboard/Mouse

Keyboard/Mouse: on this screen we can adjust which emulation the KVM should make available to the server- USB or PS/2 or Auto. To change the setting, select Auto, USB or PS/2 from the 'Host Interface' dropdown. Click 'Apply' at the bottom of the screen to save. DON'T CLICK 'Update' - it won't save the setting. The customer, using the guest account, cannot modify this.

Unit Reset: this screen gives options to reset parts of the IPKVM or the entire IPKVM. Usually we are resetting PS/2 or USB to get the keyboard to respond- rarely does the entire unit need to be reset.

Notes regarding assignment

This is a floating KVM - we move it around on an as-needed basis. With 2 KVM's at i2b and 1 at castle, usually we don't have conflicts where multiple customers need to use it at exactly the same time. Castle does have their own IPKVM which we can also use.

The steps for assigning our KVM to a new customer are:

1. determine which KVM to use. Which KVM's are free/done/available? Note, we don't always mark a KVM "D(one)" (in the ~user/kvm file) since customers don't always say when they're done. So, you have to use a bit of judgement to know who was using it last and what for. If it was for a reload, they may still be using it. If it was to get back in after a crash or network config mistake, chances are they're done and you can take it. If in doubt, login to the KVM and see if it's actively being used.

2. reset the guest password. This locks out the current (soon to be previous) user- we don't want them to be able to login to the KVM and control someone elses server.

3. contact the data center asking them to move the kvm. Usually this will take the form of: "please move kvmN from cabinet A to col0XXX in cabinet B". We usually email castle and use http://portal.i2bnetworks.com to notify i2b, but if you or the customer is on a rush, call the data center- i2b can be especially slow to handle tickets. castle/i2b phone numbers are in the ~user/kvm file on mail.

4. confirm the KVM is up- usually we ping it and watch for it to start pinging again, it takes about 1min to boot up after being plugged in. Login, make sure the keyboard is working- if not adjust input and/or reset as necessary (Keyboard/Mouse, Unit Reset).

5. contact the customer and send them the kvm email from pastes- EDITS: kvm, password, IP of share host: 69.55.230.10 (castle) or 69.55.229.4 (i2b)

Notes regarding usage

Occasionally, even after plugging in the KVM and it appears it has power, it will not come up- the nic lights don't light up. If this happens ask the noc staff to pull power and/or use a paper clip to reset the unit.

Some servers do not have legacy ports, therefore if the setting in Keyboard/Mouse was PS/2, the keyboard would not work. Conversely, some OSs don't recognize USB keyboards, you'd want to force PS/2. Usually this takes effect right away, but occasionally you'll want to reset USB and/or PS/2 via Unit Reset.

FreeBSD in particular will not recognize a PS/2 keyboard which wasn't present at OS boot. So you will need to either try USB first, or reboot to get PS/2 recognized.

If ever things aren't working (no vid or kbd not working), ask the tech to confirm the cables are not plugged into the monitor port (the monitor ports are labeled "console", and are left of the "CPU/KVM" ports- which go to the server).

To get BIOS to recognize the USB CD-ROM, you may need to tweak several settings in the BIOS screens. Options vary per hardware, some options to check: Boot optical: enable
Boot removable: enable
Boot network: disable
USB boot: enable
Boot USB first: enable

In the boot menu, make “Belkin Virtual” (or whatever it's recognized as) first in boot order. In order for the BIOS to see the CD-ROM, it must be configured via the IPKVM before you reboot the server

Usually a frozen server will not respond to a ctrl+alt+del (both from kbd sequence and also from the button in the KVM applet), just like it wouldn't if a real kbd was attached.

If you logout or timeout you'll need to remount the image. Some OS/MB combinations don't like the USB drive method. In these cases we suggest using the ftp/netinstall setup option to avoid having to access the CD/USB drive. OS's known to have this issue: Debian, FreeBSD

If you need to communicate with the customer, 2 people can use the KVM applet at the same time and there's a chat window available from the options drop down menu.

If ever you find that you are locked out of keyboard access after attaching an ISO image (this sometimes happens on modern motherboards which do not have any ps/2 connectors) you can usually get keyboard back by doing one or more of the following:

• reset the usb (in the reset menu)
• "reactivate" the ISO image
• reset the entire kvm
• sometimes attaching a physical keyboard to the system (then rebooting with that keyboard attached) solves the problem
• use 2 IPKVMs: 1 providing the ISO and the other acting as video/mouse

3wfirmware.iso

This is a special custom-made iso that we place various drivers and flashing programs on so we can easily flash bios's without needing to go to the DC with a USB or CD drive. To place new software on the iso:

Copy the iso file over to a server that can mount it (linux-based box, i.e. virt16);

scp backup2:/d2/iso/3wfirmware.iso /tmp/3wfirmware.iso

mount it up:

mount -t vfat -o loop /tmp/3wfirmware.iso /mnt/usb/

copy files over to /mnt/usb

umount it

umount /mnt/usb

copy back to backup server:

scp /tmp/3wfirmware.iso backup2:/d2/iso/3wfirmware.iso