GlobalConfig.net header image 2

IPexpert CCIE Security Section 19 Lab

January 27th, 2009 · 2 Comments

Welcome back!

Well I just wrapped up my section 19 lab.  Wow.  It was tough.   Even though it was tough I can’t help but feel satisfied.  You see I am taking a new approach to studying.  Here is what I do:

  1. Read the entire Mock lab
  2. Read the entire Mock lab and take notes for each task of either what I would type or what I would need to do to make this work.  This includes notes like “This should be done AFTER task XXX.”
  3. Work on the lab starting where it is logical to start.

I did that with this lab.  I have 3 1/2 pages front and back of notes.  When I am done I crack open the Solution in the Proctor Guide and start checking my work.  I’m doing pretty good, with the exception of some really dumb mistakes and a few “Thats New!” topics that I come across.

Here are some things I learned in this lab:

  • Sometimes an ACS Server just needs reimaged.  I will not spend too much time on it in the actual lab.
  • There is a really weird “established” command on that ASA that does what you would expect the MPF and FTP inspection to do, but for some reason they wanted this particular command in this particular lab.  I used it to allow IDENT in ftp to come back into through the firewall.
  • Another command that is interesting in its implimentation is “scheduler allocate.” This command allocates time in microseconds to spend on fast switching within any one network interrupt context and guarantees the minimum number of microseconds to spend at the process level when network interrupts are disabled.  The task I had required allocating 2.5% of CPU time for OSPF and other processes.  The solution shows scheduler allocate 39000 1000. The way you figure this is that 1000 is 2.5% of 40,000.  The number you use just has to keep the ratio.

    schedule_allocate_example

  • I forgot that config commands are not authorized unless you add the command aaa authorization config-commands
  • There is a VPN3k “on-a-stick” that doesn’t seem practical but is an intersting configuration.
  • Using the DocCD to find IDS/IPS log identification numbers are useful when the task just says to disable things like “Bomb” Attacks.

I’m sure there were a few more things but that is all I remember.  I didnt even try to do this in 8 hours.  Instead I booked rack time 24/7 and just worked on it when I was able to.  I found it easier to focus.  If I went away to watch TV for a bit I would feel guilty and head back to the labs.  If my wife needed help with the kids I didn’t feel guilty walking away for 2 or 3 hours.  I knew the configs would be just fine until I got back.

Now that I have finished that one I’m going to do the 1-Week Lab Experience -Exam One, which is part of the “Last Mile” deal right now.  Use the coupon code from my previous post on the program to get $50 bucks off.

Happy Labbing!

Related posts:

  1. CCIE R&S Studies- May 27th 2009 Today, as I stare at my challenge of CCIE in...
  2. Recap of my journey CCIE Security I know most of you have heard already, but if...
  3. CCIE Security Adds Core Knowledge Questions For a short while now those working on routing and...

Related posts brought to you by Yet Another Related Posts Plugin.

Tags: CCIE Security · IPExpert Labs

2 responses so far ↓

  • 1 Simon Baumann // Feb 1, 2009 at 4:17 am

    Great post! I’ll try to adopt it when I’m working in Proctorlabs.

  • 2 Calin // Feb 10, 2009 at 11:31 pm

    I don’t have too much experience with ASA, but on the FWSM (and I think ASA/PIX/FWSM are basically the same stuff) I’m having all the time problems with inspect / establish command. Lately the FWSM was crashing from the inspect dns, when a large amount of DNS packet where inspected. I’m not very happy with this product. I have to try ASA to see if there is a difference in behavior.
    Keep on the good work!

Leave a Comment