Hi Guys, I've found another couple of hardware faults today this time Pod119 R4 serial0/0/0 is broken (Support and I agree it looks like a faulty cable or interface). So afterhours support moved me onto Pod122.
I log into pod122 and begin re-doing the work I had for the last hour and a bit, to find that Pod122 R11 still has it's annoying fan issue (reporting it every 30seconds to the console) and it appears R2 has a fan fault now as well. This is becoming seriously no longer funny. I'm truly suprised that Samarth/Piotr/Wayne/Doug etc.. have not yet responded to this thread and say "Wow, that's really not good we will get onto fixing that for you guys". It's making me quite concerned about the upcoming 10 day bootcamp I'm attending, I want to absorb as much as I can from the guys, not chase down hardware faults or waiting for really slow vm's to process commands. Cheers, Warrick On Sat, Jun 15, 2013 at 12:01 PM, Austin Mantz <[email protected]> wrote: > I booked a session (pod117) to review the lab layout and appliance > configurations. I also experienced many of the same pain points. **** > > ** ** > > The ISE and ACS VMs were extremely slow and I was unable to get the web > pages to load at times. **** > > ** ** > > I experienced the same DNS problem. **** > > ** ** > > The PCs and Servers were also slow and at times unresponsive during my RDP > sessions. After trying to reset the VMs I waited a while before finally > giving up.**** > > ** ** > > CAT3 and CAT4 were licensed as IP Base. **** > > ** ** > > I hope they are able to correct these issues in the future.**** > > ** ** > > Austin**** > > ** ** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Warrick Mitchell > *Sent:* Friday, June 14, 2013 10:33 PM > *To:* Daljeet SinGH > *Cc:* [email protected] > *Subject:* Re: [OSL | CCIE_Security] Online rack**** > > ** ** > > Hi Daljeet,**** > > ** ** > > I've had a few issues with the racks and I've been raising them with > [email protected] who so far have responded as well as could be > expected in most cases.**** > > ** ** > > Given I'm in Australia my sessions are always in the "after hours" support > category, I do feel for the people who are getting woken up to respond to > my emails at the moment.**** > > ** ** > > My issues have been:**** > > ** ** > > 1) proctorlabs.com on the VPN resolves to 10.200.12.151 however that is > not routed over the VPN. So to fix it I've had to put a entry in my hosts > file on my PC to the real world address of www.proctorlabs.com. I > reported it to [email protected] two weeks ago and it's still > broken.**** > > ** ** > > 2) I opened up a booking on Pod119 and found a few devices without boot > images (nothing in flash or bootdisk etc... to boot from) so an email to > support and they moved me to a new POD whilst they fixed the broken pod.** > ** > > ** ** > > 3) No wireless interfaces on any of the pods I've connected to yet, so > I've not been able to test the WLC functionality. I've been told the > wireless interfaces mapping in the VM's have dropped apparently they are > working on it. But that was three days ago and I see it's still not fixed. > **** > > ** ** > > 4) On POD 122 R11 has a fan failure, which causes it to print error > messages on the console every 1 minutes for a temperature issue on the box. > I reported that a week ago, it wasn't fixed two days ago. So it makes > debugging fun :)**** > > ** ** > > 5) Someone set a password on ASA4 which wasn't the usual ones that > proctorlabs/ipexpert use which required proctorlabs to password recover the > asa during business hours, However they did move my session to another pod > so I could continue on with my labbing.**** > > ** ** > > 6) Today, I'm trying to do Section 4 (I've got a 8hour booking running) > and the ISE has been extremely slow. It took a reboot and a further 45 > minutes to get the application engine to actually start (always saying > initalising). Not good when the first task is to get the gui up, but I did > some other tasks whilst I waited. But I am surprised it took that long, but > the guys at support said it does take a while to get started.**** > > ** ** > > So I'm glad to hear it's not just me who's having issues with the gear, > but hopefully this is just teething issues and will be resolved soon.**** > > ** ** > > Cheers,**** > > Warrick**** > > ** ** > > ** ** > > On Sat, Jun 15, 2013 at 9:03 AM, Daljeet SinGH <[email protected]> > wrote:**** > > Guys ,**** > > I wan to share my experience with online Rack, I am currently accessing > online rack and running into many issues.**** > > For one of the SW auth is not working which actually connect to WSA so m > not able to access WSA**** > > Secondly , I am accessing test PC using RDP manager and it is taking > minutes to click on one options, means this is the PC which you use to > access WSA. If PC access you cantwork on WSA tasks. **** > > ** ** > > This is not my Internet speed because I can access other routers and SW's > very fast.**** > > Also I can VPN to my office LAN and RDP access is very fast.**** > > I will give up my online rack access after struggle of next 30 mins.**** > > > SAM/IPexpert Team, > Please let me know how can we work on tasks if test PC's is worst which > connects to WSA. I don't want to comments further which affects your > buisness.**** > > ** ** > > Thanks.**** > > Daljeet**** > > > _______________________________________________ > 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
