Thanks Michael, yes I was referring to v2. It then means that it is only the R&S lab that have all the bells & whistles for now...... open-ended questions, cisco assessor labs, trobleshooting section, etc...
Tech Guy ----- Original Message ----- From: Michael Ciarfello To: Tech Guy ; [email protected] Sent: Sunday, April 19, 2009 9:48 PM Subject: RE: [OSL | CCIE_Voice] Valid CCIE Voice Troubleshooting Scenarios V2? None intentional according to ask the expert over on netpro. But if sometihing were to go wrong, then anything. V3? (after July 15th) No one knows yet, but I'd say anything. Customers don't tell (even if they know and properly documented their changes if they changed something) So just about everything is fair game. People during the last two or so Networkers sessions made strong arguments that troubleshooting should be part of the exam since it's reflective of real-world scenarios. I would gladly take anything a proctor throws at me compared to some of the wacky crap I've had to troubleshoot over the years. I think if we know the material well enough and how it's supposed to work and react, troubleshooting should not be too bad. I think the big challenge will be to keep a clear mind, relax and think. oops. After re-reading, You were referring to v2. ------------------------------------------------------------------------------ From: [email protected] [[email protected]] On Behalf Of Tech Guy [[email protected]] Sent: Sunday, April 19, 2009 7:41 AM To: [email protected] Subject: [OSL | CCIE_Voice] Valid CCIE Voice Troubleshooting Scenarios I am kind of curious as to any troubleshooting Scenarios one can encounter in the Voice Lab. I will appreciate if someone can shed some more light in this area without going into NDA protected info. I am trying to be the devil's advocate here, please wear that hat for a moment and see, if I am taking too far, or not far enough and please contribute. I will apprecaite if Mark Snow, Vik and the guys from IPExperts can contribute to this. SQL: What can they possibly do in the SQL server? -Maybe stop the service. -May disable the service altogether. -May go into Computer Management/Active Directory and Disable an account that is used by on of these services/product. -They cannot delete any table, databases, users, roles, etc----so I believe, or can they? -Can the rename a table, database, user, roles and you have to figure it out yourself? -Altering permissions & rights in SQL database. Windows -Disable a vital service in window. -Disable vital accounts in Computer Management/Active directory. -Point say, Tomcat to a totally wrong directory in IIS & you left to figure it out and fix it. -Put IPMA or IPCC url in Internet Exporer Restricted Site List. -Leave an account enabled, put remove some priviledges, eg removing the Administrator user from the Administrators group. -remove certain priviledges from certain directories or folders. IPCC -Since you are going to own this from start, it is hard to see what they will throw at you here. -Or can they mess-up the idap, disable the service, etc.??? CUE -Same with IPCC, or is there anything here? Topology -anything can happen here. -last night in one of my Proctorlabs Pods; the diagram & instructions clearly said, HQ Router was connected to 6509 port XX; as usual, I configured port XX, but things were not working great; did 'sh cdp neighbor' on HQ Router found out, 6509 is being reported from a different port. Went back to 6509, configured the correct port in the correct VLAN, Trunk, etc.... ATA/VG248 -Question said ATA shld register to CCM with DN 1009; but ATA have an H323 image. -Set ATA or VG248 port to 100 Full Duplex. -Configure ATA/VG248 ports as trunk ports. CCM Service Parameters: -This is a can of worm; hope they will stay clear of this page or at leaset do something will introduction a noticable error. -Same with Enterprise Parameter Page Unity -Messing with Accounts & User rights. Are mine missing any section or info and are mine taking this too far? Another question is: Will you know you have a problem? or the problem will be very subtle and you have to go looking for it e.g. remarking signaling traffic in service parameter page down to CS1? And after configuring your scavager class, you discover that your voice traffic works great sometimes and sometimes it does not work. In the R&S lab, there is no conspiracy theory; even if you did not read the instructions (do not know why you shouldn't); you will know you have a problem because things will not just work. However, you will be clearly told that there is a troubleshooting section, you will be told the number of potential problems that have been injected and there is points awarded for rectifying each problem; is it the same in the Voice lab? Thanks. Tech Guy
