idnits 2.17.1 draft-ietf-issll-is802-sbm-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 34 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 1999) is 9082 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'INTERFACEMIB' is mentioned on line 63, but not defined == Missing Reference: 'USM' is mentioned on line 974, but not defined == Missing Reference: 'VACM' is mentioned on line 975, but not defined == Unused Reference: 'RSVP' is defined on line 837, but no explicit reference was found in the text == Unused Reference: 'IS802' is defined on line 842, but no explicit reference was found in the text == Unused Reference: 'SBM' is defined on line 849, but no explicit reference was found in the text == Unused Reference: 'IS802MAP' is defined on line 855, but no explicit reference was found in the text == Unused Reference: 'RSVPMIB' is defined on line 861, but no explicit reference was found in the text == Unused Reference: 'ARCH' is defined on line 869, but no explicit reference was found in the text == Unused Reference: 'V1PROTO' is defined on line 873, but no explicit reference was found in the text == Unused Reference: 'V1SMI' is defined on line 877, but no explicit reference was found in the text == Unused Reference: 'V1CONCISE' is defined on line 882, but no explicit reference was found in the text == Unused Reference: 'V1TRAPS' is defined on line 886, but no explicit reference was found in the text == Unused Reference: 'V2SMI' is defined on line 890, but no explicit reference was found in the text == Unused Reference: 'V2TC' is defined on line 895, but no explicit reference was found in the text == Unused Reference: 'V2CONFORM' is defined on line 900, but no explicit reference was found in the text == Unused Reference: 'V2COMMUNITY' is defined on line 905, but no explicit reference was found in the text == Unused Reference: 'V2TRANS' is defined on line 909, but no explicit reference was found in the text == Unused Reference: 'V2PROTO' is defined on line 914, but no explicit reference was found in the text == Unused Reference: 'V3INTRO' is defined on line 919, but no explicit reference was found in the text == Unused Reference: 'V3MPC' is defined on line 924, but no explicit reference was found in the text == Unused Reference: 'V3USM' is defined on line 929, but no explicit reference was found in the text == Unused Reference: 'V3APPS' is defined on line 934, but no explicit reference was found in the text == Unused Reference: 'V3VACM' is defined on line 938, but no explicit reference was found in the text == Unused Reference: 'ASN1' is defined on line 943, but no explicit reference was found in the text == Unused Reference: 'ASN1BER' is defined on line 949, but no explicit reference was found in the text == Unused Reference: 'PROCESS' is defined on line 955, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'IS802' -- Possible downref: Non-RFC (?) normative reference: ref. 'SBM' -- Possible downref: Non-RFC (?) normative reference: ref. 'IS802MAP' ** Obsolete normative reference: RFC 2571 (ref. 'ARCH') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'V1PROTO') ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'V1TRAPS') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'V2COMMUNITY') ** Obsolete normative reference: RFC 1906 (ref. 'V2TRANS') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1905 (ref. 'V2PROTO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2570 (ref. 'V3INTRO') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2572 (ref. 'V3MPC') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. 'V3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2573 (ref. 'V3APPS') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. 'V3VACM') (Obsoleted by RFC 3415) -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ASN1BER' Summary: 19 errors (**), 0 flaws (~~), 29 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft A. Smith 2 Expires December 1999 Extreme Networks 3 draft-ietf-issll-is802-sbm-mib-00.txt R. Pabbati 4 Microsoft 5 June 1999 7 Definitions of Managed Parameters for SBM network nodes 9 Status of this Memo 11 This document is an Internet Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. Internet Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its Areas, and 14 its Working Groups. Note that other groups may also distribute working 15 documents as Internet Drafts. 17 Internet Drafts are draft documents valid for a maximum of six months. 18 Internet Drafts may be updated, replaced, or obsoleted by other 19 documents at any time. It is not appropriate to use Internet Drafts as 20 reference material or to cite them other than as a "working draft" or 21 "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Copyright (C) The Internet Society (1999). All Rights Reserved. 31 Abstract 33 This memo includes a list of manageable parameters for RSVP/SBM server 34 implementations. These are in addition to those already described in RFC 35 2206 and RFC 2213. Specifically, it describes parameters for control of 36 the base signaling protocols themselves, as well as some of the 37 admission control decisions. These definitions are not intended to be 38 exhaustive but they have been identified as useful for practical 39 implementations. 41 1. Introduction 43 SBM server components of the ISSLL/IS802 architecture require some 44 configuration parameters for operational use. These fall into 2 main 45 areas: configuration of RSVP protocol operation and configuration of 46 SBM-specific parts. For the former, RFC 2206 and RFC 2213 cover some 47 configuration operations as SNMP MIBS and some additional objectsd are 48 provided here. 50 1.1. Relationship to Other MIBs 52 1.1.1. Relationship to the 'system' group 54 In MIB-II, the 'system' group is defined as being mandatory for all 55 systems such that each managed entity contains one instance of each 56 object in the 'system' group. Thus, those objects apply to the entity 57 as a whole irrespective of whether the entity's sole functionality is 58 the SBM protocol or whether this is only a subset of the entity's 59 functionality. 61 1.1.2. Relation to Interfaces MIB 63 The Interface MIB Evolution [INTERFACEMIB], requires that any MIB which 64 is an adjunct of the Interface MIB, clarify specific areas within the 65 Interface MIB. These areas were intentionally left vague in the 66 Interface MIB Evolution to avoid over-constraining the MIB, thereby 67 precluding management of certain media-types. 69 1.1.3. 71 SBM interfaces which are capable of handling outgoing sessions should 72 each be represented by an entry in the per-interface tables of this MIB 73 [INTSERVMIB]. . 75 SBM interfaces which are capable of handling outgoing Guaranteed Service 76 sessions should be represented by an entry in intSrvGuaranteedIfTable 77 [INTSERVGSMIB. This entry can be used to characterise the delay 78 parameters that the SBM will use in its admission control algorithms. 80 2. Editorial information 82 84 2.1. Open Issues 86 (1) Should we include DCLASS as well as TCLASS config info here? 88 (2) How to represent more detailed e.g. per-queue/per-class 89 information. We could use the per-interface tables from 90 RFC2213/RFC2214 int-serv MIBs but we would then need one of these 91 per queue per interface. this might need ifStackTable to group them 92 together. Could also try to use the intSrvflowQueue object for 93 this. 95 (3) Should we allow creation of new SBM instances? MIB currently only 96 allows configuration of existing SBMs and assumes that the agent 97 will create SBM instances appropriately. 99 3. Definitions for SBM Server MIB 101 SBM-SERVER-MIB DEFINITIONS ::= BEGIN 103 -- ------------------------------------------------------------- 104 -- ------------------------------------------------------------- 106 IMPORTS 107 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32 108 FROM SNMPv2-SMI 109 TruthValue 110 FROM SNMPv2-TC 111 InterfaceIndex 112 FROM IF-MIB 113 SnmpAdminString 114 FROM SNMP-FRAMEWORK-MIB 115 MODULE-COMPLIANCE, OBJECT-GROUP 116 FROM SNMPv2-CONF 117 BurstSize, BitRate, MessageSize 118 FROM INTEGRATED-SERVICES-MIB; 120 -- 121 -- REFERENCE 122 -- "Resource Reservation Protocol (RSVP) - Version 1 Functional 123 -- Specification", RFC 2205" 124 -- 125 -- "SBM (Subnet Bandwidth Manager): A Protocol for Admission 126 -- Control over IEEE 802-style Networks" (draft-ietf-issll-sbm-08.txt) 128 sbmMIB MODULE-IDENTITY 129 LAST-UPDATED "9906100000Z" 130 ORGANIZATION "Extreme Networks, Inc." 131 CONTACT-INFO 132 " Andrew Smith 133 Phone: +1 408 579 2821 134 Email: andrew@extremenetworks.com" 136 " Ramesh Pabbati 137 Phone: +1 425 936 9438 138 Email: rameshpa@microsoft.com" 139 DESCRIPTION 140 "The SBM MIB module" 141 ::= { xxx 1 } 143 sbmMIBObjects OBJECT IDENTIFIER ::= { sbmMIB 1 } 145 -- ------------------------------------------------------------- 146 -- SBM Server Parameters 147 -- ------------------------------------------------------------- 149 sbmConfigTable OBJECT-TYPE 150 SYNTAX SEQUENCE OF SbmConfigEntry 151 MAX-ACCESS not-accessible 152 STATUS current 153 DESCRIPTION 154 "A table of configuration information per SBM instance. This might be 155 e.g. per-subnet for a shared LAN or per-network-interface for a switched 156 LAN. For a full-duplex switched LAN it might only represent the transmit 157 direction: in this case the receive controls will have no effect. 158 Entries in this table are created automatically by the agent when 159 a new SBM entity is created e.g. by addition of new physical hardware 160 or creation of a new subnet." 161 ::= { sbmMIBObjects 1 } 163 sbmConfigEntry OBJECT-TYPE 164 SYNTAX SbmConfigEntry 165 MAX-ACCESS not-accessible 166 STATUS current 167 DESCRIPTION 168 "A set of SBM protocol configuration variables for a given SBM instance." 169 INDEX { sbmIndex } 170 ::= { sbmConfigTable 1 } 172 SbmConfigEntry ::= 173 SEQUENCE { 174 sbmIndex Integer32, 175 sbmDescription SnmpAdminString, 176 sbmIfIndex InterfaceIndex, 177 sbmEnable TruthValue, 178 sbmDsbmRefreshInterval Integer32, 179 sbmDsbmDeadInterval Integer32, 180 sbmDsbmElectionPriority INTEGER, 181 sbmDsbmMaxNonResvTxBucketRate BitRate, 182 sbmDsbmMaxNonResvTxBucketDepth MessageSize, 183 sbmDsbmMaxNonResvTxPeakRate BitRate, 184 sbmDsbmMaxNonResvTxMinPolicedSize MessageSize, 185 sbmDsbmMaxNonResvTxMaxPacketSize MessageSize 186 } 188 sbmIndex OBJECT-TYPE 189 SYNTAX Integer32 190 MAX-ACCESS not-accessible 191 STATUS current 192 DESCRIPTION 193 "An integer representing a particular SBM instance." 194 ::= { sbmConfigEntry 1 } 196 sbmDescription OBJECT-TYPE 197 SYNTAX SnmpAdminString 198 MAX-ACCESS read-write 199 STATUS current 200 DESCRIPTION 201 "A description of this SBM instance." 202 ::= { sbmConfigEntry 2 } 204 sbmIfIndex OBJECT-TYPE 205 SYNTAX InterfaceIndex 206 MAX-ACCESS read-only 207 STATUS current 208 DESCRIPTION 209 "The interface index representing the domain of 210 control of this SBM instance: e.g. this might be a physical 211 interface on a switch device or it might be a subnet represented by 212 a propVirtual(53) interface entry. A value of 0 represents an SBM 213 instance that has no association to any one particular ifTable entry." 214 ::= { sbmConfigEntry 3 } 216 sbmEnable OBJECT-TYPE 217 SYNTAX TruthValue 218 MAX-ACCESS read-write 219 STATUS current 220 DESCRIPTION 221 "Enable SBM processing of messages." 222 DEFVAL { true } 223 ::= { sbmConfigEntry 4 } 225 sbmDsbmRefreshInterval OBJECT-TYPE 226 SYNTAX Integer32 227 UNITS "seconds" 228 MAX-ACCESS read-write 229 STATUS current 230 DESCRIPTION 231 "DSBM refresh interval." 232 DEFVAL { 5 } 233 ::= { sbmConfigEntry 5 } 235 sbmDsbmDeadInterval OBJECT-TYPE 236 SYNTAX Integer32 237 UNITS "seconds" 238 MAX-ACCESS read-write 239 STATUS current 240 DESCRIPTION 241 "DSBM Election dead time." 242 DEFVAL { 15 } 243 ::= { sbmConfigEntry 6 } 245 sbmDsbmElectionPriority OBJECT-TYPE 246 SYNTAX INTEGER (0..255) 247 MAX-ACCESS read-write 248 STATUS current 249 DESCRIPTION 250 "Election bid for this SBM to become DSBM." 251 DEFVAL { 4 } 252 ::= { sbmConfigEntry 7 } 254 sbmDsbmMaxNonResvTxBucketRate 255 SYNTAX BitRate 256 UNITS "bits per second" 257 MAX-ACCESS read-write 258 STATUS current 259 DESCRIPTION 260 "Maximum Bucket rate that can be sent with out a reservation. This is one 261 of the parameters of the effective Tspec that senders are allowed to use 262 before any reservation is in place." 263 REFERENCE "RFC2210 section 3.1" 264 ::= { sbmConfigEntry 8 } 266 sbmDsbmMaxNonResvTxBucketDepth 267 SYNTAX BurstSize 268 UNITS "bytes" 269 MAX-ACCESS read-write 270 STATUS current 271 DESCRIPTION 272 "Maximum Bucket Depth that can be sent with out a reservation. This is one 273 of the parameters of the effective Tspec that senders are allowed to use 274 before any reservation is in place." 275 REFERENCE "RFC2210 section 3.1" 276 ::= { sbmConfigEntry 9 } 278 sbmDsbmMaxNonResvTxPeakRate 279 SYNTAX BitRate 280 UNITS "bits per second" 281 MAX-ACCESS read-write 282 STATUS current 283 DESCRIPTION 284 "Maximum Peak rate that can be sent with out a reservation. This is 285 one of the parameters of the effective Tspec that senders are 286 allowed to use before any reservation is in place." 287 REFERENCE "RFC2210 section 3.1" 288 ::= { sbmConfigEntry 10 } 290 sbmDsbmMaxNonResvTxMinPolicedSize 291 SYNTAX MessageSize 292 UNITS "bytes" 293 MAX-ACCESS read-write 294 STATUS current 295 DESCRIPTION 296 "Minimum Policed size that can be sent with out a reservation. 297 This is one of the parameters of the effective Tspec that senders are 298 allowed to use before any reservation is in place." 300 REFERENCE "RFC2210 section 3.1" 301 ::= { sbmConfigEntry 11 } 303 sbmDsbmMaxNonResvTxMaxPacketSize 304 SYNTAX MessageSize 305 UNITS "bytes" 306 MAX-ACCESS read-write 307 STATUS current 308 DESCRIPTION 309 "Maximum packet length that can be sent with out a reservation. 310 This is one of the parameters of the effective Tspec that senders are 311 allowed to use before any reservation is in place." 312 REFERENCE "RFC2210 section 3.1" 313 ::= { sbmConfigEntry 12 } 315 sbmTrafficClassConfigTable OBJECT-TYPE 316 SYNTAX SEQUENCE OF SbmTrafficClassConfigEntry 317 MAX-ACCESS not-accessible 318 STATUS current 319 DESCRIPTION 320 "A table of parameters for configuring the characteristics of 321 the mapping of sessions into layer-2 traffic classes." 322 ::= { sbmMIBObjects 2 } 324 sbmTrafficClassConfigEntry OBJECT-TYPE 325 SYNTAX SbmTrafficClassConfigEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "A set of RSVP protocol configuration variables for a given SBM instance." 330 INDEX { sbmIndex, sbmTrafficClass } 331 ::= { sbmTrafficClassConfigTable 1 } 333 SbmTrafficClassConfigEntry ::= 334 SEQUENCE { 335 sbmTrafficClass INTEGER (0..7), 336 sbmDelayBoundTarget Integer32, 337 sbmTrafficClassEnabled TruthValue 338 } 340 sbmTrafficClass OBJECT-TYPE 341 SYNTAX INTEGER (0..7) 342 MAX-ACCESS read-write 343 STATUS current 344 DESCRIPTION 345 "Traffic Class (802.1p user_priority)." 346 ::= { sbmTrafficClassConfigEntry 1 } 348 sbmDelayBoundTarget OBJECT-TYPE 349 SYNTAX Integer32 350 UNITS "micro-seconds" 351 MAX-ACCESS read-write 352 STATUS current 353 DESCRIPTION 354 "Target delay bound on flows admitted to this class. 355 A value of 0 indicates that there is no quantitative delay bound 356 target associated with this class." 357 ::= { sbmTrafficClassConfigEntry 2 } 359 sbmTrafficClassEnabled OBJECT-TYPE 360 SYNTAX TruthValue 361 MAX-ACCESS read-write 362 STATUS current 363 DESCRIPTION 364 "Enable admission of flows to this class." 365 ::= { sbmTrafficClassConfigEntry 3 } 367 -- ------------------------------------------------------------- 368 -- RSVP Configuration Parameters 369 -- ------------------------------------------------------------- 371 sbmRsvpConfigTable OBJECT-TYPE 372 SYNTAX SEQUENCE OF SbmRsvpConfigEntry 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 376 "A table of configuration information per SBM instance. This might be 377 e.g. per-subnet for a shared LAN or per-network-interface for a 378 switched LAN. For a full-duplex switched LAN it might only represent 379 the transmit direction: in this case the receive controls will have 380 no effect." 381 ::= { sbmMIBObjects 3 } 383 sbmRsvpConfigEntry OBJECT-TYPE 384 SYNTAX SbmRsvpConfigEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "A set of RSVP protocol configuration variables for a given SBM instance." 390 INDEX { sbmIndex } 391 ::= { sbmRsvpConfigTable 1 } 393 SbmRsvpConfigEntry ::= 394 SEQUENCE { 395 sbmRsvpCopsEnabled TruthValue, 396 sbmRsvpSenderPolicyEnabled TruthValue, 397 sbmRsvpReceiverPolicyEnabled TruthValue, 398 } 400 sbmRsvpCopsEnabled OBJECT-TYPE 401 SYNTAX TruthValue 402 MAX-ACCESS read-write 403 STATUS current 404 DESCRIPTION 405 "Enable outsourcing of local policy decisions via the COPS protocol." 406 DEFVAL { false } 407 ::= { sbmRsvpConfigEntry 1 } 409 sbmRsvpSenderPolicyEnabled OBJECT-TYPE 410 SYNTAX TruthValue 411 MAX-ACCESS read-write 412 STATUS current 413 DESCRIPTION 414 "Enable processing of RSVP policy objects in PATH messages." 415 DEFVAL { false } 416 ::= { sbmRsvpConfigEntry 2 } 418 sbmRsvpReceiverPolicyEnabled OBJECT-TYPE 419 SYNTAX TruthValue 420 MAX-ACCESS read-write 421 STATUS current 422 DESCRIPTION 423 "Enable processing of RSVP policy objects in RESV messages." 424 DEFVAL { false } 425 ::= { sbmRsvpConfigEntry 3 } 427 -- ------------------------------------------------------------- 428 -- SBM statistics 429 -- ------------------------------------------------------------- 431 sbmStatsTable OBJECT-TYPE 432 SYNTAX SEQUENCE OF SbmStatsEntry 433 MAX-ACCESS not-accessible 434 STATUS current 435 DESCRIPTION 436 "A table of statistics per SBM instance. This might be e.g. per-subnet 437 for a shared LAN or per-network-interface for a switched LAN. For a 438 full-duplex switched LAN it might only represent the transmit 439 direction: in this case the receive statistics may be zero." 440 ::= { sbmMIBObjects 4 } 442 sbmStatsEntry OBJECT-TYPE 443 SYNTAX SbmStatsEntry 444 MAX-ACCESS not-accessible 445 STATUS current 446 DESCRIPTION 447 "A set of SBM protocol statistics for a given SBM instance." 448 INDEX { sbmIndex } 449 ::= { sbmStatsTable 1 } 451 SbmStatsEntry ::= 452 SEQUENCE { 453 sbmStatsSbmSentBytes Counter32, 454 sbmStatsSbmReceivedBytes Counter32, 455 sbmStatsReceivedRsvpPathMsgs Counter32, 456 sbmStatsReceivedRsvpResvMsgs Counter32, 457 sbmStatsReceivedRsvpPathErrMsgs Counter32, 458 sbmStatsReceivedRsvpResvErrMsgs Counter32, 459 sbmStatsReceivedRsvpPathTearMsgs Counter32, 460 sbmStatsReceivedRsvpResvTearMsgs Counter32, 461 sbmStatsReceivedRsvpConfirmMsgs Counter32, 462 sbmStatsReceivedRsvpBadMsgs Counter32, 463 sbmStatsSentRsvpPathMsgs Counter32, 464 sbmStatsSentRsvpResvMsgs Counter32, 465 sbmStatsSentRsvpPathErrMsgs Counter32, 466 sbmStatsSentRsvpResvErrMsgs Counter32, 467 sbmStatsSentRsvpPathTearMsgs Counter32, 468 sbmStatsSentRsvpResvTearMsgs Counter32, 469 sbmStatsSentRsvpConfirmMsgs Counter32, 470 sbmStatsAdmissionControlFailures Counter32, 471 sbmStatsInPolicyControlFailures Counter32, 472 sbmStatsOutPolicyControlFailures Counter32, 473 sbmStatsOtherFailures Counter32, 474 sbmStatsInBlockadeStateResvs Counter32, 475 sbmStatsResvTimeOuts Counter32, 476 sbmStatsPathTimeOuts Counter32, 477 sbmStatsReceiveFailsBigMsg Counter32, 478 sbmStatsSendFailsBigMsg Counter32, 479 sbmStatsReceiveFailsNoResource Counter32, 480 sbmStatsSendFailsNoResource Counter32, 481 sbmStatsActiveOutgoingFlows Counter32, 482 sbmStatsAllocatedOutgoingBits Counter32, 483 sbmStatsMaxAllocatedBandwidthBits Counter32 484 } 486 sbmStatsSbmSentBytes OBJECT-TYPE 487 SYNTAX Counter32 488 UNITS "bytes" 489 MAX-ACCESS read-only 490 STATUS current 491 DESCRIPTION 492 "" 493 ::= { sbmStatsEntry 1 } 495 sbmStatsSbmReceivedBytes OBJECT-TYPE 496 SYNTAX Counter32 497 UNITS "bytes" 498 MAX-ACCESS read-only 499 STATUS current 500 DESCRIPTION 501 "" 502 ::= { sbmStatsEntry 2 } 504 sbmStatsReceivedRsvpPathMsgs OBJECT-TYPE 505 SYNTAX Counter32 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "" 510 ::= { sbmStatsEntry 3 } 512 sbmStatsReceivedRsvpResvMsgs OBJECT-TYPE 513 SYNTAX Counter32 514 MAX-ACCESS read-only 515 STATUS current 516 DESCRIPTION 517 "" 518 ::= { sbmStatsEntry 4 } 520 sbmStatsReceivedRsvpPathErrMsgs OBJECT-TYPE 521 SYNTAX Counter32 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "" 526 ::= { sbmStatsEntry 5 } 528 sbmStatsReceivedRsvpResvErrMsgs OBJECT-TYPE 529 SYNTAX Counter32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION 533 "" 534 ::= { sbmStatsEntry 6 } 536 sbmStatsReceivedRsvpPathTearMsgs OBJECT-TYPE 537 SYNTAX Counter32 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "" 542 ::= { sbmStatsEntry 7 } 544 sbmStatsReceivedRsvpResvTearMsgs OBJECT-TYPE 545 SYNTAX Counter32 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "" 550 ::= { sbmStatsEntry 8 } 552 sbmStatsReceivedRsvpConfirmMsgs OBJECT-TYPE 553 SYNTAX Counter32 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "" 558 ::= { sbmStatsEntry 9 } 560 sbmStatsReceivedRsvpBadMsgs OBJECT-TYPE 561 SYNTAX Counter32 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "Bad syntax or semantics." 566 ::= { sbmStatsEntry 10 } 568 sbmStatsSentRsvpPathMsgs OBJECT-TYPE 569 SYNTAX Counter32 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "" 574 ::= { sbmStatsEntry 11 } 576 sbmStatsSentRsvpResvMsgs OBJECT-TYPE 577 SYNTAX Counter32 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "" 582 ::= { sbmStatsEntry 12 } 584 sbmStatsSentRsvpPathErrMsgs OBJECT-TYPE 585 SYNTAX Counter32 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "" 590 ::= { sbmStatsEntry 13 } 592 sbmStatsSentRsvpResvErrMsgs OBJECT-TYPE 593 SYNTAX Counter32 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "" 598 ::= { sbmStatsEntry 14 } 600 sbmStatsSentRsvpPathTearMsgs OBJECT-TYPE 601 SYNTAX Counter32 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "" 606 ::= { sbmStatsEntry 15 } 608 sbmStatsSentRsvpResvTearMsgs OBJECT-TYPE 609 SYNTAX Counter32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "" 615 ::= { sbmStatsEntry 16 } 617 sbmStatsSentRsvpConfirmMsgs OBJECT-TYPE 618 SYNTAX Counter32 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "" 623 ::= { sbmStatsEntry 17 } 625 sbmStatsAdmissionControlFailures OBJECT-TYPE 626 SYNTAX Counter32 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "" 631 ::= { sbmStatsEntry 18 } 633 sbmStatsInPolicyControlFailures OBJECT-TYPE 634 SYNTAX Counter32 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "" 639 ::= { sbmStatsEntry 19 } 641 sbmStatsOutPolicyControlFailures OBJECT-TYPE 642 SYNTAX Counter32 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "" 647 ::= { sbmStatsEntry 20 } 649 sbmStatsOtherFailures OBJECT-TYPE 650 SYNTAX Counter32 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "" 655 ::= { sbmStatsEntry 21 } 657 sbmStatsInBlockadeStateResvs OBJECT-TYPE 658 SYNTAX Counter32 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "" 663 ::= { sbmStatsEntry 22 } 665 sbmStatsResvTimeOuts OBJECT-TYPE 666 SYNTAX Counter32 667 MAX-ACCESS read-only 668 STATUS current 669 DESCRIPTION 670 "" 671 ::= { sbmStatsEntry 23 } 673 sbmStatsPathTimeOuts OBJECT-TYPE 674 SYNTAX Counter32 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "" 679 ::= { sbmStatsEntry 24 } 681 sbmStatsReceiveFailsBigMsg OBJECT-TYPE 682 SYNTAX Counter32 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "" 687 ::= { sbmStatsEntry 25 } 689 sbmStatsSendFailsBigMsg OBJECT-TYPE 690 SYNTAX Counter32 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "" 695 ::= { sbmStatsEntry 26 } 697 sbmStatsReceiveFailsNoResource OBJECT-TYPE 698 SYNTAX Counter32 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "" 703 ::= { sbmStatsEntry 27 } 705 sbmStatsSendFailsNoResource OBJECT-TYPE 706 SYNTAX Counter32 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "" 711 ::= { sbmStatsEntry 28 } 713 sbmStatsActiveOutgoingFlows OBJECT-TYPE 714 SYNTAX Counter32 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "" 719 ::= { sbmStatsEntry 29 } 721 sbmStatsAllocatedOutgoingBits OBJECT-TYPE 722 SYNTAX Counter32 723 UNITS "bps" 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "" 728 ::= { sbmStatsEntry 30 } 730 sbmStatsMaxAllocatedBandwidthBits OBJECT-TYPE 731 SYNTAX Counter32 732 UNITS "bps" 733 MAX-ACCESS read-only 734 STATUS current 735 DESCRIPTION 736 "" 737 ::= { sbmStatsEntry 31 } 739 -- ------------------------------------------------------------- 740 -- Conformance Information 741 -- ------------------------------------------------------------- 743 sbmConformance OBJECT IDENTIFIER ::= { sbmMIB 2 } 745 sbmGroups OBJECT IDENTIFIER ::= { sbmConformance 1 } 746 sbmCompliances OBJECT IDENTIFIER ::= { sbmConformance 2 } 748 -- ------------------------------------------------------------- 749 -- units of conformance 750 -- ------------------------------------------------------------- 752 sbmSbmConfigGroup OBJECT-GROUP 753 OBJECTS { 754 sbmIfIndex, sbmEnable, sbmDsbmRefreshInterval, 755 sbmDsbmDeadInterval, sbmDsbmElectionPriority, 756 sbmTrafficClass, sbmDelayBoundTarget, 757 sbmTrafficClassEnabled 758 } 759 STATUS current 760 DESCRIPTION 761 "A collection of objects providing per-SBM control over operation 762 of the SBM protocol." 763 ::= { sbmGroups 1 } 765 sbmRsvpConfigGroup OBJECT-GROUP 766 OBJECTS { 767 sbmRsvpEnabled, sbmRsvpCopsEnabled, 768 sbmRsvpSenderPolicyEnabled, sbmRsvpReceiverPolicyEnabled, 769 sbmRsvpGsDelay, sbmRsvpGsSlack 770 } 771 STATUS current 772 DESCRIPTION 773 "A collection of objects providing per-SBM control over operation 774 of the RSVP protocol." 775 ::= { sbmGroups 2 } 777 sbmSbmStatisticsGroup OBJECT-GROUP 778 OBJECTS { 779 sbmStatsSbmSentBytes, sbmStatsSbmReceivedBytes, 780 sbmStatsReceivedRsvpPathMsgs, 781 sbmStatsReceivedRsvpResvMsgs, 782 sbmStatsReceivedRsvpPathErrMsgs, 783 sbmStatsReceivedRsvpResvErrMsgs, 784 sbmStatsReceivedRsvpPathTearMsgs, 785 sbmStatsReceivedRsvpResvTearMsgs, 786 sbmStatsReceivedRsvpConfirmMsgs, 787 sbmStatsSentRsvpPathMsgs, sbmStatsSentRsvpResvMsgs, 788 sbmStatsSentRsvpPathErrMsgs, sbmStatsSentRsvpResvErrMsgs, 789 sbmStatsSentRsvpPathTearMsgs, 790 sbmStatsSentRsvpResvTearMsgs, 791 sbmStatsSentRsvpConfirmMsgs, 792 sbmStatsAdmissionControlFailures, 793 sbmStatsInPolicyControlFailures, 794 sbmStatsOutPolicyControlFailures, sbmStatsOtherFailures, 795 sbmStatsInBlockadeStateResvs, sbmStatsResvTimeOuts, 796 sbmStatsPathTimeOuts, sbmStatsReceiveFailsBigMsg, 797 sbmStatsSendFailsBigMsg, sbmStatsReceiveFailsNoResource, 798 sbmStatsSendFailsNoResource, 799 sbmStatsActiveOutgoingFlows, 800 sbmStatsAllocatedOutgoingBits, 801 sbmStatsMaxAllocatedBandwidthBits 802 } 803 STATUS current 804 DESCRIPTION 805 "A collection of objects providing per-SBM statistics of RSVP 806 protocol operations." 807 ::= { sbmGroups 3 } 809 -- ------------------------------------------------------------- 810 -- compliance statements 811 -- ------------------------------------------------------------- 813 sbmCompliance MODULE-COMPLIANCE 814 STATUS current 815 DESCRIPTION 816 "The compliance statement for SNMP entities 817 which manage SBM protocol entities." 819 MODULE -- this module 820 MANDATORY-GROUPS 821 { 822 sbmSbmConfigGroup, 823 sbmRsvpConfigGroup, 824 sbmSbmStatisticsGroup 825 } 827 OBJECT sbmRsvpEnabled 828 MIN-ACCESS read-only 829 DESCRIPTION 830 "Read-only access is allowed." 832 ::= { sbmCompliances 1 } 834 END 836 4. References 837 [RSVP] 838 Braden, R., L. Zhang, S. Berson, S. Herzog, S. Jamin, "Resource 839 Reservation Protocol (RSVP) - Version 1 Functional Specification", 840 RFC 2205, September 1997 842 [IS802] 843 Ghanwani, A., Pace, W., Srinivasan, V., Smith, A., Seaman, M., "A 844 Framework for Providing Integrated Services Over Shared and 845 Switched LAN Technologies", Internet Draft, April 1999. 846 http://www.ietf.org/internet-drafts/draft-ietf-issll- 847 is802-framework-06.txt 849 [SBM] 850 Yavatkar, R., Hoffman, D., Bernet, Y., Baker, F., Speer, M., "SBM 851 (Subnet Bandwidth Manager): A Protocol for Admission Control over 852 IEEE 802-style Networks", Internet Draft, April 1999. 853 http://www.ietf.org/internet-drafts/draft-ietf-issll-sbm-08.txt 855 [IS802MAP] 856 Seaman, M., Smith, A., Crawley, E., "Integrated Service Mappings on 857 IEEE 802 Networks", Internet Draft, Cmetric, Extreme Networks, 858 Argon Networks, June 1999. http://www.ietf.org/internet- 859 drafts/draft-ietf-issll-is802-svc-mapping-04.txt 861 [RSVPMIB] 862 Baker, F., Krawczyk, J., Sastry, A., "RSVP Management Information 863 Base using SMIv2", RFC 2206, Sepember 1997 865 [INTSERVMIB] 866 Baker, F., Krawczyk, J., Sastry, A., "Integrated Services 867 Management Information Base using SMIv2", RFC 2213, Sepember 1997 869 [ARCH] 870 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 871 Describing SNMP Management Frameworks", RFC 2571, April 1999 873 [V1PROTO] 874 Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network 875 Management Protocol", RFC 1157, May 1990. 877 [V1SMI] 878 Rose, M., and K. McCloghrie, "Structure and Identification of 879 Management Information for TCP/IP-based Internets", RFC 1155, May 880 1990 882 [V1CONCISE] 883 Rose, M. and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 884 March 1991 886 [V1TRAPS] 887 M. Rose, "A Convention for Defining Traps for use with the SNMP", 888 RFC 1215, March 1991 890 [V2SMI] 891 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 892 and S. Waldbusser, "Structure of Management Information Version 2 893 (SMIv2)", STD 58, RFC 2578, April 1999. 895 [V2TC] 896 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 897 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 898 2579, April 1999. 900 [V2CONFORM] 901 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. 902 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 903 2580, April 1999. 905 [V2COMMUNITY] 906 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction 907 to Community-based SNMPv2", RFC 1901, January 1996. 909 [V2TRANS] 910 Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 911 Mappings for Version 2 of the Simple Network Management Protocol 912 (SNMPv2)", RFC 1906, January 1996. 914 [V2PROTO] 915 Case, J., McCloghrie, K., Rose, M. and Waldbusser, S., "Protocol 916 Operations for Version 2 of the Simple Network Management Protocol 917 (SNMPv2)", RFC 1905, January 1996. 919 [V3INTRO] 920 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to 921 Version 3 of the Internet-standard Network Management Framework", 922 RFC 2570, April 1999. 924 [V3MPC] 925 Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 926 Processing and Dispatching for the Simple Network Management 927 Protocol (SNMP)", RFC 2572, April 1999. 929 [V3USM] 930 Blumenthal, U. and B. Wijnen, "The User-Based Security Model (USM) 931 for Version 3 of the Simple Network Management Protocol (SNMPv3)", 932 RFC 2574, April 1999. 934 [V3APPS] 935 Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 2573, 936 April 1999. 938 [V3VACM] 939 Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 940 Control Model for the Simple Network Management Protocol (SNMP)", 941 RFC 2575, April 1999. 943 [ASN1] 944 Information processing systems - Open Systems Interconnection - 945 Specification of Abstract Syntax Notation One (ASN.1), 946 International Organization for Standardization, International 947 Standard 8824, December 1987. 949 [ASN1BER] 950 Information processing systems - Open Systems Interconnection - 951 Specification of Basic Encoding Rules for Abstract Notation One 952 (ASN.1), International Organization for Standardization, 953 International Standard 8825, December 1987. 955 [PROCESS] 956 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, 957 RFC 2026, October 1996. 959 5. Security Considerations 961 There are a number of management objects defined in this MIB that have a 962 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 963 considered sensitive or vulnerable in some network environments. The 964 support for SET operations in a non-secure environment without proper 965 protection can have a negative effect on network operations. 967 SNMPv1 by itself is not a secure environment. Even if the network 968 itself is secure (for example by using IPSec), even then, there is no 969 control as to who on the secure network is allowed to access and GET/SET 970 (read/change/create/delete) the objects in this MIB. 972 It is recommended that the implementers consider the security features 973 as provided by the SNMPv3 framework. Specifically, the use of the User- 974 based Security Model [USM] and the View-based Access Control Model 975 [VACM] is recommended. 977 It is then a customer/user responsibility to ensure that the SNMP entity 978 giving access to an instance of this MIB, is properly configured to give 979 access to the objects only to those principals (users) that have 980 legitimate rights to indeed GET or SET (change/create/delete) them. 982 6. Authors' Addresses 984 Andrew Smith 985 Extreme Networks 986 3585 Monroe St. 987 Santa Clara CA 95051 988 USA 989 Phone: +1 408 579 2821 990 EMail: andrew@extremenetworks.com 992 Ramesh Pabbati 993 Microsoft 994 1 Microsoft Way 995 Redmond, WA 98052 996 USA 997 Phone: +1 206 936 9438 998 Email: rameshpa@microsoft.com 1000 Copyright (C) The Internet Society (1999). All Rights Reserved. 1002 This document and translations of it may be copied and furnished 1003 to others, and derivative works that comment on or otherwise 1004 explain it or assist in its implmentation may be prepared, copied, 1005 published and distributed, in whole or in part, without 1006 restriction of any kind, provided that the above copyright notice 1007 and this paragraph are included on all such copies and derivative 1008 works. However, this document itself may not be modified in any 1009 way, such as by removing the copyright notice or references to the 1010 Internet Society or other Internet organizations, except as needed 1011 for the purpose of developing Internet standards in which case the 1012 procedures for copyrights defined in the Internet Standards 1013 process must be followed, or as required to translate it into 1014 languages other than English. 1016 The limited permissions granted above are perpetual and will not 1017 be revoked by the Internet Society or its successors or assigns. 1019 This document and the information contained herein is provided on 1020 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1021 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1022 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1023 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1024 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.