Hello Dan, You are not alone, I had same experience. Finally setup my own:) booked lab for next month.
On Wed, Jul 31, 2013 at 6:38 PM, Dan Gericke <[email protected]> wrote: > Hi everyone, > I'm not sure if I'm the only one that constantly has issues with the pods > or if I'm the only one complaining about it, but once again I had issues > today. Yesterday it took me almost 1.5 hours to get pod 120 to a point > where I could log into the PC, and AD servers. Sometime before the 1.5 > hour mark I can actually RDP to them, but it takes quite a while before I > can actually click anything. > > Today, I'm doing Section 4, the ISE labs on pod 121. To me, the ISE is > extremely slow. I'm at the 2 hour mark right now, and I've barely created > the certificate in Lab 1. > It took nearly an hour for me to even be able to SSH into the ISE box(That > includes reverting the pod, then loading the configs, then waiting), which > is ridiculous to begin with. But after you update the domain name, you > have to wait for the services to start. I started a timer after the last > service stopped(which I estimated took almost 20 minutes), and it took 17 > minutes to start all the services again. Then as soon as you go into the > GUI to create the certificate, it has to restart the services again. I'm > now at almost 30 minutes of waiting, and I can finally log into the GUI > again. > > When I'm waiting, I wait on the application server process: > ISE Database listener is running, PID: 12356 > ISE Database is running, number of processes: 27 > ISE Application Server is still initializing. > ISE M&T Session Database is running, PID: 13178 > ISE M&T Log Collector is running, PID: 14385 > ISE M&T Log Processor is running, PID: 14588 > ISE M&T Alert Process is running, PID: 14228 > % WARNING: ISE DISK SIZE NOT LARGE ENOUGH FOR PRODUCTION USE > % RECOMMENDED DISK SIZE: 200 GB, CURRENT DISK SIZE: 64 GB > > Even after it starts, the web gui is anything but fast. I often have to > reload the page or wait 1-2 minutes+ for it to load. > > Are any of you also experiencing this kind of thing when you are working > on ISE labs? It seems to me that whatever VM server is being used, it's > excessively choking. It should not, by any means, take this long to > initialize things. This issue turns into a ton of wasted lab time, so its > very frustrating. > > Here's a sample of my ping statistics to the ISE box. > --- pod121ise.proctorlabs.com ping statistics --- > 393 packets transmitted, 393 packets received, 0.0% packet loss > round-trip min/avg/max/stddev = 362.610/621.341/3963.285/453.191 ms > > > By the way, I installed my copy of ISE on vmware just now, and went to > create the self signed certificate. It took my VM all of 1 minute and 30 > seconds to restart the services fully. > Thanks for any feedback. > -Dan > > _______________________________________________ > 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 >
_______________________________________________ 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
