It's been a little tense on the list, so it seems, and I'll share some recent experience from the lighter side.
I spent this last weekend with friends, all of whom avoided computers as much as possible. Now, let me give some personal context. I have never had any interest in...ummm...spawning a child process. My closest to offspring is a Cat 1. My friends, however, have a 3 year old. Very quickly, I was given a demonstration of a demand circuit to which all traffic is interesting. As I had arrived wearing a brace on my still-healing broken foot, I also had a demonstration of collision detection when the child process decided it was GREAT to kick. At one point, we watched a video of Monty Python and the Meaning of Life, confirming the networking principle that the most important machine goes PING. We had not realized the child process was also watching, who became fascinated by the speaking fish in the movie, especially when Howard the Fish was eaten by one of the Pythons. It was quickly obvious that the child process was not flow controlled at one interface, which apparently used a new stress testing protocol issuing continuous NOs rather than ICMP echo requests. Before long, however, it became obvious that there were flow control problems at an interface at the other end. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=28935&t=28935 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
