Lab Rack Access Overview

Expand all



Contents

Lab Rack Access Overview

Last updated: March 23, 2019

Accessing the Routers & Switch

Option A: Telnet over the Internet

Access to the routers and switch's CLI is through regular telnet access over the Internet. To log in to these devices, stelnet to racks.ine.com with the telnet client of your choice, such as PuTTY or SecureCRT. When the login prompt appears, enter the rack name for your username and rack session password for the rack you have been assigned, and you will see a telnet menu to connect to the physical devices in your rack.

Option B: Telnet with a web browser via the Control Panel

With this option, you can access the routers and switch's console via the Control Panel on rentals.ine.com. Open a web browser and navigate to your current rack rental Control Panel at rentals.ine.com. From the Device Management tab, click the router or switch that you would like to access and select Open Telnet from the device menu. This uses a HTTP-to-Telnet proxy server with HTML5 and is provided for those customers who are not able to use Telnet from their location due to network restrictions. It has inherent limitations such as the inability to scroll up and should only be used if you have no choice.

More information on both options can be found in the section Telnet Connections using Control Panel.

Accessing the Windows Desktops

Option A: Direct RDP via the SSL VPN connection

The preferred method to access any of the Windows VMs is to connect to your rack using the Cisco AnyConnect SLL VPN client and then use the Microsoft Remote Desktop client on your local computer.

Option B: RDP with a web browser via the Control Panel

Access to the Windows machines can also be achieved through the rack Control Panel from rentals.ine.com, by clicking Control Panel next to your active rack session, and then clicking the Remote Desktop tab in the right pane. Usernames/passwords for Windows are also administrator/cciecollab. Like the Option B for using Telnet, this has some inhernet issues over using direct RDP and should only be used by those that can not connect to their rack using Cisco AnyConnect. This option uses a HTTP-to-RDP proxy server and HTML5 to allow you to control the remote desktop of the Windows VMs. You will experience higher latency and will consume more bandwidth versus the direct RDP option.

Do not make any changes to the MGMT NIC or you will lock yourself out of the VM, but feel free to make any other changes you want to on these machines; their disks are non-persistent and will revert to the previous snapshot upon power cycling. If you do lock yourself out of a VM, simply return to the rack control panel and use the Reset Config option to revert the VM to its default configuration. See the Control Panel Overview section for more details.

Accessing the Cisco Collaboration Servers

Option A: Direct browser connection the SSL VPN connection

The preferred method to access any of the Cisco servers is to connect to your rack using the Cisco AnyConnect SLL VPN client and then use a web browser on your local computer to conenct deirectly to the management GUI of the Cisco appliance.

Option B: RDP with a web browser via the Control Panel to a Windows VM in the rack and then use a browser on the remote desktop

Access to the Cisco server's management GUI can be achieved by using oen of the Windows machines in the rack as a jump box. Once you connect to the Windows VM using the Control Panel, use one of the web browsers on the desktop of the Windows VM to then make a HTTPS connection to the Cisco appliance.

^ back to top