[Bridge-mib] Clarification on dot1dStpPortEnable and ForcePortState for STP/RSTP.

"NK Krishnan" <nk_queries@rediffmail.com> Thu, 14 August 2003 05:29 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17557 for <bridge-archive@odin.ietf.org>; Thu, 14 Aug 2003 01:29:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nAfV-0006DR-NC for bridge-archive@odin.ietf.org; Thu, 14 Aug 2003 01:29:01 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7E5T1Yp023882 for bridge-archive@odin.ietf.org; Thu, 14 Aug 2003 01:29:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nAfU-0006Cy-IY; Thu, 14 Aug 2003 01:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19nAed-0006CT-Gr for bridge-mib@optimus.ietf.org; Thu, 14 Aug 2003 01:28:07 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17511 for <bridge-mib@ietf.org>; Thu, 14 Aug 2003 01:28:03 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19nAea-0007Xt-00 for bridge-mib@ietf.org; Thu, 14 Aug 2003 01:28:04 -0400
Received: from [203.199.83.148] (helo=rediffmail.com) by ietf-mx with smtp (Exim 4.12) id 19nAeY-0007Xo-00 for bridge-mib@ietf.org; Thu, 14 Aug 2003 01:28:03 -0400
Received: (qmail 19382 invoked by uid 510); 14 Aug 2003 05:26:45 -0000
Date: 14 Aug 2003 05:26:45 -0000
Message-ID: <20030814052645.19381.qmail@webmail26.rediffmail.com>
Received: from unknown (203.197.138.194) by rediffmail.com via HTTP; 14 aug 2003 05:26:45 -0000
MIME-Version: 1.0
From: "NK Krishnan" <nk_queries@rediffmail.com>
Reply-To: "NK Krishnan" <nk_queries@rediffmail.com>
To: bridge-mib@ietf.org
Content-type: text/plain; format=flowed
Content-Disposition: inline
Subject: [Bridge-mib] Clarification on dot1dStpPortEnable and ForcePortState for STP/RSTP.
Sender: bridge-mib-admin@ietf.org
Errors-To: bridge-mib-admin@ietf.org
X-BeenThere: bridge-mib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=unsubscribe>
List-Id: <bridge-mib.ietf.org>
List-Post: <mailto:bridge-mib@ietf.org>
List-Help: <mailto:bridge-mib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bridge-mib>, <mailto:bridge-mib-request@ietf.org?subject=subscribe>

Hi All,

I had a look into the latest draft of Bridge MIB and I have a 
doubt regarding dot1dStpPortEnable.

1. What is the expected behaviour of the port in STP when the 
object is set to disabled?
2. What is the effect of setting this object on L2 and L3 Data 
forwarding ?

As I understand, dot1dStpPortEnable is to be used to 
enable/disable STP on a port. i.e STP calculation exclude this 
port. In case of RSTP, the port will be in Disabled/Discarding. Is 
it proper to apply STP roles/States to a port that is not under 
the control of STP? When we set this object to disabled, should 
this port stop forwarding Layer 2 packets?

What is the relation between dot1dStpPortEnable and ifMainStaus of 
the interface?

Thanks in advance,
Navaneeth.


___________________________________________________
Meet your old school or college friends from
1 Million + database...
Click here to reunite www.batchmates.com/rediff.asp



_______________________________________________
Bridge-mib mailing list
Bridge-mib@ietf.org
https://www1.ietf.org/mailman/listinfo/bridge-mib