From owner-frnetmib@sunroof.eng.sun.com Mon Apr 2 09:57:35 2001 Received: from mercury.Sun.COM ([192.9.25.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA09873; Mon, 2 Apr 2001 09:57:35 -0400 (EDT) Received: from engmail3.Eng.Sun.COM ([129.144.170.5]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA23301; Mon, 2 Apr 2001 06:57:01 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA15773; Mon, 2 Apr 2001 06:56:43 -0700 (PDT) Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.0.Beta5+Sun/8.12.0.Beta5) with ESMTP id f32DuYIm018769 for ; Mon, 2 Apr 2001 06:56:35 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.0.Beta5+Sun/8.12.0.Beta5) id f32DuYkE018768 for frnetmib-dist; Mon, 2 Apr 2001 06:56:34 -0700 (PDT) X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-frnetmib@sunroof.eng.sun.com using -f Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13]) by sunroof.eng.sun.com (8.12.0.Beta5+Sun/8.12.0.Beta5) with ESMTP id f32DuSIm018761 for ; Mon, 2 Apr 2001 06:56:28 -0700 (PDT) Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA14152 for ; Mon, 2 Apr 2001 06:56:18 -0700 (PDT) Received: from nova.tx.fnc.fujitsu.com (nova.tx.fnc.fujitsu.com [167.254.254.131]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA19161 for ; Mon, 2 Apr 2001 06:56:18 -0700 (PDT) Received: from miranda.tx.fnc.fujitsu.com (localhost [127.0.0.1]) by nova.tx.fnc.fujitsu.com (8.8.8+Sun/8.8.8) with ESMTP id IAA27421; Mon, 2 Apr 2001 08:53:18 -0500 (CDT) Received: from tdd1541.tx.fnc.fujitsu.com (tdd1541.tddeng00.fnts.com [167.254.248.63]) by miranda.tx.fnc.fujitsu.com (8.9.3+Sun/8.9.3) with ESMTP id IAA10491; Mon, 2 Apr 2001 08:53:17 -0500 (CDT) Received: from fnc.fujitsu.com (localhost [127.0.0.1]) by tdd1541.tx.fnc.fujitsu.com (8.8.8+Sun/8.8.8) with ESMTP id IAA29050; Mon, 2 Apr 2001 08:53:17 -0500 (CDT) Message-ID: <3AC8844C.C9EF9C2F@fnc.fujitsu.com> Date: Mon, 02 Apr 2001 08:53:17 -0500 From: Robert Steinberger X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Lavallee, Craig (cj)" CC: frnetmib@sunroof.eng.sun.com Subject: Re: (FRNETMIB) MIB Variables References: <8BDB07FE67F3D41182F40008C70922EA8FE2DD@corp-exc5.ctron.com> Content-Type: multipart/alternative; boundary="------------4D3559D662E112D47AA5CA68" Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ --------------4D3559D662E112D47AA5CA68 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Craig, See http://www.ietf.org/internet-drafts/draft-ietf-frnetmib-frmrelay-service-03.txt for information. There are a set of variables that cover exactly what you are looking for. Rob. "Lavallee, Craig (cj)" wrote: > > > Can anyone help me with what MIB Variables do I need to > look at in order to get the necessary values for the > following SLA formulas according to FRF.10 the > "Definition of a Framerelay SLA" : > > Management Domains Edge-to Edge > Interfac, Edge-to-Edge Egress Queue,End-to End. > FDR = Frames Delivered c + e > --------------------------------- > Frames Offered c + e > DDR = Data Deleviered c+e > ------------------------------ > Data Offered c+e > FRVCA = IntervalTime-ExcludedOutageTime-OutageTime > _______________________________________ > *100 > IntervalTime - ExcludedOutageTime > FRMTR= OutageTime > ------------------ > Outage Count > FRMTBSO= > IntervalTime-ExcludedOutageTime-OutageTime > _______________________________________ > > Outage Count > thanks > craig > > --------------4D3559D662E112D47AA5CA68 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Craig,

See http://www.ietf.org/internet-drafts/draft-ietf-frnetmib-frmrelay-service-03.txt for information.  There are a set of variables that cover exactly what you are looking for.

Rob.

"Lavallee, Craig (cj)" wrote:

 
        Can anyone help me with what MIB Variables do I need to look at in order to get the necessary values for the following SLA formulas according to FRF.10 the "Definition of a Framerelay SLA" :

        Management Domains Edge-to Edge
        Interfac, Edge-to-Edge Egress Queue,End-to End.
        FDR     =       Frames Delivered c + e
                        ---------------------------------
                        Frames Offered c + e
        DDR     =       Data Deleviered c+e
                        ------------------------------
                        Data Offered c+e
        FRVCA =  IntervalTime-ExcludedOutageTime-OutageTime
                        _______________________________________ *100
                        IntervalTime - ExcludedOutageTime
        FRMTR=  OutageTime
                        ------------------
                        Outage Count
        FRMTBSO=        IntervalTime-ExcludedOutageTime-OutageTime
                        _______________________________________
                        Outage Count

      thanks
      craig
       
--------------4D3559D662E112D47AA5CA68-- X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Thu Apr 19 10:13:48 2001 Received: from patan.sun.com ([192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA11349; Thu, 19 Apr 2001 10:13:46 -0400 (EDT) Received: from engmail4.Eng.Sun.COM ([129.144.134.6]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA01126; Thu, 19 Apr 2001 07:13:11 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA08460; Thu, 19 Apr 2001 07:13:03 -0700 (PDT) Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.0.Beta7+Sun/8.12.0.Beta7) with ESMTP id f3JECpK9006612 for ; Thu, 19 Apr 2001 07:12:51 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.0.Beta7+Sun/8.12.0.Beta7) id f3JECosi006609 for frnetmib-dist; Thu, 19 Apr 2001 07:12:50 -0700 (PDT) X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-frnetmib@sunroof.eng.sun.com using -f Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13]) by sunroof.eng.sun.com (8.12.0.Beta7+Sun/8.12.0.Beta7) with ESMTP id f3JECiK9006601 for ; Thu, 19 Apr 2001 07:12:44 -0700 (PDT) Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA07473 for ; Thu, 19 Apr 2001 07:12:44 -0700 (PDT) From: Keith.Schuettpelz@go.ecitele.com Received: from mizar.ftl.telematics.com ([147.137.1.7]) by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA20407 for ; Thu, 19 Apr 2001 07:12:44 -0700 (PDT) Received: from ftlnotes01.ftl.telematics.com (ftlnotes01 [147.137.21.216]) by mizar.ftl.telematics.com (8.9.1/8.9.1) with ESMTP id KAA29983 for ; Thu, 19 Apr 2001 10:12:41 -0400 (EDT) Subject: (FRNETMIB) Question regarding RFC 3020 & FRF.16 To: frnetmib@sunroof.eng.sun.com Date: Thu, 19 Apr 2001 10:12:47 -0400 Message-ID: X-MIMETrack: Serialize by Router on ftlnotes01/ECI Telecom(Release 5.0.5 |September 22, 2000) at 04/19/2001 10:12:48 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ Hi, In reading FRF.16, RFC 3020 and the various tutorial information, I see no clear indication as to whether or not the MFR Bundle Link is ever expected/allowed to be of type ds0Bundle (IfType=82). While the example conatined in RFC 3020 shows the MFR Bundle Links as being T1s (ifType=DS1=18), this is just one example and not an exhaustive list of the expected/possible ifTypes. Can anyone tell me if MFR Bundle Links can be of ifType ds0Bundle (82)? Does anyone implement support for them as ds0Bundles? I'm investigating the enhancement of a legacy device to support FRF.16 and RFC3020. This device treats all DS1's as channelized, and implements a ds0Bundle (ifType=82) as an upper layer on each DS1, even if/when the ds0Bundle includes all 24 DS0's of the T1. My concern is that 3rd party SNMP managers may have difficulty managing the device if the managers were not written to expect MFR Bundle Links of ifType=ds0Bundle. Any helpful comments would be appreciated. Thank you in advance. Keith Schuettpelz X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message. From owner-frnetmib@sunroof.eng.sun.com Sat Apr 21 09:22:50 2001 Received: from patan.sun.com (patan.Sun.COM [192.18.98.43]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA10092; Sat, 21 Apr 2001 09:22:49 -0400 (EDT) Received: from engmail1.Eng.Sun.COM ([129.146.1.13]) by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA27733; Sat, 21 Apr 2001 06:22:20 -0700 (PDT) Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88]) by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA01813; Sat, 21 Apr 2001 06:10:57 -0700 (PDT) Received: from sunroof.eng.sun.com (localhost [127.0.0.1]) by sunroof.eng.sun.com (8.12.0.Beta7+Sun/8.12.0.Beta7) with ESMTP id f3LDAnK9010378 for ; Sat, 21 Apr 2001 06:10:50 -0700 (PDT) Received: (from majordomo@localhost) by sunroof.eng.sun.com (8.12.0.Beta7+Sun/8.12.0.Beta7) id f3LDAn7o010377 for frnetmib-dist; Sat, 21 Apr 2001 06:10:49 -0700 (PDT) X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-frnetmib@sunroof.eng.sun.com using -f Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5]) by sunroof.eng.sun.com (8.12.0.Beta7+Sun/8.12.0.Beta7) with ESMTP id f3LDAfK9010370 for ; Sat, 21 Apr 2001 06:10:43 -0700 (PDT) Received: from venus.Sun.COM (venus.EBay.Sun.COM [129.150.69.5]) by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA27328 for ; Sat, 21 Apr 2001 06:07:53 -0700 (PDT) Received: from rly-ip02.mx.aol.com (rly-ip02.mx.aol.com [152.163.225.160]) by venus.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA05124 for ; Sat, 21 Apr 2001 06:07:22 -0700 (PDT) Received: from tot-wg.proxy.aol.com (tot-wg.proxy.aol.com [205.188.196.1]) by rly-ip02.mx.aol.com (8.8.8/8.8.8/AOL-5.0.0) with ESMTP id JAA26816; Sat, 21 Apr 2001 09:06:57 -0400 (EDT) Received: from prayson (AC8B420B.ipt.aol.com [172.139.66.11]) by tot-wg.proxy.aol.com (8.10.0/8.10.0) with SMTP id f3LD6tt31862; Sat, 21 Apr 2001 09:06:56 -0400 (EDT) From: "Prayson Pate" To: , Subject: RE: (FRNETMIB) Question regarding RFC 3020 & FRF.16 Date: Sat, 21 Apr 2001 09:07:29 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 X-Apparently-From: Praysonpate@aol.com Sender: owner-frnetmib@sunroof.eng.sun.com Precedence: bulk X-Info: [Un]Subscribe to majordomo@sunroof.eng.sun.com X-Info: Submissions to frnetmib@sunroof.eng.sun.com X-Info: Email archive at ftp://ftp.ietf.org/ietf-mail-archive/frnetmib/ X-MIME-Autoconverted: from 8bit to quoted-printable by patan.sun.com id GAA27733 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA10092 Keith, See my comments below. Prayson Pate V.P. of Engineering Overture Networks prayson.pate@overturenetworks.com http://www.overturenetworks.com > -----Original Message----- > From: owner-frnetmib@sunroof.eng.sun.com > [mailto:owner-frnetmib@sunroof.eng.sun.com]On Behalf Of > Keith.Schuettpelz@go.ecitele.com > Sent: Thursday, April 19, 2001 10:13 AM > To: frnetmib@sunroof.eng.sun.com > Subject: (FRNETMIB) Question regarding RFC 3020 & FRF.16 > > > Hi, > > In reading FRF.16, RFC 3020 and the various tutorial information, I see no > clear indication as to whether or not the MFR Bundle Link is ever > expected/allowed to be of type ds0Bundle (IfType=82). Section 1.4 of FREF.16 states that a "Physical Link" is "A single physical interface that interconnects two devices in a frame relay network (e.g. DS1, DS0, Bearer channel, refer to FRF.14)." Thus any physical interface may be used as a "Physical Link". A "Bundle Link" is then defined as "A MFR sub-component that controls operation of one of the bundle'sphysical links." This makes it clear that DS0s are perfectly acceptable as Bundle Links. The intent of FRF.16 was to define a protocol independent of the physical nature of the underlying transport. Although not explicitly stated in FRF.16, it should be possible to implement a Bundle with Bundle Links of differing physical types. > > While the example contained in RFC 3020 shows the MFR Bundle > Links as being > T1s (ifType=DS1=18), this is just one example and not an > exhaustive list of > the expected/possible ifTypes. Correct. In fact, RFC3020 talks minimally about ifType and relies on the pre-existing ifTable for definition of interface types. > > Can anyone tell me if MFR Bundle Links can be of ifType ds0Bundle (82)? > Does anyone implement support for them as ds0Bundles? Lucent's "Lucent’s Enhanced Frame Relay Solutions (EFRS)" says this about Multilink Frame: Lets service providers offer custom fit bandwidth by bundling multiple connections at DSO-to-T1/E1 and T1/E1-to-DS3/E3 speeds for specific application requirements. http://www.lucent.com/products/solution/0,,CTID+2011-STID+10077-SOID+614-LOC L+1,00.html Tiara's "Multiservice Edge Routers" appear to offer NxDS0 and NxT1 MFR (see http://www.tiaranetworks.com/products/multiserve.html). At least two vendors are using DS0s in MFR; other vendors may be doing the same thing. > > I'm investigating the enhancement of a legacy device to support FRF.16 and > RFC3020. This device treats all DS1's as channelized, and implements a > ds0Bundle (ifType=82) as an upper layer on each DS1, even if/when the > ds0Bundle includes all 24 DS0's of the T1. > > My concern is that 3rd party SNMP managers may have difficulty > managing the > device if the managers were not written to expect MFR Bundle Links of > ifType=ds0Bundle. Any helpful comments would be appreciated. Most generic SNMP managers (HP OpenView, Castle Rock SNMPc, Cabletron/Aprisma Spectrum) provide simple MIB browsing, sometimes adding additional support for very common MIBs, tables or object, such as the route table, interface table, or RMON objects. Any advanced treatment of other tables or objects is usually done by vendor-specific element managers. I think that you are safe. > > Thank you in advance. > > Keith Schuettpelz Good luck! Prayson X-Info: To unsubscribe, email 'majordomo@sunroof.eng.sun.com' with X-Info: 'unsubscribe frnetmib' in the body of the message.