The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2001-Feb> msg00367



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

comments on draft-dubuc-mpls-bundle-mib-00.txt

  • From: Jim Boyle <jboyle@Level3.net>
  • Date: Tue, 27 Feb 2001 10:07:46 -0700 (MST)


Martin, good idea, if we're going to start thinking about having link
bundles, we should probably think about mibs to get relevant information
out of network (for nms) or into network (if that is one's manner).

I do think that this mib reaches too far, and replicates information that
is available elsewhere.

You mention an example of grouping 3 component links into 1 bundled
link.  For some reason you mention 2 primary and 1 secondary, is this 1:N
protection, and if so, is there a relevant APS/Sonet/SDH mib where this
assocation of the secondary to the protected links should be made?

In general, the mib should be able to grab interfaces and group them
together, however it's my view that these become standard interfaces, seen
in ifTable, in relevant OSPF mibs, TE mibs, etc...  The bundled mib keeps
track of the relationship only (e.g. id 10 really is a composite of 1,2,3)

Why would one want to be able to not only get the OSPF TE metric from the
bundled mib, and from the TEMIB?

Anyways, my comment would be that the bundle mib should stick to a core
business, and leverage information that exist (rightfully) in other
places.

regards,

Jim