Not to diverge too much from the original topic, but in response to Max (and i guess by proxy Marko :-), I think I have to disagree with the idea that R&S be a prerequisite to any other CCIE track. I am first a voice guy, and "grew up" learning call manager which migrated into other voip platforms at the enterprise and service provider level. In general, the last 10 years of my work life I have had the attitude that as long as my bandwdith is clean I can do my job just fine. I've had this same discussion with some educational guys before who felt ccnp should be a prereq for ccvp, and I couldn't have disagreed with them more. I can do my job just fine with my rudimentary knowledge of routing and switching. the only real prereq for me would be subnetting and QoS. As I have looked to hire new voice engineers the only thing i really care about is whether or not they can subnet and have at least a working knowledge of QoS. In my experience I have never needed an in depth knowledge of R&S to do my job. That's why I have "network guys".
The obvious objection to this argument (which others have posted in this thread as support for R&S in general) is that voip doesn't work without layers 1-3. I could make the same argument that then every network guy be a programmer who actually rights the routing code. I certainly don't disagree with this argument but think it is a different argument then the prereq question. I will be a better more complete engineer upon completion of my R&S, hence why I'm here :-), but I don't expect that even once I have it that I will be "up to my elbows" in R&S stuff, but certainly when issues arise I can better report/troubleshoot the problem with my network engineers. The other benefit is that I would in theory not need a network engineer thus opening the door for my skills with much smaller work forces (ie startups ect.) (although I would argue that in any size network caring for the network and voice is at least a two person job). Anyways, interested to hear what you hard core R&S guys think. I'm sure there's some support for everyone having the R&S so us pesky/picky layer 4-7 guys will stop bothering you :-) <end soapbox> Peter Fabian | Senior Voice Engineer | P: 602.740.5650 On Fri, Oct 19, 2012 at 1:18 PM, N. Max Pierson <[email protected]>wrote: > I would have to agree with others on this thought. At some point, > everything will utilize the network for transport. So the R&S track is > extremely important if network is where you're thinking about taking up > a career path. > > If you're asking which is going to make you more money, I would have to say > that "cloud" and "virtualization" (as over-hyped and marketed as they are) > is where the money will be. But why not do both? :) > > I believe Marko stated at one point during a conversation I had with him > (and to which I would have to agree), that in order to do another CCIE > track, the R&S should be a prerequisite. (However, I don't want to speak > for Marko, as he may want to chime in here about this subject). Not sure if > Cisco would ever consider making this a reality though. > > -- > max > _______________________________________________ > 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 > > http://onlinestudylist.com/mailman/listinfo/ccie_rs > _______________________________________________ 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 http://onlinestudylist.com/mailman/listinfo/ccie_rs
