From: Tim O'Brien (tobrien@xxxxxxxxxxxx)
Date: Mon Mar 18 2002 - 08:44:24 GMT-3
Are we sure that this question is best answered with a source-bridge
command? I could also read it that we would need to change the hold queue on
the TokenRing interface from the default of 75 frames to 100. The question
reads, 100 frames, not 100 explorer frames. And even if we raised the value
of the explorerQ, we could still drop explorer frames with other traffic
getting there first and filling the queue. This is the kind of detail that
has nailed me on the last couple of lab attempts, now I am paranoid... : )
Thoughts?
Tim
----- Original Message -----
From: "Emmanuel Oppong" <e-oppong@attbi.com>
To: "Manny Gonzalez" <gonzalu@nyp.org>; "CCIELab at GroupStudy.com"
<ccielab@groupstudy.com>
Sent: Sunday, March 17, 2002 8:52 PM
Subject: RE: --- DLSw+ ---
Here is your answer:
source-bridge explorerQ-depth 100
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Manny Gonzalez
Sent: Sunday, March 17, 2002 12:06 PM
To: CCIELab at GroupStudy.com
Subject: --- DLSw+ ---
I am doing a lab a friend got from a class he attended in NY. There is a
question in the DLSw section that has puzzled the heck out of me and I
simply can not make sense of it. Perhaps someone here can help:
"7.3 Assuming Ring 2 is sending a lot of explorer frames, which causes
R2 token ring to drop frames, configure R2 so that the token ring will
accept at least 100 frames."
Now, I know I can stop the explorers by populating the reachability
tables with ICANREACH, but, what the heck is this "accept at least 100
frames" stuff?
TIA
Manny
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:12 GMT-3