Four Major Updates for Proctor Labs Voice vRack Customers

CCIE Voice Candidates (Mainly those ever renting Voice vRacks from Proctor Labs)

UPDATE FOR ALL VPNs - PLEASE READ IF YOU USE Proctor Labs vRacks

Four things have been changed to give everyone a much better experience when renting Voice vRacks from Proctor Labs. I’ll list each of them briefly here, and then go into more detail on each one of them regarding what each enhancement means for you as well as what you need to do to take advantage of the new changes.

1. There is only ONE vpn group that is still functional.
2. You can now connect your VPN (Hardware or Software) over TCP port 80 or 443.
3. Network Extension Mode (NEM) is now supported for every Voice vRack.
4. ASA5505 Users VPN’s *should* now work.

Details:

1) There is only ONE vpn group that is still functional

Everyone that connects to Proctor Labs Voice vRacks and thus our VPNs, should by now, have downloaded the latest VPN configuration file (either hardware or software) from your Voice vRack VPN webpage. This is the page you come to after you login to ProctorLabs.com, and before you get to your actual vRack webpage (the page where you Load Lab Configs, Telnet to routers, Link to CUCM servers, etc).

This configuration file hasn’t changed for a long number of months now - but just to be sure - you might want to check it.

This does two things for our clients:

* Gives you a much simpler configuration. There is only 1 VPN configuration file that you will ever need to connect to our Voice vRacks - regardless of which Pod you are assigned from session to session.
* This gives every client of ours peace of mine that when they rent a vRack session from us, that they not only will they be guaranteed to connect to the correct Pod#, but there is no chance that someone else could possibly also connect to your pod and accidentally overwrite your configuration. We do this by checking each login UserID against the timeslot and pod# rented, and then place you dynamically in the proper VRF where traffic from another vRack Pod can never route to yours.

Most of you (99%) will still be able to connect to VPN just fine - as you always have. However, if for some reason you cannot connect to your VPN session, take 2 minutes to simply check the “VPN Group Authentication Name” in your Software client to make sure the name and password are exactly as follows (respectively):

vpodgroup

proctorvoice

For you hardware VPN users - I have provided the configuration below:

crypto ipsec client ezvpn IPx-Voice-vRack

group vpodgroup key proctorvoice

2) You can now connect your VPN (Hardware or Software) over TCP port 80 or 443.

Many people have reported not being able to connect their software or hardware client VPN to Proctor Labs.

Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world

• Email
• Print
• Share
  • Slashdot
  • Digg
  • Stumble
  • Reddit
  • Newsvine