idnits 2.17.1 draft-ietf-atommib-sonetaps-mib-01.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 38 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 98 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 307 has weird spacing: '...created in th...' == Line 678 has weird spacing: '...dicates unidi...' == Line 822 has weird spacing: '...tecture and K...' == Line 1053 has weird spacing: '...set the corre...' == Line 1459 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 (April 8, 2000) is 8783 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 1690 -- Looks like a reference, but probably isn't: 'RFC2575' on line 1691 == Unused Reference: '17' is defined on line 1662, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1665, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1669, 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' -- Possible downref: Non-RFC (?) normative reference: ref. '19' == Outdated reference: A later version (-01) exists of draft-kchapman-sonet-aps-00 -- Possible downref: Normative reference to a draft: ref. '20' Summary: 19 errors (**), 0 flaws (~~), 12 warnings (==), 7 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 October 8, 2000 M. Thatcher 3 J. Kuhfeld 4 Redback Networks 5 April 8, 2000 7 Definitions of Managed Objects 8 for SONET Linear APS architectures 10 draft-ietf-atommib-sonetaps-mib-01.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 April 8, 2000 62 The following changes were made for the version of this document 63 dated April 8, 2000. 65 The SYNTAX of apsMapGroupName was changed from SnmpAdminString (SIZE 66 (1..32)) to SnmpAdminString (SIZE (0..32)). 68 A statement regarding SDH support has been added (suggested by Kaj 69 Tesink). 71 The rbn prefix has been eliminated (suggested by Orly Nicklass). 73 The root of the mib has been changed to experimental XX (suggested by 74 Orly Nickalss). 76 RowStatus objects have been placed after the table index to allow for 77 growth of the tables (suggested by Orly Nicklass). 79 The architecture types onePlusOneCompatible and onePlusOneOptimized 80 were added to apsConfigMode (suggested by Orly Nicklass). 82 The value noCmd has been added to the ApsSwitchCommand and 83 ApsControlCommand TEXTUAL-CONVENTIONs. It is returned by a read 84 request when no command has been written to the object in question 85 since initialization (suggested by Orly Nicklass). 87 apsMIBNotifications was changed from apsMIB 0 to apsMIB2. 88 apsNotificationsPrefix was created as apsMIBNotifications 0 and the 89 individual notifications now fall under apsNotificationsPrefix 90 (suggested by Orly Nicklass). 92 The DEFVAL of apsConfigWaitToRestore was changed from 10 to 600 93 (suggested by Orly Nicklass). 95 ApsCommandEntry was corrected to use ApsSwitchCommand and 96 ApsControlCommand instead of Integer32 (suggested by Orly Nicklass). 98 December 7, 1999 100 The following changes were made for the version of this document 101 dated December 7, 1999. 103 The ApsK1K2 TEXTUAL-CONVENTION was changed from an Integer32 to OCTET 104 STRING (SIZE (2)) (borrowed from draft-kchapman-sonet-aps-mib-00.txt 105 [19]). 107 The command table is indexed by group and channel rather than group 108 only. In apsCommandEntry INDEX specification, IMPLIED was removed 109 from apsConfigName and apsChanNumber was added. This allows the use 110 of simple command enumeration rather than "cryptic" Integer32 values 111 combining channel and command (a variation on command handling in 112 draft-kchapman-sonet-aps-mib-00.txt [19]). 114 A number of DESCRIPTION fields have been expanded. 116 Far-End Protection Line Failure conditions are now monitored. The bit 117 feplf was added to apsStatusCurrent, the Counter32 apsStatusFEPLFs 118 was added to ApsStatusEntry, and the the NOTIFICATION-TYPE 119 apsTrapFEPLF was created (borrowed from draft-kchapman-sonet-aps- 120 mib-00.txt [19]). 122 The apsChanIfIndex DESCRIPTION indicates that it is an interface with 123 ifType sonet(39) (feedback from Kaj Tesink). 125 DisplayString objects apsConfigName and apsChanGroupName were changed 126 to SnmpAdminString (feedback from Kaj Tesink). 128 apsChanGroupName SYNTAX was changed to SnmpAdminString (SIZE (1..32)) 129 in order to be consistent with apsConfigName. 131 Channel configuration is enacted by creating rows in 132 apsChanConfigTable which is indexed by group name and channel number. 133 (a variation on channel creation in draft-kchapman-sonet-aps- 134 mib-00.txt [19]). 136 apsStatusCreationTime was renamed apsConfigCreationTime and moved 137 from apsStatusTable to apsConfigTable, since it is associated with 138 row creation in that table. 140 June 28, 1999 142 The following changes were made for the version of this document 143 dated June 28, 1999. 145 References to Protection Switch Byte Failure (PSBF) conditions were 146 moved from the channel table to the group status table. Specifically, 147 the psbf failure bit was moved from apsChanStatus to 148 apsStatusCurrent, apsChanPSBFs was deleted and replaced with 149 apsStatusPSBFs and the NOTIFICATION-TYPE apsTrapPSBF was created. 150 (feedback from Ken Chapman) 152 2. The SNMP Management Framework 154 The SNMP Management Framework presently consists of five major 155 components: 157 An overall architecture, described in RFC 2571 [1]. 159 Mechanisms for describing and naming objects and events for the 160 purpose of management. The first version of this Structure of 161 Management Information (SMI) is called SMIv1 and described in RFC 162 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 163 SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 165 Message protocols for transferring management information. The first 166 version of the SNMP message protocol is called SNMPv1 and described 167 in RFC 1157 [8]. A second version of the SNMP message protocol, which 168 is not an Internet standards track protocol, is called SNMPv2c and 169 described in RFC 1901 [9] and RFC 1906 [10]. The third version of the 170 message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 171 2572 [11] and RFC 2574 [12]. 173 Protocol operations for accessing management information. The first 174 set of protocol operations and associated PDU formats is described in 175 RFC 1157 [8]. A second set of protocol operations and associated PDU 176 formats is described in RFC 1905 [13]. 178 A set of fundamental applications described in RFC 2573 [14] and the 179 view-based access control mechanism described in RFC 2575 [15]. 181 A more detailed introduction to the current SNMP Management Framework 182 can be found in RFC 2570 [16]. 184 Managed objects are accessed via a virtual information store, termed 185 the Management Information Base or MIB. Objects in the MIB are 186 defined using the mechanisms defined in the SMI. 188 This memo specifies a MIB module that is compliant to the SMIv2. A 189 MIB conforming to the SMIv1 can be produced through the appropriate 190 translations. The resulting translated MIB must be semantically 191 equivalent, except where objects or events are omitted because no 192 translation is possible (use of Counter64). Some machine readable 193 information in SMIv2 will be converted into textual descriptions in 194 SMIv1 during the translation process. However, this loss of machine 195 readable information is not considered to change the semantics of the 196 MIB. 198 3. Object Definitions 200 Managed objects are accessed via a virtual information store, termed 201 the Management Information Base or MIB. Objects in the MIB are 202 defined using the subset of Abstract Syntax Notation One (ASN.1) 203 defined in the SMI. In particular, each object type is named by an 204 OBJECT IDENTIFIER, an administratively assigned name. The object 205 type together with an object instance serves to uniquely identify a 206 specific instantiation of the object. For human convenience, we 207 often use a textual string, termed the descriptor, to refer to the 208 object type. 210 4. Overview 212 These objects are used to control and manage SONET linear APS 213 architectures. 215 The mib contains two scalars, containing counts of APS groups and 216 SONET LTEs respectively and six tables: apsMapTable, 217 apsChanConfigTable, apsConfigTable, apsCommandTable, 218 apsChanStatusTable and apsStatusTable. The apsMapTable provides a 219 list of SONET LTE interfaces available on the system. The 220 apsChanConfigTable supports addition, modification and deletion of 221 entries representing linear APS channels. The apsConfigTable 222 supports addition, modification and deletion of entries representing 223 linear APS groups. The apsCommandTable provides linear APS commands 224 that support protection switching and the ability to modify APS 225 operation. The apsChanStatusTable provides individual channel 226 statistics. The apsStatusTable provides group level statistics. 228 5. Definitions 229 APS-MIB DEFINITIONS ::= BEGIN 231 IMPORTS 232 MODULE-IDENTITY, TimeTicks, 233 OBJECT-IDENTITY, experimental 234 FROM SNMPv2-SMI; 236 apsMIB MODULE-IDENTITY 237 LAST-UPDATED "200004082300Z" 238 ORGANIZATION "IETF AToMMIB Working Group" 239 CONTACT-INFO 240 " Jeff Johnson 241 Postal: RedBack Networks. Inc. 242 350 Holger Way 243 San Jose, CA 95134-1362 244 Tel: +1 408 571 5460 245 Email: jeff@redback.com 247 Michael Thatcher 248 Postal: RedBack Networks. Inc. 249 350 Holger Way 250 San Jose, CA 95134-1362 251 Tel: +1 408 571 5449 252 Email: thatcher@redback.com 254 Jim Kuhfeld 255 Postal: RedBack Networks. Inc. 256 350 Holger Way 257 San Jose, CA 95134-1362 258 Tel: +1 408 571 5465 259 Email: jkuhfeld@redback.com" 260 DESCRIPTION 261 "This management information module supports the configuration and 262 management of SONET linear APS groups. The definitions and 263 descriptions used in this mib have been derived from 264 Synchronous Optical Network (SONET) Transport Systems: 265 Common Generic Criteria, GR-253-CORE Revision 2, January 1999, 266 section 5.3. The MIB is also consistent with the Multiplex 267 Section Protection (MSP) protocol as specified in ITU-T 268 Recommendation G.783, Characteristics of synchronous digital 269 hierarchy (SDH) equipment function blocks, Annex A and B. 271 Ring APS groups are not currently supported by this mib. 273 The mib contains six tables. 275 The apsMapTable contains entries for each SONET LTE 276 interface available on the system. The table serves two 277 purposes. It can be used to locate SONET LTE 278 interfaces that are not currently included in 279 APS groups. It also provides a mapping from InterfaceIndex 280 to group name and channel number for those SONET LTE 281 interfaces that are included in APS groups. 282 Entries in apsMapTable cannot be added or deleted 283 through operations defined in this mib. However, an 284 apsMapEntry may be added or deleted through other system 285 mechanisms, such as hot swap. 287 The apsChanConfigTable supports addition, modification and 288 deletion of entries representing linear APS channels. 289 Entries are indexed by a text group name and integer channel 290 number. Each entry contains an InterfaceIndex value identifying 291 the SONET LTE used for the channel and the priority of the 292 channel. A side effect of row creation or deletion is 293 creation or deletion of corresponding command and 294 channel status entries, and the setting of map entry 295 fields. Creation of 2-14 entries in this table with a 296 common group name index and consecutive channel numbers 297 beginning with zero is the first step in the creation 298 and configuration of an APS group. It is not necessary 299 to create channel numbers in order, however the resulting 300 set of channels must begin with channel number 0 and 301 must be consecutive. 303 The apsConfigTable supports addition, modification and deletion of 304 entries representing linear APS groups. Entries are indexed by a 305 text group name. Each entry contains parameters that specify the 306 configuration of a particular linear APS group. Entries are 307 created in this table after a set of channels are created 308 in the apsChanConfigTable. In order to successfully set an 309 instance of apsConfigRowStatus to active the apsConfigEntry 310 must contain valid values and all associated apsChanConfigEntry 311 rows must be valid and produce a consecutive set of channels 312 beginning with channel number 0. 314 The apsCommandTable provides linear APS commands that support 315 protection switching and the ability to modify APS operation. 316 Commands may only be entered if the corresponding 317 apsConfigRowStatus instance is set to active. Entries in this 318 table are created as a side effect of row addition in the 319 apsChanConfigTable. 321 The apsChanStatusTable provides individual channel statistics. 322 Entries in this table are created as a side effect of row 323 addition in the apsChanConfigTable. 325 The apsStatusTable provides group level statistics. Entries in 326 this table are created as a side effect of row addition in 327 apsConfigTable. 329 An APS group is created and configured with the following sequence 330 of events: 332 CHANNEL CONFIGURATION 334 Create an entry in the apsChanConfigTable 335 Set the apsChanGroupName in an apsChanConfigEntry to a 336 user-friendly text string which will serve as the 337 APS group name. The string must not be equal to 338 the apsConfigName of an existing apsConfigEntry with 339 apsConfigRowStatus set to active, since a channel cannot be 340 added to an active group. The string may be set equal 341 to the apsConfigName of a row which is currently not 342 set to active, or it may be set to a string which does 343 not currently exist in any instance of apsConfigName. 344 A channel number is entered in apsChanNumber. 345 A channel priority is entered in apsChanPriority, if 346 the intended architecture is 1:n. apsChanPriority is 347 ignored if the architecture is 1+1. The InterfaceIndex 348 value of a SONET LTE interface is entered in apsChanIfIndex. 350 This step is repeated for all apsChanConfigEntry instances 351 which are to be included in the APS group. 353 ACTIVATING THE GROUP 355 If the apsChanGroupName does not exist in an instance 356 of apsConfigName, an apsConfigEntry is created with 357 the apsChanGroupName value used as the index for the row. 358 The apsConfigRowStatus value may be set to createAndGo. 359 The apsGroupConfigEntry and apsChanConfigEntry instances with 360 matching name fields will be checked for consistency. 361 If any errors in the channel numbers, architecture or 362 configuration are uncovered the apsConfigRowStatus set 363 will return inconsistentValue, otherwise noError is returned. 365 If the apsChanGroupName value used in channel configuration 366 exists in a previously created, inactive apsConfigEntry instance, 367 the apsConfigRowStatus value may be set to active. 368 " 370 REVISION "200004082300Z" 371 DESCRIPTION 372 "A draft version of the linear APS MIB." 373 ::= { experimental XX } 374 -- assign XX 375 -- remove this notice from the MIB 377 apsMIBObjects OBJECT IDENTIFIER 378 ::= { apsMIB 1 } 380 apsMIBNotifications OBJECT IDENTIFIER 381 ::= { apsMIB 2 } 383 apsMIBConformance OBJECT IDENTIFIER 384 ::= { apsMIB 3 } 386 ApsK1K2 ::= TEXTUAL-CONVENTION 387 STATUS current 388 DESCRIPTION 389 "This Textual Convention describes an object that stores 390 a SONET K1 and K2 byte APS protocol field. 392 K1 is located in the first octet, K2 is located in 393 the second octet. 395 Bits 1-4 of the K1 byte indicate a request. 397 1111 Lockout of Protection 398 1110 Forced Switch 399 1101 SF - High Priority 400 1100 SF - Low Priority 401 1011 SD - High Priority 402 1010 SD - Low Priority 403 1001 not used 404 1000 Manual Switch 405 0111 not used 406 0110 Wait-to-Restore 407 0101 not used 408 0100 Exercise 409 0011 not used 410 0010 Reverse Request 411 0001 Do Not Revert 412 0000 No Request 414 Bits 5-8 of the K1 byte indicate the channel associated with the 415 request defined in bits 1-4. 417 0000 is the Null channel 419 1-14 are working channels. 420 15 is the extra traffic channel 422 Bits 1-4 of the K2 byte indicate a channel. The channel is 423 defined with the same syntax as K1 Bits 5-8. 425 Bit 5 of the K2 byte indicates the 426 architecture. 428 0 if the architecture is 1+1 429 1 if the architecture is 1:n 431 Bits 6-8 of the K2 byte indicates the 432 mode. 434 000 - 011 are reserved for future use 436 100 indicates the mode is unidirectional 437 101 indicates the mode is bidirectional 439 110 RDI-L 441 111 AIS-L 442 " 443 REFERENCE 444 "Bellcore (Telcordia Technologies) GR-253-CORE, Issue 2, 445 Revision 2 (January 1999), 5.3.5." 446 SYNTAX OCTET STRING (SIZE (2)) 448 ApsSwitchCommand ::= TEXTUAL-CONVENTION 449 STATUS current 450 DESCRIPTION 451 "An APS switch command allows a user to perform protection 452 switch actions. 454 The Switch command values are: 456 noCmd(1) 458 This value should be returned by a read request when no switch 459 command has been written to the object in question since 460 initialization. This value may not be used in a write operation. 462 clear(2) 463 Clears all of the switch commands listed below for the specified 464 channel. 466 lockoutOfProtection(3) 468 Prevents any of the working channels from switching to the protection 469 line. 471 forcedSwitchWorkToProtect(4) 473 Switches the specified working channel to the protection line. 475 forcedSwitchProtectToWork(5) 477 Switches the working channel back from the protection line to 478 the working line. 480 manualSwitchWorkToProtect(6) 482 Switches the specified working channel to the protection line. 484 manualSwitchProtectToWork(7) 486 Switches the working channel back from the protection line to 487 the working line. 489 exercise(8) 491 Exercises the protocol for a protection switch of the specified 492 channel by issuing an Exercise request for that channel and 493 checking the response on the APS channel. 494 " 495 SYNTAX INTEGER { 496 noCmd(1), 497 clear(2), 498 lockoutOfProtection(3), 499 forcedSwitchWorkToProtect(4), 500 forcedSwitchProtectToWork(5), 501 manualSwitchWorkToProtect(6), 502 manualSwitchProtectToWork(7), 503 exercise(8) 504 } 506 ApsControlCommand ::= TEXTUAL-CONVENTION 507 STATUS current 508 DESCRIPTION 509 "An APS control command applies only to LTE that support the 510 1:n architecture and performs the following actions. 512 The Control command values are: 514 noCmd(1) 516 This value should be returned by a read request when no control 517 command has been written to the object in question since 518 initialization. This value may not be used in a write operation. 520 lockoutWorkingChannel(2) 522 Prevents the specified working channel from switching to the protection 523 line. 525 clearLockoutWorkingChannel(3) 527 Clears the lockout a working channel command for the channel specified. 528 " 529 SYNTAX INTEGER { 530 noCmd(1), 531 lockoutWorkingChannel(2), 532 clearLockoutWorkingChannel(3) 533 } 535 -- 536 -- APS Configuration Table 537 -- 538 -- This table supports the addition, configuration and deletion of APS 539 -- groups. 540 -- 542 apsConfig OBJECT IDENTIFIER ::= { apsMIBObjects 1 } 544 apsConfigGroups OBJECT-TYPE 545 SYNTAX Counter32 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "The count of APS groups." 550 ::= { apsConfig 1 } 552 apsConfigTable OBJECT-TYPE 553 SYNTAX SEQUENCE OF ApsConfigEntry 554 MAX-ACCESS not-accessible 555 STATUS current 556 DESCRIPTION 557 "This table lists the APS groups that have been configured 558 on the system." 559 ::= { apsConfig 2 } 561 apsConfigEntry OBJECT-TYPE 562 SYNTAX ApsConfigEntry 563 MAX-ACCESS not-accessible 564 STATUS current 565 DESCRIPTION 566 "A conceptual row in the apsConfigTable." 567 INDEX { IMPLIED apsConfigName } 568 ::= { apsConfigTable 1 } 570 ApsConfigEntry ::= SEQUENCE { 571 apsConfigName SnmpAdminString, 572 apsConfigRowStatus RowStatus, 573 apsConfigMode INTEGER, 574 apsConfigSdBerThreshold Integer32, 575 apsConfigSfBerThreshold Integer32, 576 apsConfigWaitToRestore Integer32, 577 apsConfigCreationTime TimeTicks 578 } 580 apsConfigName OBJECT-TYPE 581 SYNTAX SnmpAdminString (SIZE (1..32)) 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "A textual name for the APS group. 586 " 587 ::= { apsConfigEntry 1 } 589 apsConfigRowStatus OBJECT-TYPE 590 SYNTAX RowStatus 591 MAX-ACCESS read-create 592 STATUS current 593 DESCRIPTION 594 "The status of this APS group entry. 596 An entry may not exist in the active state unless all 597 objects in the entry have an appropriate value. Also, 598 all associated apsChanConfigEntry rows must represent 599 a set of consecutive channel numbers beginning with 600 zero. 602 If this object is set to destroy, all associated 603 apsChanConfigEntry, apsCommandEntry and apsChanStatusEntry 604 rows will be deleted. Also, The fields apsMapGroupName 605 and apsMapChanNumber in apsMapEntry rows corresponding 606 to the deleted channels will be set to a string of size 0 607 and -1 respectively. 609 This object may be set to notInService. When set to 610 notInService changes may be made to apsConfigMode, 611 apsConfigSdBerThreshold, apsCOnfigSfBerThreshold, 612 and apsConfigWaitToRestore. Also, rows may be 613 added and deleted from apsChanConfigTable. 614 " 615 ::= { apsConfigEntry 2 } 617 apsConfigMode OBJECT-TYPE 618 SYNTAX BITS { 619 onePlusOne(0), 620 oneToN(1), 621 onePlusOneCompatible(2), 622 onePlusOneOptimized(3), 623 revertive(4), 624 bidirectional(5), 625 extraTrafficAllowed(6) 626 } 627 MAX-ACCESS read-create 628 STATUS current 629 DESCRIPTION 630 "The architecture and mode of the APS group. The 631 values mean: 633 onePlusOne 635 The 1+1 architecture permanently bridges the working 636 line to the protection line. 638 oneToN 640 The 1:n architecture allows one protection channel to 641 protect up to n working channels. When a fault is detected 642 on one of the n working channels that channel is bridged 643 over the protection channel. 645 onePlusOneCompatible 647 This refers to 1 + 1 bidirectional switching compatible with 648 1:n bidirectional switching as specified in ITU-T 649 Recommendation G.783 (04/97) section A.3.4.1. Since this 650 mode necessitates bidirectional switching the bidirectional 651 bit must also be set whenever onePlusOneCompatible is set. 653 onePlusOneOptimized 655 This refers to 1 + 1 bidirectional switching optimized 656 for a network using predominantly 1 + 1 bidirectional 657 switching as specified in ITU-T Recommendation G.783 (04/97) 658 section B.1. Since this mode necessitates bidirectional 659 switching, the bidirectional bit must also be set whenever 660 onePlusOneOptimized is set. 662 Note: onePlusOne, oneToOne, onePlusOneCompatible and 663 onePlusOneOptimized are mutually exclusive. 665 revertive 667 When the condition that caused a switch to the protection 668 line has been cleared the signal is switched back to the 669 working line. If this bit is clear it indicates a 670 non-revertive system which remains on the protection line 671 until another switch request is received. 673 bidirectional 675 The bi-directional mode provides protection in both 676 directions. 678 If this bit is clear it indicates unidirectional mode which 679 provides protection in one direction. The default for 1:n is 680 bidirectional. The default for 1+1 is unidirectional. 682 extraTrafficAllowed 684 Extra traffic may be carried on the protection channel in 685 a 1:n architecture if this flag is set. It may be necessary 686 to disable this in order to interwork with other SONET 687 network elements that don't support extra traffic. 689 This object may not be modified if the associated 690 apsConfigRowStatus object is equal to active(1)." 691 DEFVAL { '1'H } 692 ::= { apsConfigEntry 3 } 694 apsConfigSdBerThreshold OBJECT-TYPE 695 SYNTAX Integer32 (5..9) 696 MAX-ACCESS read-create 697 STATUS current 698 DESCRIPTION 699 "The Signal Degrade Bit Error Rate. 701 The negated value of this number is used as the exponent of 702 10 for computing the threshold value for the Bit Error Rate 703 (BER). For example, a value of 5 indicates a BER threshold of 704 10^-5. 706 This object may not be modified if the associated 707 apsConfigRowStatus object is equal to active(1)." 708 DEFVAL { 5 } 709 ::= { apsConfigEntry 4 } 711 apsConfigSfBerThreshold OBJECT-TYPE 712 SYNTAX Integer32 (3..5) 713 MAX-ACCESS read-create 714 STATUS current 715 DESCRIPTION 716 "The Signal Failure Bit Error Rate. 718 The negated value of this number is used as the exponent of 719 10 for computing the threshold value for the Bit Error Rate 720 (BER). For example, a value of 5 indicates a BER threshold of 721 10^-5. 723 This object may not be modified if the associated 724 apsConfigRowStatus object is equal to active(1)." 725 DEFVAL { 3 } 726 ::= { apsConfigEntry 5 } 728 apsConfigWaitToRestore OBJECT-TYPE 729 SYNTAX Integer32 (300..720) 730 MAX-ACCESS read-create 731 STATUS current 732 DESCRIPTION 733 "The Wait To Restore period in seconds. 735 This field only applies if revertive switching is enabled, 736 otherwise this value is ignored. After clearing of a 737 condition that necessitated an automatic switch, the 738 wait to restore period must elapse before reverting. 739 This is intended to avoid rapid switch oscillations. 741 This object may not be modified if the associated 742 apsConfigRowStatus object is equal to active(1)." 743 DEFVAL { 600 } 744 ::= { apsConfigEntry 6 } 746 apsConfigCreationTime OBJECT-TYPE 747 SYNTAX TimeTicks 748 MAX-ACCESS read-only 749 STATUS current 750 DESCRIPTION 751 "The value of sysUpTime at the time the associated 752 apsConfigRowStatus instance was set to active." 753 ::= { apsConfigEntry 7 } 755 -- 756 -- APS Status Table 757 -- 758 -- This table provides APS group statistics. 759 -- 761 apsStatusTable OBJECT-TYPE 762 SYNTAX SEQUENCE OF ApsStatusEntry 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "This table provides status information about APS groups that have 767 been configured on the system." 768 ::= { apsMIBObjects 2 } 770 apsStatusEntry OBJECT-TYPE 771 SYNTAX ApsStatusEntry 772 MAX-ACCESS not-accessible 773 STATUS current 774 DESCRIPTION 775 "A conceptual row in the apsStatusTable." 776 INDEX { IMPLIED apsConfigName} 777 ::= { apsStatusTable 1 } 779 ApsStatusEntry ::= SEQUENCE { 780 apsStatusK1K2Rcv ApsK1K2, 781 apsStatusK1K2Trans ApsK1K2, 782 apsStatusCurrent BITS, 783 apsStatusModeMismatches Counter32, 784 apsStatusChannelMismatches Counter32, 785 apsStatusPSBFs Counter32, 786 apsStatusFEPLFs Counter32 787 } 788 apsStatusK1K2Rcv OBJECT-TYPE 789 SYNTAX ApsK1K2 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "The current value of the K1 and K2 bytes received on the 794 protection channel." 795 ::= { apsStatusEntry 1 } 797 apsStatusK1K2Trans OBJECT-TYPE 798 SYNTAX ApsK1K2 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "The current value of the K1 and K2 bytes transmitted on the 803 protection channel." 804 ::= { apsStatusEntry 2 } 806 apsStatusCurrent OBJECT-TYPE 807 SYNTAX BITS { 808 modeMismatch(0), 809 channelMismatch(1), 810 psbf(2), 811 feplf(3), 812 extraTraffic(4) 813 } 814 MAX-ACCESS read-only 815 STATUS current 816 DESCRIPTION 817 "The current status of the APS group. 819 modeMismatch 821 Modes other than 1+1 unidirectional monitor protection line 822 K2 bit 5, which indicates the architecture and K2 bits 823 6-8, which indicate if the mode is unidirectional or 824 bidirectional. A conflict between the current local mode 825 and the received K2 mode information constitutes a 826 mode mismatch. 828 channelMismatch 830 This bit indicates a mismatch between the transmitted K1 channel 831 and the received K2 channel has been detected. 833 psbf 835 This bit indicates a Protection Switch Byte Failure (PSBF) is 836 in effect. This condition occurs when an invalid code or 837 persistently unacceptable codes in the K1 byte are received. 839 feplf 841 Modes other than 1+1 unidirectional monitor the K1 byte 842 for Far-End Protection-Line failures. A Far-End 843 Protection-Line defect is declared based on receiving 844 SF on the protection line. 846 extraTraffic 848 This bit indicates whether extra traffic is currently being 849 accepted on the protection line. 850 " 851 ::= { apsStatusEntry 3 } 853 apsStatusModeMismatches OBJECT-TYPE 854 SYNTAX Counter32 855 MAX-ACCESS read-only 856 STATUS current 857 DESCRIPTION 858 "A count of Mode Mismatch conditions." 859 ::= { apsStatusEntry 4 } 861 apsStatusChannelMismatches OBJECT-TYPE 862 SYNTAX Counter32 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "A count of Channel Mismatch conditions." 867 ::= { apsStatusEntry 5 } 869 apsStatusPSBFs OBJECT-TYPE 870 SYNTAX Counter32 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "A count of Protection Switch Byte Failure conditions. 875 This condition occurs when an invalid code or persistently 876 unacceptable codes in the K1 byte are received." 877 ::= { apsStatusEntry 6 } 879 apsStatusFEPLFs OBJECT-TYPE 880 SYNTAX Counter32 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "A count of Far-End Protection-Line Failure conditions. 885 This condition is declared based on receiving SF on 886 the protection line in the K1 byte." 887 ::= { apsStatusEntry 7 } 889 -- 890 -- APS Map Group 891 -- 892 -- Lists the SONET LTE interfaces that may be used to create APS groups. 893 -- 895 apsMap OBJECT IDENTIFIER ::= { apsMIBObjects 3 } 897 apsChanLTEs OBJECT-TYPE 898 SYNTAX Counter32 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "The count of available SONET LTE interfaces that may be included 903 in APS groups." 904 ::= { apsMap 1 } 906 apsMapTable OBJECT-TYPE 907 SYNTAX SEQUENCE OF ApsMapEntry 908 MAX-ACCESS not-accessible 909 STATUS current 910 DESCRIPTION 911 "This table lists the SONET LTE interfaces that may be included in 912 APS groups. This is a list of all interfaces on the system with 913 ifType sonet(39)." 914 ::= { apsMap 2 } 916 apsMapEntry OBJECT-TYPE 917 SYNTAX ApsMapEntry 918 MAX-ACCESS not-accessible 919 STATUS current 920 DESCRIPTION 921 "A conceptual row in the apsMapTable." 922 INDEX { apsMapIfIndex } 923 ::= { apsMapTable 1 } 925 ApsMapEntry ::= SEQUENCE { 926 apsMapIfIndex InterfaceIndex, 927 apsMapGroupName SnmpAdminString, 928 apsMapChanNumber Integer32 929 } 931 apsMapIfIndex OBJECT-TYPE 932 SYNTAX InterfaceIndex 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "The Interface Index assigned to a SONET LTE. This is an interface 937 with ifType sonet(39)." 938 ::= { apsMapEntry 1 } 940 apsMapGroupName OBJECT-TYPE 941 SYNTAX SnmpAdminString (SIZE (0..32)) 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 "A textual name for the APS group which this channel is 946 included in. 948 If the channel is not part of an APS group this value is set to 949 a string of size 0. 950 " 951 ::= { apsMapEntry 2 } 953 apsMapChanNumber OBJECT-TYPE 954 SYNTAX Integer32 (-1..14) 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "This field is set to a unique channel number within an APS group. 959 The value 0 indicates the null channel. The values 1-14 define a 960 working channel. 962 If the SONET LTE is not part of an APS group this value is set to -1. 963 " 964 ::= { apsMapEntry 3 } 966 -- 967 -- APS Channel Configuration Table 968 -- 969 -- This table supports the addition, configuration and deletion of channels 970 -- in APS groups. 971 -- 973 apsChanConfigTable OBJECT-TYPE 974 SYNTAX SEQUENCE OF ApsChanConfigEntry 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "This table lists the APS channels that have been configured 979 in APS groups." 980 ::= { apsMIBObjects 4 } 982 apsChanConfigEntry OBJECT-TYPE 983 SYNTAX ApsChanConfigEntry 984 MAX-ACCESS not-accessible 985 STATUS current 986 DESCRIPTION 987 "A conceptual row in the apsChanConfigTable." 988 INDEX {apsChanGroupName, apsChanNumber} 989 ::= { apsChanConfigTable 1 } 991 ApsChanConfigEntry ::= SEQUENCE { 992 apsChanGroupName SnmpAdminString, 993 apsChanNumber Integer32, 994 apsChanRowStatus RowStatus, 995 apsChanIfIndex InterfaceIndex, 996 apsChanPriority INTEGER 997 } 999 apsChanGroupName OBJECT-TYPE 1000 SYNTAX SnmpAdminString (SIZE (1..32)) 1001 MAX-ACCESS not-accessible 1002 STATUS current 1003 DESCRIPTION 1004 "A textual name for the APS group which this channel is 1005 included in." 1006 ::= { apsChanConfigEntry 1 } 1008 apsChanNumber OBJECT-TYPE 1009 SYNTAX Integer32 (0..14) 1010 MAX-ACCESS not-accessible 1011 STATUS current 1012 DESCRIPTION 1013 "This field is set to a unique channel number within an APS group. 1014 The value 0 indicates the null channel. The values 1-14 define a 1015 working channel. 1017 This field must be assigned a unique number within the group." 1019 ::= { apsChanConfigEntry 2 } 1021 apsChanRowStatus OBJECT-TYPE 1022 SYNTAX RowStatus 1023 MAX-ACCESS read-create 1024 STATUS current 1025 DESCRIPTION 1026 "The status of this APS channel entry. 1028 An entry may not exist in the active state unless all 1029 objects in the entry have an appropriate value. 1031 A row may not be created with an apsChanGroupName value 1032 equal to an apsConfigName value if the associated 1033 apsConfigRowStatus object is equal to active. However, 1034 if the apsConfigRowStatus object is equal to notInService, 1035 a row may be created. In other words, a channel may not 1036 be added to an active group. 1038 A row may be created with an apsChanGroupName value 1039 that is not equal to any existing instance of apsConfigName. 1040 This action is the initial step in adding a SONET LTE to a 1041 new APS group. An instance of apsConfigName equal to this 1042 instance of apsChanGroupName will subsequently be created. 1044 If this object is set to destroy, the associated instance 1045 of apsMapGroupName will be set to a string of size 0 and 1046 the apsMapChanNumber will be set to -1 1047 The channel command and channel status entries will also be 1048 deleted by this action. 1050 apsChanNumber must be set to a unique channel number within 1051 the APS group. The value 0 indicates the null channel. 1052 The values 1-14 define a working channel. When an attempt is 1053 made to set the corresponding apsConfigRowStatus field to 1054 active the apsChanNumber values of all entries with equal 1055 apsChanGroupName fields must represent a set of consecutive 1056 integer values beginning with 0 and ending with n, where n is 1057 greater than or equal to 1 and less than or equal to 14. Otherwise 1058 the error inconsistentValue is returned to the apsConfigRowStatus 1059 set attempt. 1060 " 1061 ::= { apsChanConfigEntry 3 } 1063 apsChanIfIndex OBJECT-TYPE 1064 SYNTAX InterfaceIndex 1065 MAX-ACCESS read-create 1066 STATUS current 1067 DESCRIPTION 1068 "The Interface Index assigned to a SONET LTE. This is an 1069 interface with ifType sonet(39). This must not be set 1070 to the InterfaceIndex of a SONET LTE that is currently 1071 configured in an APS group. This cannot be set if 1072 the group specified by apsChanGroupName is currently active. 1073 " 1075 ::= { apsChanConfigEntry 4 } 1077 apsChanPriority OBJECT-TYPE 1078 SYNTAX INTEGER {low(1), high(2)} 1079 MAX-ACCESS read-create 1080 STATUS current 1081 DESCRIPTION 1082 "The priority of the channel. 1084 This field deterimines whether high or low priority 1085 SD and SF codes are used in K1 requests. 1087 This field is only applicable if the channel is to be included in 1088 a group using the 1:n architecture. It is not applicable if the 1089 channel is to be included in a group using the 1+1 architecture, 1090 and is ignored in that case. 1091 " 1092 DEFVAL { 1 } 1093 ::= { apsChanConfigEntry 5 } 1095 -- 1096 -- APS Command Table 1097 -- 1098 -- This table provides the ability to initiate APS commands. 1099 -- 1101 apsCommandTable OBJECT-TYPE 1102 SYNTAX SEQUENCE OF ApsCommandEntry 1103 MAX-ACCESS not-accessible 1104 STATUS current 1105 DESCRIPTION 1106 "This table allows commands to be sent to configured APS groups." 1107 ::= { apsMIBObjects 5 } 1109 apsCommandEntry OBJECT-TYPE 1110 SYNTAX ApsCommandEntry 1111 MAX-ACCESS not-accessible 1112 STATUS current 1113 DESCRIPTION 1114 "A conceptual row in the apsCommandTable." 1115 INDEX {apsChanGroupName, apsChanNumber} 1116 ::= { apsCommandTable 1 } 1118 ApsCommandEntry ::= SEQUENCE { 1119 apsCommandSwitch ApsSwitchCommand, 1120 apsCommandControl ApsControlCommand 1121 } 1123 apsCommandSwitch OBJECT-TYPE 1124 SYNTAX ApsSwitchCommand 1125 MAX-ACCESS read-write 1126 STATUS current 1127 DESCRIPTION 1128 "Allows the initiation of an APS switch command on the 1129 APS group and channel specified by the index values. 1131 When read this object returns the last command written 1132 or noCmd(1) if no command has been written to this 1133 channel since initialization. The return of the last command 1134 written does not imply that this command is currently in effect. 1135 This request may have been preempted by a higer priority 1136 local or remote request. In order to determine the 1137 current state of the APS group it is necessary to read 1138 the objects apsStatusK1K2Rcv and apsStatusK1K2Trans. 1140 The value lockoutOfProtection(2) should only be applied 1141 to the protection line channel since that switch command 1142 prevents any of the working channels from switching to the protection 1143 line. Following the same logic, forcedSwitchProtectToWork(4) and 1144 manualSwitchProtectToWork(6) should only be applied to the protection 1145 line channel. 1147 forcedSwitchWorkToProtect(3) and manualSwitchWorkToProtect(5) 1148 should only be applied to a working channel. 1149 " 1150 ::= { apsCommandEntry 1 } 1152 apsCommandControl OBJECT-TYPE 1153 SYNTAX ApsControlCommand 1154 MAX-ACCESS read-write 1155 STATUS current 1156 DESCRIPTION 1157 "Allows the initiation of an APS control command on the 1158 APS group and channel specified by the index values. 1160 When read this object returns the last command written 1161 or noCmd(1) if no command has been 1162 written to this channel since initialization. 1164 This command should not be applied to the protection 1165 line however, for simplicity the value noCmd(1) 1166 can be returned if this object is queried with the protection line 1167 channel. 1168 " 1169 ::= { apsCommandEntry 2 } 1171 -- 1172 -- APS Channel Status Table 1173 -- 1174 -- This table provides APS channel statistics. 1175 -- 1177 apsChanStatusTable OBJECT-TYPE 1178 SYNTAX SEQUENCE OF ApsChanStatusEntry 1179 MAX-ACCESS not-accessible 1180 STATUS current 1181 DESCRIPTION 1182 "This table contains status information for all SONET LTE 1183 interfaces that are included in APS groups." 1184 ::= { apsMIBObjects 6 } 1186 apsChanStatusEntry OBJECT-TYPE 1187 SYNTAX ApsChanStatusEntry 1188 MAX-ACCESS not-accessible 1189 STATUS current 1190 DESCRIPTION 1191 "A conceptual row in the apsChanStatusTable." 1192 INDEX {apsChanGroupName, apsChanNumber} 1193 ::= { apsChanStatusTable 1 } 1195 ApsChanStatusEntry ::= SEQUENCE { 1196 apsChanStatus BITS, 1197 apsChanSignalDegrades Counter32, 1198 apsChanSignalFailures Counter32, 1199 apsChanSwitchovers Counter32, 1200 apsChanLastSwitchover TimeTicks 1201 } 1203 apsChanStatus OBJECT-TYPE 1204 SYNTAX BITS { 1205 lockedOut(0), 1206 sd(1), 1207 sf(2), 1208 switched(3) 1209 } 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "Indicates the current state of the port. 1215 lockedOut 1217 This bit, when applied to a working channel, indicates that 1218 the channel is prevented from switching to the protection line. 1219 When applied to the null channel, this bit indicates that no 1220 working channel may switch to the protection line. 1222 sd 1224 A signal degrade condition is in effect. 1226 sf 1228 A signal failure condition is in effect. 1230 switched 1232 The switched bit is applied to a working channel if that 1233 channel is currently switched to the protection line. 1234 " 1235 ::= { apsChanStatusEntry 1 } 1237 apsChanSignalDegrades OBJECT-TYPE 1238 SYNTAX Counter32 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "A count of Signal Degrade conditions. This 1243 condition occurs when the line Bit Error Rate 1244 exceeds the currently configured threshold." 1245 ::= { apsChanStatusEntry 2 } 1247 apsChanSignalFailures OBJECT-TYPE 1248 SYNTAX Counter32 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "A count of Signal Failure conditions that have been 1253 detected on the incoming signal. This condition occurs 1254 when a loss of signal, loss of frame, AIS-L or a Line 1255 bit error rate exceeding 10^-3 is detected on an 1256 incoming line." 1257 ::= { apsChanStatusEntry 3 } 1259 apsChanSwitchovers OBJECT-TYPE 1260 SYNTAX Counter32 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "The number of times this channel has switched to the protection 1265 line. When queried with index value apsChanNumber set to 0, which 1266 is the protection line, this object will return 0. " 1267 ::= { apsChanStatusEntry 4 } 1269 apsChanLastSwitchover OBJECT-TYPE 1270 SYNTAX TimeTicks 1271 MAX-ACCESS read-only 1272 STATUS current 1273 DESCRIPTION 1274 "The value of sysUpTime when this channel last completed a switch 1275 to the protection line. If this channel has never switched to the 1276 protection line, or this channel is the protection line, the value 1277 0 will be returned." 1278 ::= { apsChanStatusEntry 5 } 1280 -- 1281 -- APS TRAPS 1282 -- 1284 apsNotificationsPrefix OBJECT IDENTIFIER 1285 ::= { apsMIBNotifications 0 } 1287 apsTrapSwitchover NOTIFICATION-TYPE 1288 OBJECTS { apsChanSwitchovers, apsChanStatus } 1289 STATUS current 1290 DESCRIPTION 1291 "An apsTrapSwitchover notification is sent when the 1292 value of an instance of apsChanSwitchovers increments." 1293 ::= { apsNotificationsPrefix 1 } 1295 apsTrapModeMismatch NOTIFICATION-TYPE 1296 OBJECTS { apsStatusModeMismatches, apsStatusCurrent } 1297 STATUS current 1298 DESCRIPTION 1299 "An apsTrapModeMismatch notification is sent when the 1300 value of an instance of apsStatusModeMismatches increments." 1301 ::= { apsNotificationsPrefix 2 } 1303 apsTrapChannelMismatch NOTIFICATION-TYPE 1304 OBJECTS { apsStatusChannelMismatches, apsStatusCurrent } 1305 STATUS current 1306 DESCRIPTION 1307 "An apsTrapChannelMismatch notification is sent when the 1308 value of an instance of apsStatusChannelMismatches increments." 1309 ::= { apsNotificationsPrefix 3 } 1311 apsTrapPSBF NOTIFICATION-TYPE 1312 OBJECTS { apsStatusPSBFs, apsStatusCurrent } 1313 STATUS current 1314 DESCRIPTION 1315 "An apsTrapPSBF notification is sent when the 1316 value of an instance of apsStatusPSBFs increments." 1317 ::= { apsNotificationsPrefix 4 } 1319 apsTrapFEPLF NOTIFICATION-TYPE 1320 OBJECTS { apsStatusFEPLFs, apsStatusCurrent } 1321 STATUS current 1322 DESCRIPTION 1323 "An apsTrapFEPLFs notification is sent when the 1324 value of an instance of apsStatusFEPLFs increments." 1325 ::= { apsNotificationsPrefix 5 } 1327 -- conformance information 1329 apsGroups OBJECT IDENTIFIER ::= { apsMIBConformance 1 } 1330 apsCompliances OBJECT IDENTIFIER ::= { apsMIBConformance 2 } 1332 apsCompliance MODULE-COMPLIANCE 1333 STATUS current 1334 DESCRIPTION 1335 "The compliance statement for linear APS groups." 1337 MODULE 1338 MANDATORY-GROUPS { apsConfigGeneral, apsStatusGeneral, apsChanGeneral } 1340 OBJECT apsConfigMode 1341 MIN-ACCESS read-only 1342 DESCRIPTION 1343 "Write access is not required." 1345 OBJECT apsConfigSdBerThreshold 1346 MIN-ACCESS read-only 1347 DESCRIPTION 1348 "Write access is not required." 1350 OBJECT apsConfigSfBerThreshold 1351 MIN-ACCESS read-only 1352 DESCRIPTION 1353 "Write access is not required." 1355 OBJECT apsConfigWaitToRestore 1356 MIN-ACCESS read-only 1357 DESCRIPTION 1358 "Write access is not required." 1360 OBJECT apsConfigRowStatus 1361 MIN-ACCESS read-only 1362 DESCRIPTION 1363 "Write access is not required." 1365 OBJECT apsChanIfIndex 1366 MIN-ACCESS read-only 1367 DESCRIPTION 1368 "Write access is not required." 1370 OBJECT apsChanPriority 1371 MIN-ACCESS read-only 1372 DESCRIPTION 1373 "Write access is not required." 1375 OBJECT apsChanRowStatus 1376 MIN-ACCESS read-only 1377 DESCRIPTION 1378 "Write access is not required." 1380 GROUP apsConfigOneToN 1381 DESCRIPTION 1382 "Implementation of this group is optional for all 1383 linear APS implementations. The information is 1384 applicable to groups implementing the linear 1385 APS 1:n architecture" 1387 GROUP apsCommandOnePlusOne 1388 DESCRIPTION 1389 "Implementation of this group is optional for all 1390 linear APS implementations. The information is 1391 applicable to groups implementing the linear 1392 APS 1+1 architecture and supporting set operations." 1394 GROUP apsCommandOneToN 1395 DESCRIPTION 1396 "Implementation of this group is optional for all 1397 linear APS implementations. The information is 1398 applicable to groups implementing the linear 1399 APS 1:n architecture and supporting set operations." 1401 GROUP apsChanOneToN 1402 DESCRIPTION 1403 "Implementation of this group is optional for all 1404 linear APS implementations. The information is 1405 applicable to groups implementing the linear 1406 APS 1:n architecture." 1408 GROUP apsTotalsGroup 1409 DESCRIPTION 1410 "Implementation of this group is optional for all 1411 linear APS implementations." 1413 GROUP apsMapGroup 1414 DESCRIPTION 1415 "Implementation of this group is optional for all 1416 linear APS implementations." 1418 ::= { apsCompliances 1 } 1420 -- units of conformance 1422 apsConfigGeneral OBJECT-GROUP 1423 OBJECTS 1424 { 1425 apsConfigMode, 1426 apsConfigSdBerThreshold, 1427 apsConfigSfBerThreshold, 1428 apsConfigCreationTime, 1429 apsConfigRowStatus 1430 } 1431 STATUS current 1432 DESCRIPTION 1433 "A collection of apsConfigTable objects providing configuration 1434 information applicable to all linear APS groups." 1435 ::= { apsGroups 1 } 1437 apsConfigOneToN OBJECT-GROUP 1438 OBJECTS 1439 { 1440 apsConfigWaitToRestore 1441 } 1442 STATUS current 1443 DESCRIPTION 1444 "The apsConfigTable object that provides information which is only 1445 applicable to groups implementing the linear APS 1:n architecture." 1446 ::= { apsGroups 2 } 1448 -- If set operations are not supported neither of the following two groups 1449 -- are implemented. If sets are supported only one of these groups is 1450 -- implemented for a linear APS group instance. 1452 apsCommandOnePlusOne OBJECT-GROUP 1453 OBJECTS 1454 { 1455 apsCommandSwitch 1456 } 1457 STATUS current 1458 DESCRIPTION 1459 "The apsCommandTable object which is applicable to groups 1460 implementing the linear APS 1+1 architecture. Also, set operations 1461 must be supported." 1462 ::= { apsGroups 3 } 1464 apsCommandOneToN OBJECT-GROUP 1465 OBJECTS 1466 { 1467 apsCommandSwitch, 1468 apsCommandControl 1469 } 1470 STATUS current 1471 DESCRIPTION 1472 "A collection of apsCommandTable objects which are applicable to 1473 groups implementing the linear APS 1:n architecture. Also, set 1474 operations must be supported." 1475 ::= { apsGroups 4 } 1477 apsStatusGeneral OBJECT-GROUP 1478 OBJECTS 1479 { 1480 apsStatusK1K2Rcv, 1481 apsStatusK1K2Trans, 1482 apsStatusCurrent, 1483 apsStatusModeMismatches, 1484 apsStatusChannelMismatches, 1485 apsStatusPSBFs, 1486 apsStatusFEPLFs 1487 } 1488 STATUS current 1489 DESCRIPTION 1490 "A collection of apsStatusTable objects providing status information 1491 applicable to all linear APS groups." 1493 ::= { apsGroups 5 } 1495 apsChanGeneral OBJECT-GROUP 1496 OBJECTS 1497 { 1498 apsChanIfIndex, 1499 apsChanRowStatus, 1500 apsChanStatus, 1501 apsChanSignalDegrades, 1502 apsChanSignalFailures, 1503 apsChanSwitchovers, 1504 apsChanLastSwitchover 1505 } 1506 STATUS current 1507 DESCRIPTION 1508 "A collection of channel objects providing information applicable to 1509 all linear APS channels." 1510 ::= { apsGroups 6 } 1512 apsChanOneToN OBJECT-GROUP 1513 OBJECTS 1514 { 1515 apsChanPriority 1516 } 1517 STATUS current 1518 DESCRIPTION 1519 "The apsChanConfigTable object that provides information which is only 1520 applicable to groups implementing the linear APS 1:n architecture." 1521 ::= { apsGroups 7 } 1523 apsTotalsGroup OBJECT-GROUP 1524 OBJECTS 1525 { 1526 apsConfigGroups, 1527 apsChanLTEs 1528 } 1529 STATUS current 1530 DESCRIPTION 1531 "A collection of objects providing optional counts of configured APS groups 1532 and SONET LTE interfaces." 1533 ::= { apsGroups 8 } 1535 apsMapGroup OBJECT-GROUP 1536 OBJECTS 1537 { 1538 apsMapGroupName, 1539 apsMapChanNumber 1541 } 1542 STATUS current 1543 DESCRIPTION 1544 "A collection of apsMapTable objects providing a mapping 1545 from sonet(39) InterfaceIndex to group name and channel 1546 number for assigned APS channels and a list of unassigned 1547 sonet(39) interfaces." 1548 ::= { apsGroups 9 } 1550 apsTrapOptional NOTIFICATION-GROUP 1551 NOTIFICATIONS {apsTrapSwitchover, apsTrapModeMismatch, 1552 apsTrapChannelMismatch, apsTrapPSBF, 1553 apsTrapFEPLF } 1554 STATUS current 1555 DESCRIPTION 1556 "A collection of SONET linear APS notifications that may optionally be 1557 implemented." 1558 ::= { apsGroups 10 } 1560 END 1562 6. Intellectual Property 1564 The IETF takes no position regarding the validity or scope of any 1565 intellectual property or other rights that might be claimed to 1566 pertain to the implementation or use of the technology described in 1567 this document or the extent to which any license under such rights 1568 might or might not be available; neither does it represent that it 1569 has made any effort to identify any such rights. Information on the 1570 IETF's procedures with respect to rights in standards-track and 1571 standards-related documentation can be found in BCP-11. Copies of 1572 claims of rights made available for publication and any assurances of 1573 licenses to be made available, or the result of an attempt made to 1574 obtain a general license or permission for the use of such 1575 proprietary rights by implementors or users of this specification can 1576 be obtained from the IETF Secretariat. 1578 7. Acknowledgments 1580 This document is a product of the AToMMIB Working Group. A number of 1581 constructs from a separate draft submission by Ken Chapman have been 1582 included here. Additionally, suggestions by Orly Nicklass and Kaj Tesink 1583 have been incorporated. 1585 8. References 1587 [1] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for 1588 Describing SNMP Management Frameworks, RFC 2571, Cabletron Systems, 1589 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 1591 [2] Rose, M., and K. McCloghrie, Structure and Identification of 1592 Management Information for TCP/IP-based Internets, RFC 1155, 1593 STD 16, Performance Systems International, Hughes LAN Systems, May 1990 1595 [3] Rose, M., and K. McCloghrie, Concise MIB Definitions, RFC 1212, 1596 STD 16, Performance Systems International, Hughes LAN Systems, March 1991 1598 [4] M. Rose, A Convention for Defining Traps for use with the SNMP, 1599 RFC 1215, Performance Systems International, March 1991 1601 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1602 M., and S. Waldbusser, Structure of Management Information Version 2 1603 (SMIv2), RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1604 Braunschweig, SNMP Research, First Virtual Holdings, International 1605 Network Services, April 1999 1607 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1608 M., and S. Waldbusser, Textual Conventions for SMIv2, RFC 2579, 1609 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1610 First Virtual Holdings, International Network Services, April 1999 1612 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1613 M., and S. Waldbusser, Conformance Statements for SMIv2, RFC 1614 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1615 First Virtual Holdings, International Network Services, April 1999 1617 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, Simple Network 1618 Management Protocol, RFC 1157, STD 15, SNMP Research, Performance 1619 Systems International, Performance Systems International, MIT Laboratory 1620 for Computer Science, May 1990. 1622 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1623 Introduction to Community-based SNMPv2, RFC 1901, SNMP Research, 1624 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1625 Network Services, January 1996. 1627 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1628 Transport Mappings for Version 2 of the Simple 1629 Network Management Protocol (SNMPv2), RFC 1906, SNMP Research, Inc., 1630 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1631 Network Services, January 1996. 1633 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, Message 1634 Processing and Dispatching for the Simple Network Management Protocol 1635 (SNMP), RFC 2572, SNMP Research, Inc., Cabletron Systems, Inc., 1636 BMC Software, Inc., IBM T. J. Watson Research, April 1999 1638 [12] Blumenthal, U., and B. Wijnen, User-based Security Model (USM) 1639 for version 3 of the Simple Network Management Protocol (SNMPv3), 1640 RFC 2574, IBM T. J. Watson Research, April 1999 1642 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1643 Protocol Operations for Version 2 of the Simple 1644 Network Management Protocol (SNMPv2), RFC 1905, SNMP Research, Inc., 1645 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1646 Network Services, January 1996. 1648 [14] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, 1649 RFC 2573, SNMP Research, Inc., Secure Computing Corporation, 1650 Cisco Systems, April 1999 1652 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based Access 1653 Control Model (VACM) for the Simple Network Management Protocol 1654 (SNMP), RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1655 Cisco Systems, Inc., April 1999 1657 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, Introduction to 1658 Version 3 of the Internet-standard Network Management Framework, 1659 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, Inc., 1660 Ericsson, Cisco Systems, April 1999 1662 [17] McCloghrie, K., and F. Kastenholz. "The Interfaces Group MIB 1663 using SMIv2", RFC 2233, November 1997. 1665 [18] GR-253-CORE Issue 2, December 1995, Revision 2, January 1999 1667 [19] ITU-T Recommendation G.783 (04/97) 1669 [20] K. Chapman, "Definitions of Managed Objects for SONET Linear 1670 Automatic Protection Switching (APS)", 1671 draft-kchapman-sonet-aps-00.txt, July 1999 1673 9.Security Considerations 1675 There are a number of management objects defined in this MIB 1676 that have a MAX-ACCESS clause of read-write and/or read-create. 1677 Such objects may be considered sensitive or vulnerable in some 1678 network environments. The support for SET operations in a 1679 non-secure environment without proper protection can have a 1680 negative effect on network operations. 1682 SNMPv1 by itself is not a secure environment. Even if the 1683 network itself is secure (for example by using IPSec), even then, 1684 there is no control as to who on the secure network is allowed 1685 to access and GET/SET (read/change/create/delete) the objects in 1686 this MIB. 1688 It is recommended that the implementers consider the security 1689 features as provided by the SNMPv3 framework. Specifically, the 1690 use of the User-based Security Model RFC 2574 [RFC2574] and the 1691 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1693 It is then a customer/user responsibility to ensure that the SNMP 1694 entity giving access to an instance of this MIB, is properly 1695 configured to give access to the objects only to those 1696 principals (users) that have legitimate rights to indeed GET or 1697 SET (change/create/delete) them. 1699 10. Editor's Address 1701 Jeff Johnson 1702 RedBack Networks. Inc. 1703 350 Holger Way 1704 San Jose, CA 95134-1362 1705 Phone: +1 408 571 5460 1706 Email: jeff@redback.com 1708 Michael Thatcher 1709 RedBack Networks. Inc. 1710 350 Holger Way 1711 San Jose, CA 95134-1362 1712 Phone: +1 408 571 5449 1713 Email: thatcher@redback.com 1715 Jim Kuhfeld 1716 RedBack Networks. Inc. 1717 350 Holger Way 1718 San Jose, CA 95134-1362 1719 Phone: +1 408 571 5465 1720 Email: jkuhfeld@redback.com 1722 11. Full Copyright Statement 1724 Copyright (C) The Internet Society (1999). All Rights Reserved. 1726 This document and translations of it may be copied and furnished 1727 to others, and derivative works that comment on or otherwise 1728 explain it or assist in its implmentation may be prepared, copied, 1729 published and distributed, in whole or in part, without 1730 restriction of any kind, provided that the above copyright notice 1731 and this paragraph are included on all such copies and derivative 1732 works. However, this document itself may not be modified in any 1733 way, such as by removing the copyright notice or references to the 1734 Internet Society or other Internet organizations, except as needed 1735 for the purpose of developing Internet standards in which case the 1736 procedures for copyrights defined in the Internet Standards 1737 process must be followed, or as required to translate it into 1738 languages other than English. 1740 The limited permissions granted above are perpetual and will not 1741 be revoked by the Internet Society or its successors or assigns. 1743 This document and the information contained herein is provided on 1744 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1745 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1746 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1747 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1748 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 1749 PURPOSE."