idnits 2.17.1 draft-ietf-atommib-sonetaps-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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 36 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** 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 90 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 == Line 257 has weird spacing: '...created in th...' == Line 565 has weird spacing: '...dicates unidi...' == Line 738 has weird spacing: '...tecture and K...' == Line 1001 has weird spacing: '...set the corre...' == Line 1372 has weird spacing: '... "The apsCo...' -- 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 (December 7, 1999) is 8904 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) -- Looks like a reference, but probably isn't: 'RFC2574' on line 1603 -- Looks like a reference, but probably isn't: 'RFC2575' on line 1604 == Unused Reference: '17' is defined on line 1577, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1580, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2233 (ref. '17') (Obsoleted by RFC 2863) -- Possible downref: Non-RFC (?) normative reference: ref. '18' == Outdated reference: A later version (-01) exists of draft-kchapman-sonet-aps-00 -- Possible downref: Normative reference to a draft: ref. '19' Summary: 19 errors (**), 0 flaws (~~), 11 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT SONET LINEAR APS MIB J. Johnson 2 Expires June 7, 2000 M. Thatcher 3 J. Kuhfeld 4 Redback Networks 5 December 7, 1999 7 Definitions of Managed Objects 8 for SONET Linear APS architectures 10 draft-ietf-atommib-sonetaps-mib-00.txt 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet- Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Copyright Notice 35 Copyright (C) The Internet Society 1999. All Rights Reserved. 37 Abstract 39 This memo defines a portion of the Management Information Base (MIB) 40 for use with network management protocols in TCP/IP based internets. 41 In particular it defines objects for managing networks using SONET 42 linear Automatic Protection Switching (APS) architectures. 44 This memo specifies a MIB module in a manner that is both compliant 45 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 46 definitions. 48 1. Introduction 50 This memo defines a portion of the Management Information Base (MIB) 51 used for managing SONET linear Automatic Protection Switching (APS) 52 architectures. Two linear APS architectures are supported, the 1+1 53 architecture and the 1:n architecture. 55 1.1 Change Log 57 This section lists changes made in the Internet Draft revisions of 58 this document. 60 December 7, 1999 62 The following changes were made for the version of this document 63 dated December 7, 1999. 65 The ApsK1K2 TEXTUAL-CONVENTION was changed from an Integer32 to OCTET 66 STRING (SIZE (2)) (borrowed from draft-kchapman-sonet-aps-mib-00.txt 67 [19]). 69 The command table is indexed by group and channel rather than group 70 only. In apsCommandEntry INDEX specification, IMPLIED was removed 71 from apsConfigName and apsChanNumber was added. This allows the use 72 of simple command enumeration rather than "cryptic" Integer32 values 73 combining channel and command (a variation on command handling in 74 draft-kchapman-sonet-aps-mib-00.txt [19]). 76 A number of DESCRIPTION fields have been expanded. 78 Far-End Protection Line Failure conditions are now monitored. The bit 79 feplf was added to apsStatusCurrent, the Counter32 apsStatusFEPLFs 80 was added to ApsStatusEntry, and the the NOTIFICATION-TYPE 81 apsTrapFEPLF was created (borrowed from draft-kchapman-sonet-aps- 82 mib-00.txt [19]). 84 The apsChanIfIndex DESCRIPTION indicates that it is an interface with 85 ifType sonet(39) (feedback from Kaj Tesink). 87 DisplayString objects apsConfigName and apsChanGroupName were changed 88 to SnmpAdminString (feedback from Kaj Tesink). 90 apsChanGroupName SYNTAX was changed to SnmpAdminString (SIZE (1..32)) 91 in order to be consistent with apsConfigName. 93 Channel configuration is enacted by creating rows in 94 apsChanConfigTable which is indexed by group name and channel number. 95 (a variation on channel creation in draft-kchapman-sonet-aps- 96 mib-00.txt [19]). 98 apsStatusCreationTime was renamed apsConfigCreationTime and moved 99 from apsStatusTable to apsConfigTable, since it is associated with 100 row creation in that table. 102 June 28, 1999 104 The following changes were made for the version of this document 105 dated June 28, 1999. 107 References to Protection Switch Byte Failure (PSBF) conditions were 108 moved from the channel table to the group status table. Specifically, 109 the psbf failure bit was moved from apsChanStatus to 110 apsStatusCurrent, apsChanPSBFs was deleted and replaced with 111 apsStatusPSBFs and the NOTIFICATION-TYPE apsTrapPSBF was created. 112 (feedback from Ken Chapman) 114 2. The SNMP Management Framework 116 The SNMP Management Framework presently consists of five major 117 components: 119 An overall architecture, described in RFC 2571 [1]. 121 Mechanisms for describing and naming objects and events for the 122 purpose of management. The first version of this Structure of 123 Management Information (SMI) is called SMIv1 and described in RFC 124 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 125 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 127 Message protocols for transferring management information. The first 128 version of the SNMP message protocol is called SNMPv1 and described 129 in RFC 1157 [8]. A second version of the SNMP message protocol, which 130 is not an Internet standards track protocol, is called SNMPv2c and 131 described in RFC 1901 [9] and RFC 1906 [10]. The third version of the 132 message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 133 2572 [11] and RFC 2574 [12]. 135 Protocol operations for accessing management information. The first 136 set of protocol operations and associated PDU formats is described in 137 RFC 1157 [8]. A second set of protocol operations and associated PDU 138 formats is described in RFC 1905 [13]. 140 A set of fundamental applications described in RFC 2573 [14] and the 141 view-based access control mechanism described in RFC 2575 [15]. 143 A more detailed introduction to the current SNMP Management Framework 144 can be found in RFC 2570 [16]. 146 Managed objects are accessed via a virtual information store, termed 147 the Management Information Base or MIB. Objects in the MIB are 148 defined using the mechanisms defined in the SMI. 150 This memo specifies a MIB module that is compliant to the SMIv2. A 151 MIB conforming to the SMIv1 can be produced through the appropriate 152 translations. The resulting translated MIB must be semantically 153 equivalent, except where objects or events are omitted because no 154 translation is possible (use of Counter64). Some machine readable 155 information in SMIv2 will be converted into textual descriptions in 156 SMIv1 during the translation process. However, this loss of machine 157 readable information is not considered to change the semantics of the 158 MIB. 160 3. Object Definitions 162 Managed objects are accessed via a virtual information store, termed 163 the Management Information Base or MIB. Objects in the MIB are 164 defined using the subset of Abstract Syntax Notation One (ASN.1) 165 defined in the SMI. In particular, each object type is named by an 166 OBJECT IDENTIFIER, an administratively assigned name. The object 167 type together with an object instance serves to uniquely identify a 168 specific instantiation of the object. For human convenience, we 169 often use a textual string, termed the descriptor, to refer to the 170 object type. 172 4. Overview 174 These objects are used to control and manage SONET linear APS 175 architectures. 177 The mib contains two scalars, containing counts of APS groups and 178 SONET LTEs respectively and six tables: apsMapTable, 179 apsChanConfigTable, apsConfigTable, apsCommandTable, 180 apsChanStatusTable and apsStatusTable. The apsMapTable provides a 181 list of SONET LTE interfaces available on the system. The 182 apsChanConfigTable supports addition, modification and deletion of 183 entries representing linear APS channels. The apsConfigTable 184 supports addition, modification and deletion of entries representing 185 linear APS groups. The apsCommandTable provides linear APS commands 186 that support protection switching and the ability to modify APS 187 operation. The apsChanStatusTable provides individual channel 188 statistics. The apsStatusTable provides group level statistics. 190 5. Definitions 192 RBN-APS-MIB DEFINITIONS ::= BEGIN 194 IMPORTS 195 MODULE-IDENTITY, TimeTicks, 196 OBJECT-IDENTITY 197 FROM SNMPv2-SMI 198 rbnMgmt 199 FROM RBN-SMI; 201 rbnApsMIB MODULE-IDENTITY 202 LAST-UPDATED "9912072300Z" 203 ORGANIZATION "RedBack Networks, Inc." 204 CONTACT-INFO 205 " RedBack Networks, Inc. 207 Postal: 1389 Moffett Park Drive 208 Sunnyvale, CA 94089-1134 209 USA 211 Phone: +1 408 548 3500 212 Fax: +1 408 548 3599 214 E-mail: mib-info@RedBackNetworks.com" 215 DESCRIPTION 216 "This management information module supports the configuration and 217 management of SONET linear APS groups. The definitions and 218 descriptions used in this mib have been derived from 219 GR-253-CORE Revision 2, January 1999, section 5.3. 221 Ring APS groups are not currently supported by this mib. 223 The mib contains six tables. 225 The apsMapTable contains entries for each SONET LTE 226 interface available on the system. The table serves two 227 purposes. It can be used to locate SONET LTE 228 interfaces that are not currently included in 229 APS groups. It also provides a mapping from InterfaceIndex 230 to group name and channel number for those SONET LTE 231 interfaces that are included in APS groups. 232 Entries in apsMapTable cannot be added or deleted 233 through operations defined in this mib. However, an 234 apsMapEntry may be added or deleted through other system 235 mechanisms, such as hot swap. 237 The apsChanConfigTable supports addition, modification and 238 deletion of entries representing linear APS channels. 239 Entries are indexed by a text group name and integer channel 240 number. Each entry contains an InterfaceIndex value identifying 241 the SONET LTE used for the channel and the priority of the 242 channel. A side effect of row creation or deletion is 243 creation or deletion of corresponding command and 244 channel status entries, and the setting of map entry 245 fields. Creation of 2-14 entries in this table with a 246 common group name index and consecutive channel numbers 247 beginning with zero is the first step in the creation 248 and configuration of an APS group. It is not necessary 249 to create channel numbers in order, however the resulting 250 set of channels must begin with channel number 0 and 251 must be consecutive. 253 The apsConfigTable supports addition, modification and deletion of 254 entries representing linear APS groups. Entries are indexed by a 255 text group name. Each entry contains parameters that specify the 256 configuration of a particular linear APS group. Entries are 257 created in this table after a set of channels are created 258 in the apsChanConfigTable. In order to successfully set an 259 instance of apsConfigRowStatus to active the apsConfigEntry 260 must contain valid values and all associated apsChanConfigEntry 261 rows must be valid and produce a consecutive set of channels 262 beginning with channel number 0. 264 The apsCommandTable provides linear APS commands that support 265 protection switching and the ability to modify APS operation. 266 Commands may only be entered if the corresponding 267 apsConfigRowStatus instance is set to active. Entries in this 268 table are created as a side effect of row addition in the 269 apsChanConfigTable. 271 The apsChanStatusTable provides individual channel statistics. 272 Entries in this table are created as a side effect of row 273 addition in the apsChanConfigTable. 275 The apsStatusTable provides group level statistics. Entries in 276 this table are created as a side effect of row addition in 277 apsConfigTable. 279 An APS group is created and configured with the following sequence 280 of events: 282 CHANNEL CONFIGURATION 284 Create an entry in the apsChanConfigTable 285 Set the apsChanGroupName in an apsChanConfigEntry to a 286 user-friendly text string which will serve as the 287 APS group name. The string must not be equal to 288 the apsConfigName of an existing apsConfigEntry with 289 apsConfigRowStatus set to active, since a channel cannot be 290 added to an active group. The string may be set equal 291 to the apsConfigName of a row which is currently not 292 set to active, or it may be set to a string which does 293 not currently exist in any instance of apsConfigName. 294 A channel number is entered in apsChanNumber. 295 A channel priority is entered in apsChanPriority, if 296 the intended architecture is 1:n. apsChanPriority is 297 ignored if the architecture is 1+1. The InterfaceIndex 298 value of a SONET LTE interface is entered in apsChanIfIndex. 300 This step is repeated for all apsChanConfigEntry instances 301 which are to be included in the APS group. 303 ACTIVATING THE GROUP 305 If the apsChanGroupName does not exist in an instance 306 of apsConfigName, an apsConfigEntry is created with 307 the apsChanGroupName value used as the index for the row. 308 The apsConfigRowStatus value may be set to createAndGo. 309 The apsGroupConfigEntry and apsChanConfigEntry instances with 310 matching name fields will be checked for consistency. 311 If any errors in the channel numbers, architecture or 312 configuration are uncovered the apsConfigRowStatus set 313 will return inconsistentValue, otherwise noError is returned. 315 If the apsChanGroupName value used in channel configuration 316 exists in a previously created, inactive apsConfigEntry instance, 317 the apsConfigRowStatus value may be set to active. 318 " 320 REVISION "9912072300Z" 321 DESCRIPTION 322 "A draft version of the linear APS MIB." 323 ::= { rbnMgmt 5 } 325 rbnApsMIBNotifications OBJECT IDENTIFIER 326 ::= { rbnApsMIB 0 } 328 rbnApsMIBObjects OBJECT IDENTIFIER 329 ::= { rbnApsMIB 1 } 331 rbnApsMIBConformance OBJECT IDENTIFIER 332 ::= { rbnApsMIB 2 } 334 ApsK1K2 ::= TEXTUAL-CONVENTION 335 STATUS current 336 DESCRIPTION 337 "This Textual Convention describes an object that stores 338 a SONET K1 and K2 byte APS protocol field. 340 K1 is located in the first octet, K2 is located in 341 the second octet. 343 Bits 1-4 of the K1 byte indicate a request. 345 1111 Lockout of Protection 346 1110 Forced Switch 347 1101 SF - High Priority 348 1100 SF - Low Priority 349 1011 SD - High Priority 350 1010 SD - Low Priority 351 1001 not used 352 1000 Manual Switch 353 0111 not used 354 0110 Wait-to-Restore 355 0101 not used 356 0100 Exercise 357 0011 not used 358 0010 Reverse Request 359 0001 Do Not Revert 360 0000 No Request 362 Bits 5-8 of the K1 byte indicate the channel associated with the 363 request defined in bits 1-4. 365 0000 is the Null channel 367 1-14 are working channels. 368 15 is the extra traffic channel 370 Bits 1-4 of the K2 byte indicate a channel. The channel is 371 defined with the same syntax as K1 Bits 5-8. 373 Bit 5 of the K2 byte indicates the 374 architecture. 376 0 if the architecture is 1+1 377 1 if the architecture is 1:n 379 Bits 6-8 of the K2 byte indicates the 380 mode. 382 000 - 011 are reserved for future use 384 100 indicates the mode is unidirectional 385 101 indicates the mode is bidirectional 387 110 RDI-L 389 111 AIS-L 390 " 391 REFERENCE 392 "Bellcore (Telcordia Technologies) GR-253-CORE, Issue 2, 393 Revision 2 (January 1999), 5.3.5." 394 SYNTAX OCTET STRING (SIZE (2)) 396 ApsSwitchCommand ::= TEXTUAL-CONVENTION 397 STATUS current 398 DESCRIPTION 399 "An APS switch command allows a user to perform protection 400 switch actions. 402 The Switch command values are: 404 clear(1) 406 Clears all of the switch commands listed below for the specified 407 channel. 409 lockoutOfProtection(2) 411 Prevents any of the working channels from switching to the protection 412 line. 414 forcedSwitchWorkToProtect(3) 416 Switches the specified working channel to the protection line. 418 forcedSwitchProtectToWork(4) 419 Switches the working channel back from the protection line to 420 the working line. 422 manualSwitchWorkToProtect(5) 424 Switches the specified working channel to the protection line. 426 manualSwitchProtectToWork(6) 428 Switches the working channel back from the protection line to 429 the working line. 431 exercise(7) 433 Exercises the protocol for a protection switch of the specified 434 channel by issuing an Exercise request for that channel and 435 checking the response on the APS channel. 436 " 437 SYNTAX INTEGER { 438 clear(1), 439 lockoutOfProtection(2), 440 forcedSwitchWorkToProtect(3), 441 forcedSwitchProtectToWork(4), 442 manualSwitchWorkToProtect(5), 443 manualSwitchProtectToWork(6), 444 exercise(7) 445 } 447 ApsControlCommand ::= TEXTUAL-CONVENTION 448 STATUS current 449 DESCRIPTION 450 "An APS control command applies only to LTE that support the 451 1:n architecture and performs the following actions. 453 The Control command values are: 455 lockoutWorkingChannel(1) 457 Prevents the specified working channel from switching to the protection 458 line. 460 clearLockoutWorkingChannel(2) 462 Clears the lockout a working channel command for the channel specified. 463 " 464 SYNTAX INTEGER { 465 lockoutWorkingChannel(1), 466 clearLockoutWorkingChannel(2) 467 } 469 -- 470 -- APS Configuration Table 471 -- 472 -- This table supports the addition, configuration and deletion of APS 473 -- groups. 474 -- 476 apsConfig OBJECT IDENTIFIER ::= { rbnApsMIBObjects 1 } 478 apsConfigGroups OBJECT-TYPE 479 SYNTAX Counter32 480 MAX-ACCESS read-only 481 STATUS current 482 DESCRIPTION 483 "The count of APS groups." 484 ::= { apsConfig 1 } 486 apsConfigTable OBJECT-TYPE 487 SYNTAX SEQUENCE OF ApsConfigEntry 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "This table lists the APS groups that have been configured 492 on the system." 493 ::= { apsConfig 2 } 495 apsConfigEntry OBJECT-TYPE 496 SYNTAX ApsConfigEntry 497 MAX-ACCESS not-accessible 498 STATUS current 499 DESCRIPTION 500 "A conceptual row in the apsConfigTable." 501 INDEX { IMPLIED apsConfigName } 502 ::= { apsConfigTable 1 } 504 ApsConfigEntry ::= SEQUENCE { 505 apsConfigName SnmpAdminString, 506 apsConfigMode INTEGER, 507 apsConfigSdBerThreshold Integer32, 508 apsConfigSfBerThreshold Integer32, 509 apsConfigWaitToRestore Integer32, 510 apsConfigCreationTime TimeTicks, 511 apsConfigRowStatus RowStatus 513 } 515 apsConfigName OBJECT-TYPE 516 SYNTAX SnmpAdminString (SIZE (1..32)) 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "A textual name for the APS group. 521 " 522 ::= { apsConfigEntry 1 } 524 apsConfigMode OBJECT-TYPE 525 SYNTAX BITS { 526 onePlusOne(0), 527 oneToN(1), 528 revertive(2), 529 bidirectional(3), 530 extraTrafficAllowed(4) 531 } 532 MAX-ACCESS read-create 533 STATUS current 534 DESCRIPTION 535 "The architecture and mode of the APS group. The 536 values mean: 538 onePlusOne 540 The 1+1 architecture permanently bridges the working 541 line to the protection line. 543 oneToN 545 The 1:n architecture allows one protection channel to 546 protect up to n working channels. When a fault is detected 547 on one of the n working channels that channel is bridged 548 over the protection channel. 550 Note: onePlusOne and oneToN are mutually exclusive. 552 revertive 554 When the condition that caused a switch to the protection 555 line has been cleared the signal is switched back to the 556 working line. If this bit is clear it indicates a 557 non-revertive system which remains on the protection line 558 until another switch request is received. 560 bidirectional 562 The bi-directional mode provides protection in both 563 directions. 565 If this bit is clear it indicates unidirectional mode which 566 provides protection in one direction. The default for 1:n is 567 bidirectional. The default for 1+1 is unidirectional. 569 extraTrafficAllowed 571 Extra traffic may be carried on the protection channel in 572 a 1:n architecture if this flag is set. It may be necessary 573 to disable this in order to interwork with other SONET 574 network elements that don't support extra traffic. 576 This object may not be modified if the associated 577 apsConfigRowStatus object is equal to active(1)." 578 DEFVAL { '1'H } 579 ::= { apsConfigEntry 2 } 581 apsConfigSdBerThreshold OBJECT-TYPE 582 SYNTAX Integer32 (5..9) 583 MAX-ACCESS read-create 584 STATUS current 585 DESCRIPTION 586 "The Signal Degrade Bit Error Rate. 588 The negated value of this number is used as the exponent of 589 10 for computing the threshold value for the Bit Error Rate 590 (BER). For example, a value of 5 indicates a BER threshold of 591 10^-5. 593 This object may not be modified if the associated 594 apsConfigRowStatus object is equal to active(1)." 595 DEFVAL { 5 } 596 ::= { apsConfigEntry 3 } 598 apsConfigSfBerThreshold OBJECT-TYPE 599 SYNTAX Integer32 (3..5) 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "The Signal Failure Bit Error Rate. 605 The negated value of this number is used as the exponent of 606 10 for computing the threshold value for the Bit Error Rate 607 (BER). For example, a value of 5 indicates a BER threshold of 608 10^-5. 610 This object may not be modified if the associated 611 apsConfigRowStatus object is equal to active(1)." 612 DEFVAL { 3 } 613 ::= { apsConfigEntry 4 } 615 apsConfigWaitToRestore OBJECT-TYPE 616 SYNTAX Integer32 (300..720) 617 MAX-ACCESS read-create 618 STATUS current 619 DESCRIPTION 620 "The Wait To Restore period in seconds. 622 This field only applies if revertive switching is enabled, 623 otherwise this value is ignored. After clearing of a 624 condition that necessitated an automatic switch, the 625 wait to restore period must elapse before reverting. 626 This is intended to avoid rapid switch oscillations. 628 This object may not be modified if the associated 629 apsConfigRowStatus object is equal to active(1)." 630 DEFVAL { 10 } 631 ::= { apsConfigEntry 5 } 633 apsConfigCreationTime OBJECT-TYPE 634 SYNTAX TimeTicks 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "The value of sysUpTime at the time the associated 639 apsConfigRowStatus instance was set to active." 640 ::= { apsConfigEntry 6 } 642 apsConfigRowStatus OBJECT-TYPE 643 SYNTAX RowStatus 644 MAX-ACCESS read-create 645 STATUS current 646 DESCRIPTION 647 "The status of this APS group entry. 649 An entry may not exist in the active state unless all 650 objects in the entry have an appropriate value. Also, 651 all associated apsChanConfigEntry rows must represent 652 a set of consecutive channel numbers beginning with 653 zero. 655 If this object is set to destroy, all associated 656 apsChanConfigEntry, apsCommandEntry and apsChanStatusEntry 657 rows will be deleted. Also, The fields apsMapGroupName 658 and apsMapChanNumber in apsMapEntry rows corresponding 659 to the deleted channels will be set to a string of size 0 660 and -1 respectively. 662 This object may be set to notInService. When set to 663 notInService changes may be made to apsConfigMode, 664 apsConfigSdBerThreshold, apsCOnfigSfBerThreshold, 665 and apsConfigWaitToRestore. Also, rows may be 666 added and deleted from apsChanConfigTable. 667 " 668 ::= { apsConfigEntry 7 } 670 -- 671 -- APS Status Table 672 -- 673 -- This table provides APS group statistics. 674 -- 676 apsStatusTable OBJECT-TYPE 677 SYNTAX SEQUENCE OF ApsStatusEntry 678 MAX-ACCESS not-accessible 679 STATUS current 680 DESCRIPTION 681 "This table provides status information about APS groups that have 682 been configured on the system." 683 ::= { rbnApsMIBObjects 2 } 685 apsStatusEntry OBJECT-TYPE 686 SYNTAX ApsStatusEntry 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "A conceptual row in the apsStatusTable." 691 INDEX { IMPLIED apsConfigName} 692 ::= { apsStatusTable 1 } 694 ApsStatusEntry ::= SEQUENCE { 695 apsStatusK1K2Rcv ApsK1K2, 696 apsStatusK1K2Trans ApsK1K2, 697 apsStatusCurrent BITS, 698 apsStatusModeMismatches Counter32, 699 apsStatusChannelMismatches Counter32, 700 apsStatusPSBFs Counter32, 701 apsStatusFEPLFs Counter32 702 } 704 apsStatusK1K2Rcv OBJECT-TYPE 705 SYNTAX ApsK1K2 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "The current value of the K1 and K2 bytes received on the 710 protection channel." 711 ::= { apsStatusEntry 1 } 713 apsStatusK1K2Trans OBJECT-TYPE 714 SYNTAX ApsK1K2 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "The current value of the K1 and K2 bytes transmitted on the 719 protection channel." 720 ::= { apsStatusEntry 2 } 722 apsStatusCurrent OBJECT-TYPE 723 SYNTAX BITS { 724 modeMismatch(0), 725 channelMismatch(1), 726 psbf(2), 727 feplf(3), 728 extraTraffic(4) 729 } 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "The current status of the APS group. 735 modeMismatch 737 Modes other than 1+1 unidirectional monitor protection line 738 K2 bit 5, which indicates the architecture and K2 bits 739 6-8, which indicate if the mode is unidirectional or 740 bidirectional. A conflict between the current local mode 741 and the received K2 mode information constitutes a 742 mode mismatch. 744 channelMismatch 746 This bit indicates a mismatch between the transmitted K1 channel 747 and the received K2 channel has been detected. 749 psbf 751 This bit indicates a Protection Switch Byte Failure (PSBF) is 752 in effect. This condition occurs when an invalid code or 753 persistently unacceptable codes in the K1 byte are received. 755 feplf 757 Modes other than 1+1 unidirectional monitor the K1 byte 758 for Far-End Protection-Line failures. A Far-End 759 Protection-Line defect is declared based on receiving 760 SF on the protection line. 762 extraTraffic 764 This bit indicates whether extra traffic is currently being 765 accepted on the protection line. 766 " 767 ::= { apsStatusEntry 3 } 769 apsStatusModeMismatches OBJECT-TYPE 770 SYNTAX Counter32 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "A count of Mode Mismatch conditions." 775 ::= { apsStatusEntry 4 } 777 apsStatusChannelMismatches OBJECT-TYPE 778 SYNTAX Counter32 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "A count of Channel Mismatch conditions." 783 ::= { apsStatusEntry 5 } 785 apsStatusPSBFs OBJECT-TYPE 786 SYNTAX Counter32 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "A count of Protection Switch Byte Failure conditions. 791 This condition occurs when an invalid code or persistently 792 unacceptable codes in the K1 byte are received." 793 ::= { apsStatusEntry 6 } 795 apsStatusFEPLFs OBJECT-TYPE 796 SYNTAX Counter32 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "A count of Far-End Protection-Line Failure conditions. 801 This condition is declared based on receiving SF on 802 the protection line in the K1 byte." 803 ::= { apsStatusEntry 7 } 805 -- 806 -- APS Map Group 807 -- 808 -- Lists the SONET LTE interfaces that may be used to create APS groups. 809 -- 811 apsMap OBJECT IDENTIFIER ::= { rbnApsMIBObjects 3 } 813 apsChanLTEs OBJECT-TYPE 814 SYNTAX Counter32 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "The count of available SONET LTE interfaces that may be included 819 in APS groups." 820 ::= { apsMap 1 } 822 apsMapTable OBJECT-TYPE 823 SYNTAX SEQUENCE OF ApsMapEntry 824 MAX-ACCESS not-accessible 825 STATUS current 826 DESCRIPTION 827 "This table lists the SONET LTE interfaces that may be included in 828 APS groups. This is a list of all interfaces on the system with 829 ifType sonet(39)." 830 ::= { apsMap 2 } 832 apsMapEntry OBJECT-TYPE 833 SYNTAX ApsMapEntry 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "A conceptual row in the apsMapTable." 838 INDEX { apsMapIfIndex } 839 ::= { apsMapTable 1 } 841 ApsMapEntry ::= SEQUENCE { 842 apsMapIfIndex InterfaceIndex, 843 apsMapGroupName SnmpAdminString, 844 apsMapChanNumber Integer32 845 } 847 apsMapIfIndex OBJECT-TYPE 848 SYNTAX InterfaceIndex 849 MAX-ACCESS not-accessible 850 STATUS current 851 DESCRIPTION 852 "The Interface Index assigned to a SONET LTE. This is an interface 853 with ifType sonet(39)." 854 ::= { apsMapEntry 1 } 856 apsMapGroupName OBJECT-TYPE 857 SYNTAX SnmpAdminString (SIZE (1..32)) 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "A textual name for the APS group which this channel is 862 included in. 864 If the channel is not part of an APS group this value is set to 865 a string of size 0. 866 " 867 ::= { apsMapEntry 2 } 869 apsMapChanNumber OBJECT-TYPE 870 SYNTAX Integer32 (-1..14) 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "This field is set to a unique channel number within an APS group. 875 The value 0 indicates the null channel. The values 1-14 define a 876 working channel. 878 If the SONET LTE is not part of an APS group this value is set to -1. 879 " 880 ::= { apsMapEntry 3 } 882 -- 883 -- APS Channel Configuration Table 884 -- 885 -- This table supports the addition, configuration and deletion of channels 886 -- in APS groups. 887 -- 889 apsChanConfigTable OBJECT-TYPE 890 SYNTAX SEQUENCE OF ApsChanConfigEntry 891 MAX-ACCESS not-accessible 892 STATUS current 893 DESCRIPTION 894 "This table lists the APS channels that have been configured 895 in APS groups." 896 ::= { rbnApsMIBObjects 4 } 898 apsChanConfigEntry OBJECT-TYPE 899 SYNTAX ApsChanConfigEntry 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION 903 "A conceptual row in the apsChanConfigTable." 904 INDEX {apsChanGroupName, apsChanNumber} 905 ::= { apsChanConfigTable 1 } 907 ApsChanConfigEntry ::= SEQUENCE { 908 apsChanGroupName SnmpAdminString, 909 apsChanNumber Integer32, 910 apsChanIfIndex InterfaceIndex, 911 apsChanPriority INTEGER, 912 apsChanRowStatus RowStatus 913 } 915 apsChanGroupName OBJECT-TYPE 916 SYNTAX SnmpAdminString (SIZE (1..32)) 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION 920 "A textual name for the APS group which this channel is 921 included in." 922 ::= { apsChanConfigEntry 1 } 924 apsChanNumber OBJECT-TYPE 925 SYNTAX Integer32 (0..14) 926 MAX-ACCESS not-accessible 927 STATUS current 928 DESCRIPTION 929 "This field is set to a unique channel number within an APS group. 930 The value 0 indicates the null channel. The values 1-14 define a 931 working channel. 933 This field must be assigned a unique number within the group." 935 ::= { apsChanConfigEntry 2 } 937 apsChanIfIndex OBJECT-TYPE 938 SYNTAX InterfaceIndex 939 MAX-ACCESS read-create 940 STATUS current 941 DESCRIPTION 942 "The Interface Index assigned to a SONET LTE. This is an 943 interface with ifType sonet(39). This must not be set 944 to the InterfaceIndex of a SONET LTE that is currently 945 configured in an APS group. This cannot be set if 946 the group specified by apsChanGroupName is currently active. 947 " 949 ::= { apsChanConfigEntry 3 } 951 apsChanPriority OBJECT-TYPE 952 SYNTAX INTEGER {low(1), high(2)} 953 MAX-ACCESS read-create 954 STATUS current 955 DESCRIPTION 956 "The priority of the channel. 958 This field deterimines whether high or low priority 959 SD and SF codes are used in K1 requests. 961 This field is only applicable if the channel is to be included in 962 a group using the 1:n architecture. It is not applicable if the 963 channel is to be included in a group using the 1+1 architecture, 964 and is ignored in that case. 965 " 966 DEFVAL { 1 } 967 ::= { apsChanConfigEntry 4 } 969 apsChanRowStatus OBJECT-TYPE 970 SYNTAX RowStatus 971 MAX-ACCESS read-create 972 STATUS current 973 DESCRIPTION 974 "The status of this APS channel entry. 976 An entry may not exist in the active state unless all 977 objects in the entry have an appropriate value. 979 A row may not be created with an apsChanGroupName value 980 equal to an apsConfigName value if the associated 981 apsConfigRowStatus object is equal to active. However, 982 if the apsConfigRowStatus object is equal to notInService, 983 a row may be created. In other words, a channel may not 984 be added to an active group. 986 A row may be created with an apsChanGroupName value 987 that is not equal to any existing instance of apsConfigName. 988 This action is the initial step in adding a SONET LTE to a 989 new APS group. An instance of apsConfigName equal to this 990 instance of apsChanGroupName will subsequently be created. 992 If this object is set to destroy, the associated instance 993 of apsMapGroupName will be set to a string of size 0 and 994 the apsMapChanNumber will be set to -1 995 The channel command and channel status entries will also be 996 deleted by this action. 998 apsChanNumber must be set to a unique channel number within 999 the APS group. The value 0 indicates the null channel. 1000 The values 1-14 define a working channel. When an attempt is 1001 made to set the corresponding apsConfigRowStatus field to 1002 active the apsChanNumber values of all entries with equal 1003 apsChanGroupName fields must represent a set of consecutive 1004 integer values beginning with 0 and ending with n, where n is 1005 greater than or equal to 1 and less than or equal to 14. Otherwise 1006 the error inconsistentValue is returned to the apsConfigRowStatus 1007 set attempt. 1008 " 1009 ::= { apsChanConfigEntry 5 } 1011 -- 1012 -- APS Command Table 1013 -- 1014 -- This table provides the ability to initiate APS commands. 1015 -- 1017 apsCommandTable OBJECT-TYPE 1018 SYNTAX SEQUENCE OF ApsCommandEntry 1019 MAX-ACCESS not-accessible 1020 STATUS current 1021 DESCRIPTION 1022 "This table allows commands to be sent to configured APS groups." 1023 ::= { rbnApsMIBObjects 5 } 1025 apsCommandEntry OBJECT-TYPE 1026 SYNTAX ApsCommandEntry 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "A conceptual row in the apsCommandTable." 1031 INDEX {apsChanGroupName, apsChanNumber} 1032 ::= { apsCommandTable 1 } 1034 ApsCommandEntry ::= SEQUENCE { 1035 apsCommandSwitch Integer32, 1036 apsCommandControl Integer32 1037 } 1039 apsCommandSwitch OBJECT-TYPE 1040 SYNTAX ApsSwitchCommand 1041 MAX-ACCESS read-write 1042 STATUS current 1043 DESCRIPTION 1044 "Allows the initiation of an APS switch command on the 1045 APS group and channel specified by the index values. 1047 When read this object returns the last command written 1048 or clear(1) if no command has been written to this 1049 channel since initialization. The return of the last command 1050 written does not imply that this command is currently in effect. 1051 This request may have been preempted by a higer priority 1052 local or remote request. In order to determine the 1053 current state of the APS group it is necessary to read 1054 the objects apsStatusK1K2Rcv and apsStatusK1K2Trans. 1056 The value lockoutOfProtection(2) should only be applied 1057 to the protection line channel since that switch command 1058 prevents any of the working channels from switching to the protection 1059 line. Following the same logic, forcedSwitchProtectToWork(4) and 1060 manualSwitchProtectToWork(6) should only be applied to the protection 1061 line channel. 1063 forcedSwitchWorkToProtect(3) and manualSwitchWorkToProtect(5) 1064 should only be applied to a working channel. 1065 " 1066 ::= { apsCommandEntry 1 } 1068 apsCommandControl OBJECT-TYPE 1069 SYNTAX ApsControlCommand 1070 MAX-ACCESS read-write 1071 STATUS current 1072 DESCRIPTION 1073 "Allows the initiation of an APS control command on the 1074 APS group and channel specified by the index values. 1076 When read this object returns the last command written 1077 or clearLockoutWorkingChannel(2) if no command has been 1078 written to this channel since initialization. 1080 This command should not be applied to the protection 1081 line however, for simplicity the value clearLockoutWorkingChannel(2) 1082 can be returned if this object is queried with the protection line 1083 channel. 1084 " 1085 ::= { apsCommandEntry 2 } 1087 -- 1088 -- APS Channel Status Table 1089 -- 1090 -- This table provides APS channel statistics. 1091 -- 1093 apsChanStatusTable OBJECT-TYPE 1094 SYNTAX SEQUENCE OF ApsChanStatusEntry 1095 MAX-ACCESS not-accessible 1096 STATUS current 1097 DESCRIPTION 1098 "This table contains status information for all SONET LTE 1099 interfaces that are included in APS groups." 1100 ::= { rbnApsMIBObjects 6 } 1102 apsChanStatusEntry OBJECT-TYPE 1103 SYNTAX ApsChanStatusEntry 1104 MAX-ACCESS not-accessible 1105 STATUS current 1106 DESCRIPTION 1107 "A conceptual row in the apsChanStatusTable." 1108 INDEX {apsChanGroupName, apsChanNumber} 1109 ::= { apsChanStatusTable 1 } 1111 ApsChanStatusEntry ::= SEQUENCE { 1112 apsChanStatus BITS, 1113 apsChanSignalDegrades Counter32, 1114 apsChanSignalFailures Counter32, 1115 apsChanSwitchovers Counter32, 1116 apsChanLastSwitchover TimeTicks 1117 } 1119 apsChanStatus OBJECT-TYPE 1120 SYNTAX BITS { 1121 lockedOut(0), 1122 sd(1), 1123 sf(2), 1124 switched(3) 1125 } 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "Indicates the current state of the port. 1131 lockedOut 1133 This bit, when applied to a working channel, indicates that 1134 the channel is prevented from switching to the protection line. 1135 When applied to the null channel, this bit indicates that no 1136 working channel may switch to the protection line. 1138 sd 1140 A signal degrade condition is in effect. 1142 sf 1144 A signal failure condition is in effect. 1146 switched 1148 The switched bit is applied to a working channel if that 1149 channel is currently switched to the protection line. 1150 " 1151 ::= { apsChanStatusEntry 1 } 1153 apsChanSignalDegrades OBJECT-TYPE 1154 SYNTAX Counter32 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "A count of Signal Degrade conditions. This 1159 condition occurs when the line Bit Error Rate 1160 exceeds the currently configured threshold." 1161 ::= { apsChanStatusEntry 2 } 1163 apsChanSignalFailures OBJECT-TYPE 1164 SYNTAX Counter32 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "A count of Signal Failure conditions that have been 1169 detected on the incoming signal. This condition occurs 1170 when a loss of signal, loss of frame, AIS-L or a Line 1171 bit error rate exceeding 10^-3 is detected on an 1172 incoming line." 1173 ::= { apsChanStatusEntry 3 } 1175 apsChanSwitchovers OBJECT-TYPE 1176 SYNTAX Counter32 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "The number of times this channel has switched to the protection 1181 line. When queried with index value apsChanNumber set to 0, which 1182 is the protection line, this object will return 0. " 1183 ::= { apsChanStatusEntry 4 } 1185 apsChanLastSwitchover OBJECT-TYPE 1186 SYNTAX TimeTicks 1187 MAX-ACCESS read-only 1188 STATUS current 1189 DESCRIPTION 1190 "The value of sysUpTime when this channel last completed a switch 1191 to the protection line. If this channel has never switched to the 1192 protection line, or this channel is the protection line, the value 1193 0 will be returned." 1194 ::= { apsChanStatusEntry 5 } 1196 -- 1197 -- APS TRAPS 1198 -- 1200 apsTrapSwitchover NOTIFICATION-TYPE 1201 OBJECTS { apsChanSwitchovers, apsChanStatus } 1202 STATUS current 1203 DESCRIPTION 1204 "An apsTrapSwitchover notification is sent when the 1205 value of an instance of apsChanSwitchovers increments." 1206 ::= { rbnApsMIBNotifications 1 } 1208 apsTrapModeMismatch NOTIFICATION-TYPE 1209 OBJECTS { apsStatusModeMismatches, apsStatusCurrent } 1210 STATUS current 1211 DESCRIPTION 1212 "An apsTrapModeMismatch notification is sent when the 1213 value of an instance of apsStatusModeMismatches increments." 1214 ::= { rbnApsMIBNotifications 2 } 1216 apsTrapChannelMismatch NOTIFICATION-TYPE 1217 OBJECTS { apsStatusChannelMismatches, apsStatusCurrent } 1218 STATUS current 1219 DESCRIPTION 1220 "An apsTrapChannelMismatch notification is sent when the 1221 value of an instance of apsStatusChannelMismatches increments." 1222 ::= { rbnApsMIBNotifications 3 } 1224 apsTrapPSBF NOTIFICATION-TYPE 1225 OBJECTS { apsStatusPSBFs, apsStatusCurrent } 1226 STATUS current 1227 DESCRIPTION 1228 "An apsTrapPSBF notification is sent when the 1229 value of an instance of apsStatusPSBFs increments." 1230 ::= { rbnApsMIBNotifications 4 } 1232 apsTrapFEPLF NOTIFICATION-TYPE 1233 OBJECTS { apsStatusFEPLFs, apsStatusCurrent } 1234 STATUS current 1235 DESCRIPTION 1236 "An apsTrapFEPLFs notification is sent when the 1237 value of an instance of apsStatusFEPLFs increments." 1238 ::= { rbnApsMIBNotifications 5 } 1240 -- conformance information 1242 apsGroups OBJECT IDENTIFIER ::= { rbnApsMIBConformance 1 } 1243 apsCompliances OBJECT IDENTIFIER ::= { rbnApsMIBConformance 2 } 1245 apsCompliance MODULE-COMPLIANCE 1246 STATUS current 1247 DESCRIPTION 1248 "The compliance statement for linear APS groups." 1250 MODULE 1251 MANDATORY-GROUPS { apsConfigGeneral, apsStatusGeneral, apsChanGeneral } 1253 OBJECT apsConfigMode 1254 MIN-ACCESS read-only 1255 DESCRIPTION 1256 "Write access is not required." 1258 OBJECT apsConfigSdBerThreshold 1259 MIN-ACCESS read-only 1260 DESCRIPTION 1261 "Write access is not required." 1263 OBJECT apsConfigSfBerThreshold 1264 MIN-ACCESS read-only 1265 DESCRIPTION 1266 "Write access is not required." 1268 OBJECT apsConfigWaitToRestore 1269 MIN-ACCESS read-only 1270 DESCRIPTION 1271 "Write access is not required." 1273 OBJECT apsConfigRowStatus 1274 MIN-ACCESS read-only 1275 DESCRIPTION 1276 "Write access is not required." 1278 OBJECT apsChanIfIndex 1279 MIN-ACCESS read-only 1280 DESCRIPTION 1281 "Write access is not required." 1283 OBJECT apsChanPriority 1284 MIN-ACCESS read-only 1285 DESCRIPTION 1286 "Write access is not required." 1288 OBJECT apsChanRowStatus 1289 MIN-ACCESS read-only 1290 DESCRIPTION 1291 "Write access is not required." 1293 GROUP apsConfigOneToN 1294 DESCRIPTION 1295 "Implementation of this group is optional for all 1296 linear APS implementations. The information is 1297 applicable to groups implementing the linear 1298 APS 1:n architecture" 1300 GROUP apsCommandOnePlusOne 1301 DESCRIPTION 1302 "Implementation of this group is optional for all 1303 linear APS implementations. The information is 1304 applicable to groups implementing the linear 1305 APS 1+1 architecture and supporting set operations." 1307 GROUP apsCommandOneToN 1308 DESCRIPTION 1309 "Implementation of this group is optional for all 1310 linear APS implementations. The information is 1311 applicable to groups implementing the linear 1312 APS 1:n architecture and supporting set operations." 1314 GROUP apsChanOneToN 1315 DESCRIPTION 1316 "Implementation of this group is optional for all 1317 linear APS implementations. The information is 1318 applicable to groups implementing the linear 1319 APS 1:n architecture." 1321 GROUP apsTotalsGroup 1322 DESCRIPTION 1323 "Implementation of this group is optional for all 1324 linear APS implementations." 1326 GROUP apsMapGroup 1327 DESCRIPTION 1328 "Implementation of this group is optional for all 1329 linear APS implementations." 1331 ::= { apsCompliances 1 } 1333 -- units of conformance 1335 apsConfigGeneral OBJECT-GROUP 1336 OBJECTS 1337 { 1338 apsConfigMode, 1339 apsConfigSdBerThreshold, 1340 apsConfigSfBerThreshold, 1341 apsConfigCreationTime, 1342 apsConfigRowStatus 1343 } 1344 STATUS current 1345 DESCRIPTION 1346 "A collection of apsConfigTable objects providing configuration 1347 information applicable to all linear APS groups." 1348 ::= { apsGroups 1 } 1350 apsConfigOneToN OBJECT-GROUP 1351 OBJECTS 1352 { 1353 apsConfigWaitToRestore 1354 } 1355 STATUS current 1356 DESCRIPTION 1357 "The apsConfigTable object that provides information which is only 1358 applicable to groups implementing the linear APS 1:n architecture." 1359 ::= { apsGroups 2 } 1361 -- If set operations are not supported neither of the following two groups 1362 -- are implemented. If sets are supported only one of these groups is 1363 -- implemented for a linear APS group instance. 1365 apsCommandOnePlusOne OBJECT-GROUP 1366 OBJECTS 1367 { 1368 apsCommandSwitch 1369 } 1370 STATUS current 1371 DESCRIPTION 1372 "The apsCommandTable object which is applicable to groups 1373 implementing the linear APS 1+1 architecture. Also, set operations 1374 must be supported." 1375 ::= { apsGroups 3 } 1377 apsCommandOneToN OBJECT-GROUP 1378 OBJECTS 1379 { 1380 apsCommandSwitch, 1381 apsCommandControl 1382 } 1383 STATUS current 1384 DESCRIPTION 1385 "A collection of apsCommandTable objects which are applicable to 1386 groups implementing the linear APS 1:n architecture. Also, set 1387 operations must be supported." 1388 ::= { apsGroups 4 } 1390 apsStatusGeneral OBJECT-GROUP 1391 OBJECTS 1392 { 1393 apsStatusK1K2Rcv, 1394 apsStatusK1K2Trans, 1395 apsStatusCurrent, 1396 apsStatusModeMismatches, 1397 apsStatusChannelMismatches, 1398 apsStatusPSBFs, 1399 apsStatusFEPLFs 1401 } 1402 STATUS current 1403 DESCRIPTION 1404 "A collection of apsStatusTable objects providing status information 1405 applicable to all linear APS groups." 1406 ::= { apsGroups 5 } 1408 apsChanGeneral OBJECT-GROUP 1409 OBJECTS 1410 { 1411 apsChanIfIndex, 1412 apsChanRowStatus, 1413 apsChanStatus, 1414 apsChanSignalDegrades, 1415 apsChanSignalFailures, 1416 apsChanSwitchovers, 1417 apsChanLastSwitchover 1418 } 1419 STATUS current 1420 DESCRIPTION 1421 "A collection of channel objects providing information applicable to 1422 all linear APS channels." 1423 ::= { apsGroups 6 } 1425 apsChanOneToN OBJECT-GROUP 1426 OBJECTS 1427 { 1428 apsChanPriority 1429 } 1430 STATUS current 1431 DESCRIPTION 1432 "The apsChanConfigTable object that provides information which is only 1433 applicable to groups implementing the linear APS 1:n architecture." 1434 ::= { apsGroups 7 } 1436 apsTotalsGroup OBJECT-GROUP 1437 OBJECTS 1438 { 1439 apsConfigGroups, 1440 apsChanLTEs 1441 } 1442 STATUS current 1443 DESCRIPTION 1444 "A collection of objects providing optional counts of configured APS groups 1445 and SONET LTE interfaces." 1446 ::= { apsGroups 8 } 1448 apsMapGroup OBJECT-GROUP 1449 OBJECTS 1450 { 1451 apsMapGroupName, 1452 apsMapChanNumber 1453 } 1454 STATUS current 1455 DESCRIPTION 1456 "A collection of apsMapTable objects providing a mapping 1457 from sonet(39) InterfaceIndex to group name and channel 1458 number for assigned APS channels and a list of unassigned 1459 sonet(39) interfaces." 1460 ::= { apsGroups 9 } 1462 apsTrapOptional NOTIFICATION-GROUP 1463 NOTIFICATIONS {apsTrapSwitchover, apsTrapModeMismatch, 1464 apsTrapChannelMismatch, apsTrapPSBF, 1465 apsTrapFEPLF } 1466 STATUS current 1467 DESCRIPTION 1468 "A collection of SONET linear APS notifications that may optionally be 1469 implemented." 1470 ::= { apsGroups 10 } 1472 END 1474 6. Intellectual Property 1476 The IETF takes no position regarding the validity or scope of any 1477 intellectual property or other rights that might be claimed to 1478 pertain to the implementation or use of the technology described in 1479 this document or the extent to which any license under such rights 1480 might or might not be available; neither does it represent that it 1481 has made any effort to identify any such rights. Information on the 1482 IETF's procedures with respect to rights in standards-track and 1483 standards-related documentation can be found in BCP-11. Copies of 1484 claims of rights made available for publication and any assurances of 1485 licenses to be made available, or the result of an attempt made to 1486 obtain a general license or permission for the use of such 1487 proprietary rights by implementors or users of this specification can 1488 be obtained from the IETF Secretariat. 1490 7. APS Draft Progression Plan 1492 This document incorporates some aspects of Ken Chapman's 1493 draft-kchapman-sonet-aps-00.txt. However, this document takes 1494 a different approach in a number of areas, for example 1495 indexing of APS groups and arrangement of group and channel 1496 tables. It is the intent of this draft to serve as a starting 1497 point for discussion of the differences between the two documents, 1498 with the goal of subsequently producing a unified draft. 1500 8. References 1502 [1] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for 1503 Describing SNMP Management Frameworks, RFC 2571, Cabletron Systems, 1504 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 1506 [2] Rose, M., and K. McCloghrie, Structure and Identification of 1507 Management Information for TCP/IP-based Internets, RFC 1155, 1508 STD 16, Performance Systems International, Hughes LAN Systems, May 1990 1510 [3] Rose, M., and K. McCloghrie, Concise MIB Definitions, RFC 1212, 1511 STD 16, Performance Systems International, Hughes LAN Systems, March 1991 1513 [4] M. Rose, A Convention for Defining Traps for use with the SNMP, 1514 RFC 1215, Performance Systems International, March 1991 1516 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1517 M., and S. Waldbusser, Structure of Management Information Version 2 1518 (SMIv2), RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1519 Braunschweig, SNMP Research, First Virtual Holdings, International 1520 Network Services, April 1999 1522 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1523 M., and S. Waldbusser, Textual Conventions for SMIv2, RFC 2579, 1524 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1525 First Virtual Holdings, International Network Services, April 1999 1527 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1528 M., and S. Waldbusser, Conformance Statements for SMIv2, RFC 1529 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1530 First Virtual Holdings, International Network Services, April 1999 1532 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple Network 1533 Management Protocol, RFC 1157, STD 15, SNMP Research, Performance 1534 Systems International, Performance Systems International, MIT Laboratory 1535 for Computer Science, May 1990. 1537 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1538 Introduction to Community-based SNMPv2, RFC 1901, SNMP Research, 1539 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1540 Network Services, January 1996. 1542 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1543 Transport Mappings for Version 2 of the Simple 1544 Network Management Protocol (SNMPv2), RFC 1906, SNMP Research, Inc., 1545 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1546 Network Services, January 1996. 1548 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, Message 1549 Processing and Dispatching for the Simple Network Management Protocol 1550 (SNMP), RFC 2572, SNMP Research, Inc., Cabletron Systems, Inc., 1551 BMC Software, Inc., IBM T. J. Watson Research, April 1999 1553 [12] Blumenthal, U., and B. Wijnen, User-based Security Model (USM) 1554 for version 3 of the Simple Network Management Protocol (SNMPv3), 1555 RFC 2574, IBM T. J. Watson Research, April 1999 1557 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1558 Protocol Operations for Version 2 of the Simple 1559 Network Management Protocol (SNMPv2), RFC 1905, SNMP Research, Inc., 1560 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1561 Network Services, January 1996. 1563 [14] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, 1564 RFC 2573, SNMP Research, Inc., Secure Computing Corporation, 1565 Cisco Systems, April 1999 1567 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based Access 1568 Control Model (VACM) for the Simple Network Management Protocol 1569 (SNMP), RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1570 Cisco Systems, Inc., April 1999 1572 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, Introduction to 1573 Version 3 of the Internet-standard Network Management Framework, 1574 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., 1575 Ericsson, Cisco Systems, April 1999 1577 [17] McCloghrie, K., and F. Kastenholz. "The Interfaces Group MIB 1578 using SMIv2", RFC 2233, November 1997. 1580 [18] GR-253-CORE Issue 2, December 1995, Revision 2, January 1999 1582 [19] K. Chapman, "Definitions of Managed Objects for SONET Linear 1583 Automatic Protection Switching (APS)", 1584 draft-kchapman-sonet-aps-00.txt, July 1999 1586 9.Security Considerations 1588 There are a number of management objects defined in this MIB 1589 that have a MAX-ACCESS clause of read-write and/or read-create. 1590 Such objects may be considered sensitive or vulnerable in some 1591 network environments. The support for SET operations in a 1592 non-secure environment without proper protection can have a 1593 negative effect on network operations. 1595 SNMPv1 by itself is not a secure environment. Even if the 1596 network itself is secure (for example by using IPSec), even then, 1597 there is no control as to who on the secure network is allowed 1598 to access and GET/SET (read/change/create/delete) the objects in 1599 this MIB. 1601 It is recommended that the implementers consider the security 1602 features as provided by the SNMPv3 framework. Specifically, the 1603 use of the User-based Security Model RFC 2574 [RFC2574] and the 1604 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1606 It is then a customer/user responsibility to ensure that the SNMP 1607 entity giving access to an instance of this MIB, is properly 1608 configured to give access to the objects only to those 1609 principals (users) that have legitimate rights to indeed GET or 1610 SET (change/create/delete) them. 1612 10. Authors' Address 1614 Jeff Johnson 1615 RedBack Networks. Inc. 1616 1389 Moffett Park Drive 1617 Sunnyvale, CA 94089-1134 1618 Phone: +1 408 548 3516 1619 Email: jeff@redback.com 1621 Michael Thatcher 1622 RedBack Networks. Inc. 1623 1389 Moffett Park Drive 1624 Sunnyvale, CA 94089-1134 1625 Phone: +1 408 548 3946 1626 Email: thatcher@redback.com 1628 Jim Kuhfeld 1629 RedBack Networks. Inc. 1630 1389 Moffett Park Drive 1631 Sunnyvale, CA 94089-1134 1632 Phone: +1 408 548 2817 1633 Email: jkuhfeld@redback.com 1635 11. Full Copyright Statement 1637 Copyright (C) The Internet Society (1999). All Rights Reserved. 1639 This document and translations of it may be copied and furnished 1640 to others, and derivative works that comment on or otherwise 1641 explain it or assist in its implmentation may be prepared, copied, 1642 published and distributed, in whole or in part, without 1643 restriction of any kind, provided that the above copyright notice 1644 and this paragraph are included on all such copies and derivative 1645 works. However, this document itself may not be modified in any 1646 way, such as by removing the copyright notice or references to the 1647 Internet Society or other Internet organizations, except as needed 1648 for the purpose of developing Internet standards in which case the 1649 procedures for copyrights defined in the Internet Standards 1650 process must be followed, or as required to translate it into 1651 languages other than English. 1653 The limited permissions granted above are perpetual and will not 1654 be revoked by the Internet Society or its successors or assigns. 1656 This document and the information contained herein is provided on 1657 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1658 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1659 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1660 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1661 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 1662 PURPOSE."