Re: You can call yourself and internetworking engineer when . . . .
A couple years ago I was investigating a problem with high CPU utilization on a farm of 7500's at a very large wall street brokerage, (thank god it was saturday), things were pointing to excessive UDP traffic. So it seemed like a good idea to get a quick dump of the traffic details by logging the output of debugging UDP. Believe it or not, I was not recovering from a major head injury. Maybe a brain cloud... It earned me the nickname "the debug kid". I still haven't heard the end of it. Erik Mintz - Original Message - From: Ben Lovegrove [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, August 08, 2000 3:19 AM Subject: "You can call yourself and internetworking engineer when . . . ." | (tongue firmly in cheek) | | I have this theory that you can call yourself and internetworking | engineer when . . . . | | 1. You have run a debug command on a customer router while | investigating a performance problem, or perhaps a security issue, and | you have caused the CPU to exceed 100% and the router has hung/crashed. | | 2. You have edited an ACL remotely and reapplied it only to find you | have blocked all traffic including telnet from your desk and you are | now locked out. | | 3. In both of the above scenarios you have made up some story for the | Help Desk/1st Line Support and asked them to get the customer to reboot | the router, claiming that "a reboot may help the performance problem . | . blah . . blah" | | 4. In each of points 1 2 the customer in question is a major account | that has threatened legal action against your company for failing to | maintain SLAs, or to close the account altogether. | | Does this sound familiar to anyone? Have you every felt that cold | feeling in the pit of your stomach when you entered a command and the | screen froze? Did you blame hardware/software/customer/gremlins i.e. | anybody and anything but not yourself? | | ;-) | | Ben | | | | = | Ben Lovegrove, CCNP | Redspan Solutions Ltd | http://www.redspan.com | Cisco: Products, Training, Jobs, Study Guides, Resources. | | | Do You Yahoo!? | Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk | or your free @yahoo.ie address at http://mail.yahoo.ie | | ___ | UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html | FAQ, list archives, and subscription info: http://www.groupstudy.com | Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] | ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: You can call yourself and internetworking engineer when . . . .
A couple years ago I was investigating a problem with high CPU utilization on a farm of 7500's at a very large wall street brokerage, (thank god it was saturday), things were pointing to excessive UDP traffic. So it seemed like a good idea to get a quick dump of the traffic details by logging the output of debugging UDP. Believe it or not, I was not recovering from a major head injury. Maybe a brain cloud... It earned me the nickname "the debug kid". I still haven't heard the end of it. Erik Mintz - Original Message - From: Ben Lovegrove [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, August 08, 2000 3:19 AM Subject: "You can call yourself and internetworking engineer when . . . ." | (tongue firmly in cheek) | | I have this theory that you can call yourself and internetworking | engineer when . . . . | | 1. You have run a debug command on a customer router while | investigating a performance problem, or perhaps a security issue, and | you have caused the CPU to exceed 100% and the router has hung/crashed. | | 2. You have edited an ACL remotely and reapplied it only to find you | have blocked all traffic including telnet from your desk and you are | now locked out. | | 3. In both of the above scenarios you have made up some story for the | Help Desk/1st Line Support and asked them to get the customer to reboot | the router, claiming that "a reboot may help the performance problem . | . blah . . blah" | | 4. In each of points 1 2 the customer in question is a major account | that has threatened legal action against your company for failing to | maintain SLAs, or to close the account altogether. | | Does this sound familiar to anyone? Have you every felt that cold | feeling in the pit of your stomach when you entered a command and the | screen froze? Did you blame hardware/software/customer/gremlins i.e. | anybody and anything but not yourself? | | ;-) | | Ben | | | | = | Ben Lovegrove, CCNP | Redspan Solutions Ltd | http://www.redspan.com | Cisco: Products, Training, Jobs, Study Guides, Resources. ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
Has anyone ever added a static route only to find out that the route is not in the route table nor is the customers routes? I usually blame it on bad memory, reboot and it works. I know I did it right but you still feel like an ass. Jason Hitt MCSE+I, CNA, CCNA, CCDA, A+, Network + -Original Message- From: McMasters, Eric [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 10:57 AM To: 'Cohen, Michael'; [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." That also falls in-line with when we wanted to see what "debug all" would do on the core router. After about a minute of continuous logging messages it just stopped working. Again we had to reboot the router and we were somehow able to blame it on the server guys! "Sir, the NT servers were generating excessive broadcasts which filled the routers buffers and forced it to shut down. You know Sir you really should talk to those server guys about configuring their equipment right." Ah the good ole' days, huh Mike!!! Eric L. McMasters, CCNP/CCDA OSSN - Sr. Network Engineer Phone:913.859.1986 PCS:913.485.9734 Fax: 913.859.1234 -Original Message- From: Cohen, Michael [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 8:38 AM To: [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." Too funny. I can think of one incident about 4 years back when I was in the military and we didn't know anything about configuring cisco equipment. A friend of mine who lurks on this list like me (you know who you are Eric) and myself were trying to play a prank on a fellow co-worker and block traffic on his computer. We thought of an ACL to block his IP address but he was smart enough to change it if we did that. So we settled on creating a filter by mac address. The problem was we couldn't apply it to the interface so after a little reading we figured the interface needed to be in a bridge group to apply this ACL. Now, this interface was serving our entire building which was the Communications Squadron for the base. Needless to say when when everyone in the building started yelling we rebooted it and blamed it on a software crash on the router (hey these things happen:)... Michael Cohen CCDP, CCNP CCIE #6080 -Original Message- From: Ben Lovegrove [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 12:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.
RE: You can call yourself and internetworking engineer when . . . .
or entered a static route for a gateway of last resort as ip route 0.0.0.0 255.255.255.255 10.20.30.254 hmm, how come that didn't work. it shows up in the routing table. (fx: scratches head and tries to look confident in front of the customer) what's this /32 at the end of the address? daveh -Original Message- From: Hitt, Jason [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 22, 2000 11:37 AM To: 'McMasters, Eric'; 'Cohen, Michael'; [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." Has anyone ever added a static route only to find out that the route is not in the route table nor is the customers routes? I usually blame it on bad memory, reboot and it works. I know I did it right but you still feel like an ass. Jason Hitt MCSE+I, CNA, CCNA, CCDA, A+, Network + -Original Message- From: McMasters, Eric [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 10:57 AM To: 'Cohen, Michael'; [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." That also falls in-line with when we wanted to see what "debug all" would do on the core router. After about a minute of continuous logging messages it just stopped working. Again we had to reboot the router and we were somehow able to blame it on the server guys! "Sir, the NT servers were generating excessive broadcasts which filled the routers buffers and forced it to shut down. You know Sir you really should talk to those server guys about configuring their equipment right." Ah the good ole' days, huh Mike!!! Eric L. McMasters, CCNP/CCDA OSSN - Sr. Network Engineer Phone:913.859.1986 PCS:913.485.9734 Fax: 913.859.1234 -Original Message- From: Cohen, Michael [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 8:38 AM To: [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." Too funny. I can think of one incident about 4 years back when I was in the military and we didn't know anything about configuring cisco equipment. A friend of mine who lurks on this list like me (you know who you are Eric) and myself were trying to play a prank on a fellow co-worker and block traffic on his computer. We thought of an ACL to block his IP address but he was smart enough to change it if we did that. So we settled on creating a filter by mac address. The problem was we couldn't apply it to the interface so after a little reading we figured the interface needed to be in a bridge group to apply this ACL. Now, this interface was serving our entire building which was the Communications Squadron for the base. Needless to say when when everyone in the building started yelling we rebooted it and blamed it on a software crash on the router (hey these things happen:)... Michael Cohen CCDP, CCNP CCIE #6080 -Original Message- From: Ben Lovegrove [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 12:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstu
Re: You can call yourself and internetworking engineer when . . . .
Been there, done that... Reload is a marvelous 'cover your ass' command. I guess by Bens definition I am a truly great engineer (not - but hey we all have to learn) Havent monumentally messed up in along time (famous last words...) L8r. ;-) "Sasa Milic" [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... There is great command 'reload in number of minutes'; should be used before any serious work :) Atif Awan wrote: lol :) hasnt happened to me yet but i cant help thinking abt the feeling :o) ( guess i am not a complete internetworking engineer yet ) 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] --- ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
Yes! I knew I was not the only one. Internetworking - it's living life to the max. Oh, the thrill of: "Hit it, and see what happens" "It's only a mild debug command" "This is a certainty for improving throughput" "Of course I know what 'implicit deny' means" --- David Jones [EMAIL PROTECTED] wrote: Ooh Ben, been there done that :) -Original Message- From: Cbridgett [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 6:46 PM To: Ben Lovegrove; [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." Got one even better. copy run testconfg Do you want to erase flash? Y ...ohhssh oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oe "...to hell with what other people think, I'm ridin' my own broom!" L. M. Cynthia Bridgett, raised in SE DC and proud of it! CCNA, MCSE, CNE, CNA, MCP, A+ oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Lovegrove Sent: Tuesday, August 08, 2000 3:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: You can call yourself and internetworking engineer when . . . .
Ben: I do neither. I smile and act like that I expected that result. THEN I reboot. David (tongue placed back in cheek after wagging furiously) Besides, the secret to being a consultant is to know *at least* 2% more than your client. Mind you, the requirement rarely exceeds 2%! - Original Message - From: "Ben Lovegrove" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, August 08, 2000 3:19 AM Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
lol :) hasnt happened to me yet but i cant help thinking abt the feeling :o) ( guess i am not a complete internetworking engineer yet ) Atif -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Lovegrove Sent: Tuesday, August 08, 2000 12:20 PM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: You can call yourself and internetworking engineer when . . . .
There is great command 'reload in number of minutes'; should be used before any serious work :) Atif Awan wrote: lol :) hasnt happened to me yet but i cant help thinking abt the feeling :o) ( guess i am not a complete internetworking engineer yet ) 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
I have to say that I was surprised when I found a show command that will crash a router in the first releases of 12.0. The first time I played in a customers 8500 Series running 12.0 I did a bunch if show commands until I found out Cisco added "show diag ? ". I decided it would be interesting to try every option possible behind it and see what was shown. Then, the router completely quit responding. Of course this happened around 2 AM 800 miles away from my building. So I contacted the customer to go in and reboot the box. The customer said that all the lights on the entire chassis were bright red. After the reboot the box recovered saying possible write erase preformed and of course went right to the setup dialog. The config was not in the router anyway and the customer failed to back it up. So of course I spent the next three hours helping the customer figure out how to restore the configuration by tracing cable and looking at IP addresses assigned on each machine. Now I can't tell my new employees that show commands will never cause a problem...But if it does you blame it on that Cisco IOS. James Hilving -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Lovegrove Sent: Tuesday, August 08, 2000 2:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
That also falls in-line with when we wanted to see what "debug all" would do on the core router. After about a minute of continuous logging messages it just stopped working. Again we had to reboot the router and we were somehow able to blame it on the server guys! "Sir, the NT servers were generating excessive broadcasts which filled the routers buffers and forced it to shut down. You know Sir you really should talk to those server guys about configuring their equipment right." Ah the good ole' days, huh Mike!!! Eric L. McMasters, CCNP/CCDA OSSN - Sr. Network Engineer Phone:913.859.1986 PCS:913.485.9734 Fax: 913.859.1234 -Original Message- From: Cohen, Michael [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 8:38 AM To: [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." Too funny. I can think of one incident about 4 years back when I was in the military and we didn't know anything about configuring cisco equipment. A friend of mine who lurks on this list like me (you know who you are Eric) and myself were trying to play a prank on a fellow co-worker and block traffic on his computer. We thought of an ACL to block his IP address but he was smart enough to change it if we did that. So we settled on creating a filter by mac address. The problem was we couldn't apply it to the interface so after a little reading we figured the interface needed to be in a bridge group to apply this ACL. Now, this interface was serving our entire building which was the Communications Squadron for the base. Needless to say when when everyone in the building started yelling we rebooted it and blamed it on a software crash on the router (hey these things happen:)... Michael Cohen CCDP, CCNP CCIE #6080 -Original Message- From: Ben Lovegrove [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 12:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
Got one even better. copy run testconfg Do you want to erase flash? Y ...ohhssh "...to hell with what other people think, I'm ridin' my own broom!" L. M. Cynthia Bridgett, raised in SE DC and proud of it! CCNA, MCSE, CNE, CNA, MCP, A+ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Lovegrove Sent: Tuesday, August 08, 2000 3:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
Ooh Ben, been there done that :) -Original Message- From: Cbridgett [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 6:46 PM To: Ben Lovegrove; [EMAIL PROTECTED] Subject: RE: "You can call yourself and internetworking engineer when . . . ." Got one even better. copy run testconfg Do you want to erase flash? Y ...ohhssh oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oe "...to hell with what other people think, I'm ridin' my own broom!" L. M. Cynthia Bridgett, raised in SE DC and proud of it! CCNA, MCSE, CNE, CNA, MCP, A+ oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoeoe oe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Lovegrove Sent: Tuesday, August 08, 2000 3:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: You can call yourself and internetworking engineer when . . . .
Too funny. I can think of one incident about 4 years back when I was in the military and we didn't know anything about configuring cisco equipment. A friend of mine who lurks on this list like me (you know who you are Eric) and myself were trying to play a prank on a fellow co-worker and block traffic on his computer. We thought of an ACL to block his IP address but he was smart enough to change it if we did that. So we settled on creating a filter by mac address. The problem was we couldn't apply it to the interface so after a little reading we figured the interface needed to be in a bridge group to apply this ACL. Now, this interface was serving our entire building which was the Communications Squadron for the base. Needless to say when when everyone in the building started yelling we rebooted it and blamed it on a software crash on the router (hey these things happen:)... Michael Cohen CCDP, CCNP CCIE #6080 -Original Message- From: Ben Lovegrove [mailto:[EMAIL PROTECTED]] Sent: Tuesday, August 08, 2000 12:20 AM To: [EMAIL PROTECTED] Subject: "You can call yourself and internetworking engineer when . . . ." (tongue firmly in cheek) I have this theory that you can call yourself and internetworking engineer when . . . . 1. You have run a debug command on a customer router while investigating a performance problem, or perhaps a security issue, and you have caused the CPU to exceed 100% and the router has hung/crashed. 2. You have edited an ACL remotely and reapplied it only to find you have blocked all traffic including telnet from your desk and you are now locked out. 3. In both of the above scenarios you have made up some story for the Help Desk/1st Line Support and asked them to get the customer to reboot the router, claiming that "a reboot may help the performance problem . . blah . . blah" 4. In each of points 1 2 the customer in question is a major account that has threatened legal action against your company for failing to maintain SLAs, or to close the account altogether. Does this sound familiar to anyone? Have you every felt that cold feeling in the pit of your stomach when you entered a command and the screen froze? Did you blame hardware/software/customer/gremlins i.e. anybody and anything but not yourself? ;-) Ben = Ben Lovegrove, CCNP Redspan Solutions Ltd http://www.redspan.com Cisco: Products, Training, Jobs, Study Guides, Resources. Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
