In line (like a firewall)... >>> "The Long and Winding Road" 10/09/02 01:46AM >>> in line ( like the skates )
""Ken Diliberto"" wrote in message news:200210090539.FAA09794@;groupstudy.com... [snip] > > It's difficult to try keeping a "hands-off" approach to letting a > vendor install a major piece of equipment in the core of MY network. > Maybe you know how it is... watching an engineer (CCNP with some > experience) who is supposed to know what he's doing but brings down the > network instead. Add a CCIE with a few years experience to the mix, > three more tries with two of them resulting in network outages. CL: Let he who has never brought a network down by accident ( or otherwise ) cast the first stone. Did I ever tell you the one about the newly minted Novell admin who decided to have some fun one afternoon unloading and loading NLM's? KD: The difference is, we hire consultants to make it work. It's my job to break it and I don't like to share. :-) KD: NLM's are designed to be loaded and unloaded. Was this a problem??? ;-) > > The suggested configuration for our first 6500 (a 6513 with dual > Sup2/MSFC2/PFC2) was to run in HSRP between the two MSFCs. (For those > who don't know, an MSFC - Multiservice Switch Feature Card or something > like that, is a routing module on the switch supervisor). We are > running IP, IPX and AppleTalk. What they didn't tell us was we had to > keep the configurations sync'ed between the two MSFCs otherwise there > would be problems. Config Sync doesn't support AppleTalk. Guess > what... we had problems. We're now running SRM. CL: serves you right for running AppleTalk. KD: Ouch!!! That hurts. We're using things like Cisco stating Apple Talk will not be supported in EIGRP as a tool to migrate away from it. Several issues to overcome first, though. [snip] > > It seems our vendor keeps shooting itself in the foot. Their engineers > keep doing things that prevents them from earning any respect from us. > On a positive note, I know one engineer with that company who I do > respect. Too bad they keep him in design. :-) CL: seriously, having spent wonderful quality ( but far too little ) time with the likes of Marty Adkins and Val Pavlichenko, not to mention a young guy at work I'm beginning to think is in this class, I suspect that there are very few top level network engineers in the world, and a lot of wannabe's. CL: Not everyone can be a brain surgeon. Most of us are just GP's. Of the CCIE's I have met, many are in this latter category as well. Let alone us CCNP / CCDP types. ;-> We all just do the best we can, and live in fear that something we touch is going to break and we won't know how to fix it. KD: I'm not a brain surgeon. I'm a podiatrist. Or should that be... never mind. :-) KD: I know what you mean about talent levels. A brief technical talk with someone who really knows their stuff is very revealing. At a previous job our Cabletron SE knew more about the insides of Token Ring and the different flavors of Ethernet (not to mention FDDI) than I'll probably ever know. He also knew how to present it. KD: Working for a company IT group, I don't worry about breaking things. I tell my management that it could happen (and times it probably will happen) and go one with my job. As for knowing how to fix something I break, I'm not sure if that's happened yet. Usually backing out a change works. I do know what you mean, though. Definitely a down-side to consulting work. KD: Funny thing. I mentioned our vendor shooting themselves in the foot. Someone on this list (don't worry... I'll find out who it is) told the project manager about my message. The PM called my manager. Talk about hurting respect and burning bridges. Maybe we'll see Project Manager #5 in the near future. (I'm hoping he gets this message since he's too cowardly to talk to me directly). [snip] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=55474&t=55064 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
