CCIE Pursuit Blog

May 12, 2008

Booking the CCIE Lab

Filed under: Cisco, Cisco Certification, Lab Tips — cciepursuit @ 9:19 am
Tags: , , ,

I passed the CCIE Routing and Switching written exam in mid March.  I was unable to login to the CCIE database to schedule my exam.  The problem was pretty obvious to me.  My test results listed my Cisco ID as “ID Pending”.  I had used Prometric for all of my previous certification exams and this was the first time that I had used VUE.  For some reason my Cisco ID was not in their system.  I waited the mandatory two weeks and then opened a ticket with Cisco.  I provided Cisco with all of my information and it looked like the issue would be resolved soon.  Then a week went by.  I asked for an update.  Another week went by.  Then the ticket was updated and set to close.  The last entry by Cisco:

“You need to login to the CCIE database to get your information.”

WTF???  I opened the ticket because I could NOT login to that database.  This was like telling someone who had locked their car keys in their car “You need to unlock your car and get your keys so that you can use them to unlock your car.”

I spent another week seeing if I could make headway with VUE.  That didn’t work so I opened another ticket with Cisco.  Within a couple of hours my issue was resolved and I could login.  It was now about 6 weeks since I passed the written exam.

I have been planning on taking my lab in San Jose in late July.  I plugged in July 21 to see which slots were available.  The database showed me dates in October.  Oh hell no.

I went a differnt route and just plugged in today’s date.  I saw a number of very recent dates available.  The database will show you 5 dates at a time.  I saw dates in mid June and then….early October.  :(

I bit the bullet and scheduled my lab for October 2.  I’ll just have to play the same dreary game that most candidates play: keep checking the database for slots that may come available for my preferred date.

So I plugged in my information with credit card in hand.  Then I got a bit of a shock.  I knew that Cisco does not charge your card until 28 days prior to the lab.  What I did not know is that you don’t need to provide a payment method until that time. 

Lab Request Completed
 
Your lab exam has been scheduled as requested and shown below. Be sure to review the lab preparation guidelines and best of luck on your exam.
 
Please print this page and keep it for your reference.
You may also click on Certification Status (at left) to review scheduled exams.
——————————————————————————–
 
Lab Date: 02-Oct-2008
Location: San_Jose
Lab Type: Routing and Switching
Payment Due Date: 04-Sep-2008
 
——————————————————————————–

So basically, anyone who has passed the written exam can schedule a lab date with no financial obligation until 28 days before the exam.

Cancellation Policy
Candidates must read and indicate they understand the CCIE cancellation policy before a lab date can be confirmed.

Lab dates may be cancelled or rescheduled without penalty up until the payment due date, 28 days before the scheduled lab date. Rescheduling is required for any change to lab date, track or location.
 
Once the payment due date has passed, we cannot refund payments for rescheduling, cancellations or no shows. Rescheduling a lab after the payment date has passed will require an additional payment of $1400US. Our labs have only a limited number of seats and we are unable to book another candidate to replace you so close to the exam date.
 
If you decide not to attend a scheduled lab date, you will be marked as a “no show” and will not be able to re-book any date for the next 30 days.

No wonder the lab is so booked up.  No wonder that a number of lab slots come available within 28 days of a preferred date.

I have seen this viewpoint voiced on GroupStudy and I support it as well: Cisco should take payment immediately when a lab date is scheduled.  That would decrease the number of “soft” slots that are scheduled.  Cisco could still allow you to reschedule outside of the 28 day mark, but just not provide refunds.  This would decrease the amount of daily lab date fishing.

As it stands, I’ll stick with the October date.  I hope to have a good idea of where I’m at preparation wise after the Mock Lab Workshop in June.  If I get a green light then I’ll start fishing for an earlier date.  If not, I’ll just stick with my October date.
 

Question Of The Day: 12 May, 2008

Topic: RIP

r1 is a high-end router running RIP on it’s connection to the low-speed router r2.  The site engineer for r2 has noticed that the routing table on r2 is losing RIP routes.  He thinks that your r1 is sending RIP updates too quickly for r2 to process.  Configure r1 to implement a 25 millisecond delay between RIP packets.

Click Here For The Answer


Yesterday’s Question

Question Of The Day: 06 May, 2008 

Topic: EIGRP

Limit r1’s FastEthernet0/0 interface to only be able to use up to 3Mbps for EIGRP traffic.

router eigrp 100
 no auto-summary
 network 10.1.12.1 0.0.0.0
!
interface FastEthernet0/0
 ip address 10.1.12.1 255.255.255.0
 speed 100
 duplex full

Answer:

interface fa0/0
 ip bandwidth-percent eigrp 100 3

By default, EIGRP can use up to 50% of an interface’s bandwidth.  You can control that percentage with the ’ip bandwidth-percent eigrp’ command.

ip bandwidth-percent eigrp

Usage Guidelines
EIGRP will use up to 50 percent of the bandwidth of a link, as defined by the bandwidth interface configuration command. This command may be used if some other fraction of the bandwidth is desired. Note that values greater than 100 percent may be configured. The configuration option may be useful if the bandwidth is set artificially low for other reasons.

In our example, r1’s fa0/0 interface is hard-set to 100Mbps so we need to limit EIGRP to 3% of that bandwidth.

 

 

Blog at WordPress.com.