In a practice environment, I'd suggest using Catalyst switches as pretend hosts.... Set 'em up, test 'em out and remove the config. In the real lab, don't waste the time unless you absolutely need it! HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al. CCSI/JNCI-M/JNCI-ER VP - Technical Training - IPexpert, Inc. IPexpert Sr. Technical Instructor A Cisco Learning Partner - We Accept Learning Credits! [EMAIL PROTECTED] Telephone: +1.810.326.1444 Fax: +1.810.454.0130 http://www.ipexpert.com _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Morris, Jason L. Sent: Tuesday, March 11, 2008 11:09 PM To: [email protected] Subject: [OSL | CCIE_RS] Double checking 'Untestable' After going through some of the ipexpert labs I have some questions on methods of testing or double check some of my work. I don't really see a good way of test some of things the lab is having me do, for example some of the ACL's I'm putting on interfaces with imaginary hosts behind them or restricting subnets that aren't in the lab, some of the QOS stuff isn't really double checkable. Routing and reachablity is the easy part it would seem at least I can look at routing tables and ping. But the 'untestable' things seem to be what would kill. Does anybody have a good strategies or is it just know the stuff so well you don't need to double check? Jason Morris
