All

 

As some of you have experienced in the last few weeks, the Proctor Labs
wireless racks have been shut down on two different occasions.  First, let
me apologize for this inconvenience for those of you who had scheduled time
to use them.  I understand what that time means to you.  Here is a brief
explanation of what happened and what steps have been taken to remedy that
situation.

 

Both outages were due to network loops, one caused by a bridge connection
and the other probably by a partial Etherchannel configuration.  Due to the
way the VPN network was set up, these loops propagated to an edge router,
causing an outage for all of Proctor Labs.  Until the causes could be
determined, the wireless racks were shut down in both cases.  In the last
instance, the racks were shutdown until a more permanent solution could be
implemented.

 

In order to prevent this issue in the future, the Internet connection has
been moved from CAT2 Fa0/1 to an interface on the CME router.  This does a
few things:

 

1)      Any network storms will affect that one pod, including the CME
router.  If you experience extreme slowness in managing the pod after
configuring a device, check to see if there is high CPU utilization (if you
can access devices.)  If you are unable to reconfigure the device, reboot it
(or the switch to which it is attached in the case of the access points.)
If you saved the configuration, and thus a reboot will not fix the problem,
contact Proctor Labs Support at [email protected].

2)      All of the Workbook Volume 1 initial configurations have been
changed, where appropriate, to reflect the fact that the default route
should go to the CME IP address of 10.10.210.20.  There are many references
to the 10.10.205.20 address in the workbook, which is also on the CME
router.  But, the first IP address is the one to reference.

3)      The topology diagrams are being updated and should be posted
shortly.

4)      The Detailed Solution Guide for version 1 will not show these
changes at this time.  The biggest difference is in Labs 2.4 and 2.5.  Think
like a proctor - how could you rewrite the requirement to match the current
setup?

 

Also, if you haven't heard, we are in the process of converting over two
more racks for the CCIEW version 2.  We'll send out a note when those are
ready to go.

 

Take care.

 

 

Jason Boyers - CCIE #26024 (Wireless)

Senior Technical Instructor - IPexpert, Inc.
Mailto:  <mailto:[email protected]> [email protected]

_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Reply via email to