--- 1/draft-ietf-mpls-mgmt-overview-05.txt 2006-02-05 00:41:49.000000000 +0100 +++ 2/draft-ietf-mpls-mgmt-overview-06.txt 2006-02-05 00:41:49.000000000 +0100 @@ -1,24 +1,23 @@ Network Working Group Thomas D. Nadeau Internet Draft Cisco Systems, Inc. Category: Informational -Expires: October 2003 Cheenu Srinivasan - Parama Networks, Inc. +Expires: November 2003 Cheenu Srinivasan Adrian Farrel Movaz Networks, Inc. - May 2003 + June 2003 Multiprotocol Label Switching (MPLS) Management Overview - draft-ietf-mpls-mgmt-overview-05.txt + draft-ietf-mpls-mgmt-overview-06.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026 [RFC2026]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working @@ -335,30 +334,29 @@ In the case of an IP-to-MPLS mapping, the FEC objects describe IP 6-tuples representing source and destination address ranges, source and destination port ranges, IPv4 Protocol field or IPv6 next-header field and the DiffServ Code Point (DSCP). 4.10. TE-LINK-STD-MIB TE-LINK-STD-MIB describes managed objects that are used to model - and manage bundling of TE links in an MPLS network. + and manage TE links, including bundled links, in an MPLS network. - The link bundling feature is designed to aggregate one or - more similar data channels between a pair of LSRs into a - bundled link. The data channel is referred to as a TE link + The TE link feature is designed to aggregate one or more similar + data channels or TE links between a pair of LSRs. A TE link and is a sub-interface capable of carrying traffic engineered MPLS traffic. - A link bundle is a sub-interface that bonds the traffic of - a group of one or more TE links. + A bundled link is a sub-interface that bonds the traffic of + a group of one or more TE links." 4.11. MIB Module Interdependencies This section provides an overview of the relationship between the MPLS MIB modules described above. More details of these relationships are given below once the MIB modules have been discussed in more detail. The arrows in the following diagram show a 'depends on' relationship. A "MIB module A depends on MIB module B" @@ -804,88 +802,76 @@ TE-LINK-STD-MIB contains the following tables. - The TE link table (teLinkTable) is used to specify TE links, including bundled links, and their generic traffic engineering parameters. - The TE link descriptor table (teLinkDescriptorTable) is used to list the TE link descriptors. - - The TE link OSPF traffic engineering table - (teLinkOspfTeTable) is used for configuring OSPF - traffic engineering parameters associated with TE - links. - - The shared risk link group (SRLG) table (teLinkSrlgTable) is used to specify the SRLGs associated with TE links. - The TE link bandwidth table (teLinkBandwidthTable) is used to report priority-based bandwidth values associated with TE links. - - The data-bearing channel table - (dataBearingChannelTable) is used to identify the data- - bearing channels that are associated with the TE links - and specify the data-bearing channel generic traffic + - The component link table + (componentLinkTable) is used to identify the data- + bearing component links that are associated with the + TE links and specify the data-bearing link generic traffic engineering parameters. - - The data-bearing channel link descriptor table - (dataBearingChannelDescriptorTable) is used to list the - data-bearing channel link descriptors. + - The component link descriptor table + (componentLinkDescriptorTable) is used to list the + data-bearing component link descriptors. - - The data-bearing channel bandwidth table - (dataBearingChannelBandwidthTable) is used to report + - The component link bandwidth table + (componentLinkBandwidthTable) is used to report priority-based bandwidth values associated with data- - bearing channels. + bearing component links. 9.2. Scalars - A single scalar (teLinkNotifEnable) exists. It is - used to enable and disable notifications defined in the MIB - module from being issued by a device. + There are no scalars in this MIB module. 9.3. Notifications - A single notification is defined. - - - linkBundleMismatch is generated when a mismatch of TE - parameters between members of a bundled link is found. + There are no notifications in this MIB module. 9.4. Dependencies Between MIB Module Tables The tables in TE-LINK-STD-MIB are related as shown on the diagram below. The arrows indicate a reference from one table to another. Note that many of the associations between tables are through a common index that is the ifIndex of the related interface. teLinkTable ^ | - teLinkOspfLinkTable -----+ - | teLinkDescriptorTable ---+ | teLinkSrlgTable ---------+ | teLinkBandwidthTable ----+ - dataBearingChannelTable + componentLinkTable ^ | - dataBearingChannelDescriptorTable ---+ + componentLinkDescriptorTable ---+ | - dataBearingChannelBandwidthTable ----+ + componentLinkBandwidthTable ----+ 10. Table Dependencies Between MPLS MIB Modules Section 4.11 gave an overview of how the MPLS MIB modules are related. Now that the tables in the MIB modules have been introduced, it is possible to give a more detailed diagram of these relationships. MPLS-TC-STD-MIB is left off the diagram since so many of the MIB module tables use textual conventions from that MIB @@ -960,40 +946,42 @@ 11.2. Application of the Interfaces Group to TE Links The TE-LINK-STD-MIB also uses interface stacking to manage TE Link interfaces as logical interfaces. The TE Link interface is represented as an entry in the ifTable. The inter-relation of entries in the ifTable is defined by Interfaces Stack Group defined in [RFC2863]. When using TE Link interfaces, the interface stack table might appear as follows: - +---------------------------------------------------------------+ + +-------------------------------------------------------------------+ | MPLS interface ifType = mpls(166) | - +---------------------------------------------------------------+ - | TE link-interface (bundle) ifType = teLink(200) | - +------------------------------+-+------------------------------+ + | ifIndex = 1 | + +-------------------------------------------------------------------+ + | TE link (bundled link) ifType = teLink(200) | + | ifIndex = 2 | + +--------------------------------+-+--------------------------------+ | TE link ifType = teLink(200) | | TE link ifType = teLink(200) | - +-------------+--+-------------+ +-------------+--+-------------+ - |opticalTrans | |opticalTrans | |opticalTrans | |opticalTrans | - |ifType = 196 | |ifType = 196 | |ifType = 196 | |ifType = 196 | - +-------------+ +-------------+ +-------------+ +-------------+ + | ifIndex = 3 | | ifIndex = 4 | + +--------------------------------+ +--------------------------------+ + | Component link | | Component link | + | ifType = opticalTransport(196) | | ifType = opticalTransport(196) | + | ifIndex = 5 | | ifIndex = 6 | + +--------------------------------+ +--------------------------------+ - In the above diagram, "opticalTrans" is an example of an - underlying physical interface: in this case an optical - transport interface. TE link management and bundling can - be seen in the levels of interface stacking. Two TE links - are defined each managing two optical transport links. - These two TE links are combined into a bundle which is - managed as a single TE link interface. This TE Link - interface supports MPLS and is presented as an MPLS - interface. + In the above diagram, "opticalTransport" is an example of an + underlying physical interface: in this case an optical transport + interface. TE link management and bundling can be seen in the levels + of interface stacking. Two TE links are defined each managing an + optical transport link. These two TE links are combined into a + bundle which is managed as a single TE link interface. This TE Link + interface supports MPLS and is presented as an MPLS interface. A detailed listing of the mapping between ifTable objects and their use for TE Links is given in [TELMIB]. A few key objects are listed here to provide an overview of the concepts. Each TE Link interface is represented by a separate entry in the ifTable with a unique ifIndex. The type of an interface represented by an entry in the @@ -1420,25 +1408,21 @@ 20. Authors' Addresses Thomas D. Nadeau Cisco Systems, Inc. 300 Apollo Drive Chelmsford, MA 01824 Phone: +1-978-244-3051 Email: tnadeau@cisco.com Cheenu Srinivasan - Parama Networks, Inc. - 1030 Broad Street - Shrewsbury, NJ 07702 - Phone: +1-732-544-9120 x731 - Email: cheenu@paramanet.com + Email: cheenu@alumni.princeton.edu Adrian Farrel Movaz Networks, Inc. 7926 Jones Branch Drive, Suite 615 McLean, VA 22102 Phone: +1-703-847-1867 Email: afarrel@movaz.com 21. Full Copyright Statement