Re: [Bridge-mib] Portlist in RFC2764

Michael MacFaden <mrm@riverstonenet.com> Thu, 19 December 2002 09:19 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12133 for <bridge-archive@odin.ietf.org>; Thu, 19 Dec 2002 04:19:03 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBJ9Ljt12841 for bridge-archive@odin.ietf.org; Thu, 19 Dec 2002 04:21:45 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBJ9Lfv12833; Thu, 19 Dec 2002 04:21:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBJ9Kwv12790 for <bridge-mib@optimus.ietf.org>; Thu, 19 Dec 2002 04:20:58 -0500
Received: from agile.yagosys.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA12126 for <bridge-mib@ietf.org>; Thu, 19 Dec 2002 04:17:45 -0500 (EST)
Received: (qmail 4255 invoked by uid 10041); 19 Dec 2002 09:20:45 -0000
Date: Thu, 19 Dec 2002 01:20:45 -0800
From: Michael MacFaden <mrm@riverstonenet.com>
To: Pat Medved <medved@lachman.com>
Cc: bridge-mib@ietf.org
Subject: Re: [Bridge-mib] Portlist in RFC2764
Message-ID: <20021219092045.GC4160@riverstonenet.com>
References: <Pine.LNX.3.96.1021218142135.14734B-100000@wry.lachman.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.3.96.1021218142135.14734B-100000@wry.lachman.com>
User-Agent: Mutt/1.4i
X-Operating-System: GNU/Linux 2.4.18
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>

On Wed, Dec 18, 2002 at 02:22:33PM -0600, Pat Medved wrote:
>I noticed the portlist in rfc2764.  I've seen this same thing in other
>Vendors MIbs as well.  I was wondering what these port numbers are.
>
>If they are ports 1-256, what do those numbers map to on the switch
>itself?  I was trying to find the correlation between these ports
>and the ports in the bridge MIB itself.

Have a look at
http://www.nanog.org/mtg-0102/ppt/mibs/sld082.htm

In short, dot1dBasePortNum are typically mapped to an ifIndex.
Then from ifIndex you can check with either an entity mib or
an enterprise mib module to locate the vendor port identifier.

>Also, if there is only 32 octets, what goes in this list if more than 256 
>ports are on a bridge?

PortList TC uses a plain OCTET STRING, it can be larger than 32 octets.
See rfc 2578 section 7.1.2.

Regards,
Mike MacFaden


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