idnits 2.17.1 draft-ietf-atommib-sonetaps-mib-04.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 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 72 instances of too long lines in the document, the longest one being 7 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 145 has weird spacing: '...ponding chann...' == Line 1060 has weird spacing: '...set the corre...' == Line 1064 has weird spacing: '...re n is great...' == Line 1502 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 2, 2001) is 8418 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: 'RFC2571' on line 61 -- Looks like a reference, but probably isn't: 'RFC1155' on line 66 -- Looks like a reference, but probably isn't: 'RFC1212' on line 66 -- Looks like a reference, but probably isn't: 'RFC1215' on line 67 -- Looks like a reference, but probably isn't: 'RFC2578' on line 68 -- Looks like a reference, but probably isn't: 'RFC2579' on line 68 -- Looks like a reference, but probably isn't: 'RFC2580' on line 69 -- Looks like a reference, but probably isn't: 'RFC1157' on line 82 -- Looks like a reference, but probably isn't: 'RFC1901' on line 76 -- Looks like a reference, but probably isn't: 'RFC1906' on line 78 -- Looks like a reference, but probably isn't: 'RFC2572' on line 78 -- Looks like a reference, but probably isn't: 'RFC2574' on line 1717 -- Looks like a reference, but probably isn't: 'RFC1905' on line 84 -- Looks like a reference, but probably isn't: 'RFC2573' on line 87 -- Looks like a reference, but probably isn't: 'RFC2575' on line 1718 -- Looks like a reference, but probably isn't: 'RFC2570' on line 91 == Unused Reference: '1' is defined on line 1631, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 1634, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 1638, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1641, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 1644, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 1648, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1652, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 1656, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1659, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1662, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 1666, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 1670, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 1674, but no explicit reference was found in the text == Unused Reference: '14' is defined on line 1678, but no explicit reference was found in the text == Unused Reference: '15' is defined on line 1681, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 1685, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 1689, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1692, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1694, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1696, 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) -- 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: 18 errors (**), 0 flaws (~~), 27 warnings (==), 21 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT SONET LINEAR APS MIB J. Johnson 3 Expires October 2, 2001 M. Thatcher 4 J. Kuhfeld 5 Redback Networks 6 April 2, 2001 8 Definitions of Managed Objects 9 for SONET Linear APS architectures 11 draft-ietf-atommib-sonetaps-mib-04.txt 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of Section 10 of RFC2026. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The Internet Society 2001. All Rights Reserved. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in TCP/IP based internets. 42 In particular it defines objects for managing networks using SONET 43 linear Automatic Protection Switching (APS) architectures. 45 This memo specifies a MIB module in a manner that is both compliant 46 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 47 definitions. 49 1. Introduction 51 This memo defines a portion of the Management Information Base (MIB) 52 used for managing SONET linear Automatic Protection Switching (APS) 53 architectures. Two linear APS architectures are supported, the 1+1 54 architecture and the 1:n architecture. 56 2. The SNMP Management Framework 58 The SNMP Management Framework presently consists of five major 59 components: 61 An overall architecture, described in RFC 2571 [RFC2571]. 63 Mechanisms for describing and naming objects and events for the 64 purpose of management. The first version of this Structure of 65 Management Information (SMI) is called SMIv1 and described in 66 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 67 1215 [RFC1215]. The second version, called SMIv2, is described 68 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 69 STD 58, RFC 2580 [RFC2580]. 71 Message protocols for transferring management information. The 72 first version of the SNMP message protocol is called SNMPv1 and 73 described in STD 15, RFC 1157 [RFC1157]. A second version of 74 the SNMP message protocol, which is not an Internet standards 75 track protocol, is called SNMPv2c and described in RFC 1901 76 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 77 message protocol is called SNMPv3 and described in RFC 1906 78 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 80 Protocol operations for accessing management information. The 81 first set of protocol operations and associated PDU formats is 82 described in STD 15, RFC 1157 [RFC1157]. A second set of 83 protocol operations and associated PDU formats is described in 84 RFC 1905 [RFC1905]. 86 A set of fundamental applications described in RFC 2573 87 [RFC2573] and the view-based access control mechanism described 88 in RFC 2575 [RFC2575]. 90 A more detailed introduction to the current SNMP Management Framework 91 can be found in RFC 2570 [RFC2570]. 93 Managed objects are accessed via a virtual information store, termed 94 the Management Information Base or MIB. Objects in the MIB are 95 defined using the mechanisms defined in the SMI. 97 This memo specifies a MIB module that is compliant to the SMIv2. A 98 MIB conforming to the SMIv1 can be produced through the appropriate 99 translations. The resulting translated MIB must be semantically 100 equivalent, except where objects or events are omitted because no 101 translation is possible (use of Counter64). Some machine readable 102 information in SMIv2 will be converted into textual descriptions in 103 SMIv1 during the translation process. However, this loss of machine 104 readable information is not considered to change the semantics of the 105 MIB. 107 3. Object Definitions 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. Objects in the MIB are 111 defined using the subset of Abstract Syntax Notation One (ASN.1) 112 defined in the SMI. In particular, each object type is named by an 113 OBJECT IDENTIFIER, an administratively assigned name. The object 114 type together with an object instance serves to uniquely identify a 115 specific instantiation of the object. For human convenience, we 116 often use a textual string, termed the descriptor, to refer to the 117 object type. 119 4. Overview 121 These objects are used to control and manage SONET linear APS 122 architectures. Ring APS groups are not currently supported by this 123 mib. 125 The mib contains two scalars, containing counts of APS groups and 126 SONET LTEs and six tables. 128 The apsMapTable contains entries for each SONET LTE interface 129 available on the system. The table serves two purposes. It can be 130 used to locate SONET LTE interfaces that are not currently included 131 in APS groups. It also provides a mapping from InterfaceIndex to 132 group name and channel number for those SONET LTE interfaces that are 133 included in APS groups. Entries in apsMapTable cannot be added or 134 deleted through operations defined in this mib. However, an 135 apsMapEntry may be added or deleted through other system mechanisms, 136 such as hot swap. Also, existing entries cannot be directly modified 137 and instead, such modifications occur as a result of side-effects of 138 operations on the apsChanConfigTable. 140 The apsChanConfigTable supports addition, modification and deletion 141 of entries representing linear APS channels. Entries are indexed by 142 a text group name and integer channel number. Each entry contains an 143 InterfaceIndex value identifying the SONET LTE used for the channel 144 and the priority of the channel. A side effect of row creation or 145 deletion is creation or deletion of corresponding channel status 146 entries, and the setting of map entry fields. Creation of 2-14 147 entries in this table with a common group name index and consecutive 148 channel numbers beginning with zero is the first step in the creation 149 and configuration of an APS group. It is not necessary to create 150 channel numbers in order, however the resulting set of channels must 151 begin with channel number 0 and must be consecutive. However, if the 152 onePlusOneOptimized architecture is selected, the set of channel 153 numbers begins with 1 instead of 0. Note that the term null channel, 154 which is used throughout this document refers to the protection line. 156 The apsConfigTable supports addition, modification and deletion of 157 entries representing linear APS groups. Entries are indexed by a text 158 group name. Each entry contains parameters that specify the 159 configuration of a particular linear APS group. Entries are created 160 in this table after a set of channels are created in the 161 apsChanConfigTable. In order to successfully set an instance of 162 apsConfigRowStatus to active the apsConfigEntry must contain valid 163 values and all associated apsChanConfigEntry rows must be valid and 164 produce a consecutive set of channels beginning with channel number 0 165 or 1, depending on the selected architecture. 167 The apsCommandTable provides linear APS commands that support 168 protection switching and the ability to modify APS operation. 169 Entries in this table are created as a side effect of setting the 170 associated apsConfigRowStatus object to active. Entries in that table 171 are deleted if the associated apsConfigRowStatus object is set to any 172 value except active. 174 The apsChanStatusTable provides individual channel statistics. 175 Entries in this table are created as a side effect of row addition in 176 the apsChanConfigTable. 178 The apsStatusTable provides group level statistics. Entries in this 179 table are created as a side effect of row addition in apsConfigTable. 181 An APS group is created and configured with the following sequence of 182 events: 184 CHANNEL CONFIGURATION 186 Create an entry in the apsChanConfigTable. Set the 187 apsChanConfigGroupName in an apsChanConfigEntry to a user-friendly 188 text string which will serve as the APS group name. The string must 189 not be equal to the apsConfigName of an existing apsConfigEntry with 190 apsConfigRowStatus set to active, since a channel cannot be added to 191 an active group. The string may be set equal to the apsConfigName of 192 a row which is currently not set to active, or it may be set to a 193 string which does not currently exist in any instance of 194 apsConfigName. A channel number is entered in apsChanConfigNumber. 195 A channel priority is entered in apsChanConfigPriority, if the 196 intended architecture is 1:n. apsChanConfigPriority is ignored if the 197 architecture is 1+1. The InterfaceIndex value of a SONET LTE 198 interface is entered in apsChanConfigIfIndex. 200 This step is repeated for all apsChanConfigEntry instances which are 201 to be included in the APS group. 203 ACTIVATING THE GROUP 205 If the apsChanConfigGroupName does not exist in an instance of 206 apsConfigName, an apsConfigEntry is created with the 207 apsChanConfigGroupName value used as the index for the row. The 208 apsConfigRowStatus value may be set to createAndGo. The 209 apsGroupConfigEntry and apsChanConfigEntry instances with matching 210 name fields will be checked for consistency. If any errors in the 211 channel numbers, architecture or configuration are uncovered the 212 apsConfigRowStatus set will return inconsistentValue, otherwise 213 noError is returned. 215 If the apsChanConfigGroupName value used in channel configuration 216 exists in a previously created, inactive apsConfigEntry instance, the 217 apsConfigRowStatus value may be set to active. 219 An agent is not required to process SNMP Set Requests that affect 220 multiple control objects within this MIB. This is intended to 221 simplify the processing of Set Requests for the various control 222 tables by eliminating the possibility that a single Set PDU will 223 contain multiple varbinds which are in conflict, such as a PDU which 224 both activates a given apsConfigEntry while at the same time it 225 deactivates an associated apsChanConfigEntry. 227 5. Definitions 229 APS-MIB DEFINITIONS ::= BEGIN 230 IMPORTS 231 MODULE-IDENTITY, NOTIFICATION-TYPE, 232 OBJECT-TYPE, 233 Gauge32, Counter32, Integer32, 234 experimental, TimeTicks 235 FROM SNMPv2-SMI 237 TEXTUAL-CONVENTION, RowStatus 238 FROM SNMPv2-TC 240 SnmpAdminString 241 FROM SNMP-FRAMEWORK-MIB 243 InterfaceIndex 244 FROM IF-MIB 246 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 247 FROM SNMPv2-CONF; 249 apsMIB MODULE-IDENTITY 250 LAST-UPDATED "200104022300Z" 251 ORGANIZATION "IETF AToMMIB Working Group" 252 CONTACT-INFO 253 " Jeff Johnson 254 Postal: RedBack Networks. Inc. 255 350 Holger Way 256 San Jose, CA 95134-1362 257 Tel: +1 408 571 5460 258 Email: jeff@redback.com 260 Michael Thatcher 261 Postal: RedBack Networks. Inc. 262 350 Holger Way 263 San Jose, CA 95134-1362 264 Tel: +1 408 571 5449 265 Email: thatcher@redback.com 267 Jim Kuhfeld 268 Postal: RedBack Networks. Inc. 269 350 Holger Way 270 San Jose, CA 95134-1362 271 Tel: +1 408 571 5465 272 Email: jkuhfeld@redback.com" 273 DESCRIPTION 274 "This management information module supports the configuration and 275 management of SONET linear APS groups. The definitions and 276 descriptions used in this mib have been derived from 277 Synchronous Optical Network (SONET) Transport Systems: 279 Common Generic Criteria, GR-253-CORE Revision 2, January 1999, 280 section 5.3. The MIB is also consistent with the Multiplex 281 Section Protection (MSP) protocol as specified in ITU-T 282 Recommendation G.783, Characteristics of synchronous digital 283 hierarchy (SDH) equipment function blocks, Annex A and B. 284 " 286 REVISION "200104022300Z" 287 DESCRIPTION 288 "Initial version of this MIB, published as RFC xxxx." 289 -- xxxx to be assigned by RFC-Editor 290 ::= { experimental XX } 291 -- assign XX 292 -- remove this notice from the MIB 294 apsMIBObjects OBJECT IDENTIFIER 295 ::= { apsMIB 1 } 297 apsMIBNotifications OBJECT IDENTIFIER 298 ::= { apsMIB 2 } 300 apsMIBConformance OBJECT IDENTIFIER 301 ::= { apsMIB 3 } 303 ApsK1K2 ::= TEXTUAL-CONVENTION 304 STATUS current 305 DESCRIPTION 306 "This Textual Convention describes an object that stores 307 a SONET K1 and K2 byte APS protocol field. 309 K1 is located in the first octet, K2 is located in 310 the second octet. Bits are numbered from left to right. 312 Bits 1-4 of the K1 byte indicate a request. 314 1111 Lockout of Protection 315 1110 Forced Switch 316 1101 SF - High Priority 317 1100 SF - Low Priority 318 1011 SD - High Priority 319 1010 SD - Low Priority 320 1001 not used 321 1000 Manual Switch 322 0111 not used 323 0110 Wait-to-Restore 324 0101 not used 325 0100 Exercise 326 0011 not used 327 0010 Reverse Request 328 0001 Do Not Revert 329 0000 No Request 331 Bits 5-8 of the K1 byte indicate the channel associated with the 332 request defined in bits 1-4. 334 0000 is the Null channel. 336 1-14 are working channels. 337 15 is the extra traffic channel 339 Bits 1-4 of the K2 byte indicate a channel. The channel is 340 defined with the same syntax as K1 Bits 5-8. 342 Bit 5 of the K2 byte indicates the 343 architecture. 345 0 if the architecture is 1+1 346 1 if the architecture is 1:n 348 Bits 6-8 of the K2 byte indicates the 349 mode. 351 000 - 011 are reserved for future use 353 100 indicates the mode is unidirectional 354 101 indicates the mode is bidirectional 356 110 RDI-L 358 111 AIS-L 359 " 360 REFERENCE 361 "Bellcore (Telcordia Technologies) GR-253-CORE, Issue 2, 362 Revision 2 (January 1999), 5.3.5." 363 SYNTAX OCTET STRING (SIZE (2)) 365 ApsSwitchCommand ::= TEXTUAL-CONVENTION 366 STATUS current 367 DESCRIPTION 368 "An APS switch command allows a user to perform protection 369 switch actions. 371 The Switch command values are: 373 noCmd 375 This value should be returned by a read request when no switch 376 command has been written to the object in question since 377 initialization. This value may not be used in a write operation. 379 clear 381 Clears all of the switch commands listed below for the specified 382 channel. 384 lockoutOfProtection 386 Prevents any of the working channels from switching to the protection 387 line. The specified channel should be the protection channel. 389 forcedSwitchWorkToProtect 391 Switches the specified working channel to the protection line. 393 forcedSwitchProtectToWork 395 Switches the working channel back from the protection 396 line to the working line. The specified channel should be 397 the protection channel. 399 manualSwitchWorkToProtect 401 Switches the specified working channel to the protection line. 403 manualSwitchProtectToWork 405 Switches the working channel back from the protection 406 line to the working line. The specified channel should be 407 the protection channel. 409 exercise 411 Exercises the protocol for a protection switch of the specified 412 channel by issuing an Exercise request for that channel and 413 checking the response on the APS channel. 414 " 415 SYNTAX INTEGER { 416 noCmd(1), 417 clear(2), 418 lockoutOfProtection(3), 419 forcedSwitchWorkToProtect(4), 420 forcedSwitchProtectToWork(5), 421 manualSwitchWorkToProtect(6), 422 manualSwitchProtectToWork(7), 423 exercise(8) 424 } 426 ApsControlCommand ::= TEXTUAL-CONVENTION 427 STATUS current 428 DESCRIPTION 429 "An APS control command applies only to LTE that support the 430 1:n architecture and performs the following actions. 432 The Control command values are: 434 noCmd 436 This value should be returned by a read request when no control 437 command has been written to the object in question since 438 initialization. This value may not be used in a write operation. 440 lockoutWorkingChannel 442 Prevents the specified working channel from switching to the protection 443 line. 445 clearLockoutWorkingChannel 447 Clears the lockout a working channel command for the channel specified. 448 " 449 SYNTAX INTEGER { 450 noCmd(1), 451 lockoutWorkingChannel(2), 452 clearLockoutWorkingChannel(3) 453 } 455 -- 456 -- APS Configuration Table 457 -- 458 -- This table supports the addition, configuration and deletion of APS 459 -- groups. 460 -- 462 apsConfig OBJECT IDENTIFIER ::= { apsMIBObjects 1 } 463 apsConfigGroups OBJECT-TYPE 464 SYNTAX Gauge32 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "The count of APS groups. This count includes all rows in 469 apsConfigTable." 470 ::= { apsConfig 1 } 472 apsConfigTable OBJECT-TYPE 473 SYNTAX SEQUENCE OF ApsConfigEntry 474 MAX-ACCESS not-accessible 475 STATUS current 476 DESCRIPTION 477 "This table lists the APS groups that have been configured 478 on the system." 479 ::= { apsConfig 2 } 481 apsConfigEntry OBJECT-TYPE 482 SYNTAX ApsConfigEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "A conceptual row in the apsConfigTable." 487 INDEX { IMPLIED apsConfigName } 488 ::= { apsConfigTable 1 } 490 ApsConfigEntry ::= SEQUENCE { 491 apsConfigName SnmpAdminString, 492 apsConfigRowStatus RowStatus, 493 apsConfigMode INTEGER, 494 apsConfigRevert INTEGER, 495 apsConfigDirection INTEGER, 496 apsConfigExtraTraffic INTEGER, 497 apsConfigSdBerThreshold Integer32, 498 apsConfigSfBerThreshold Integer32, 499 apsConfigWaitToRestore Integer32, 500 apsConfigCreationTime TimeTicks 501 } 503 apsConfigName OBJECT-TYPE 504 SYNTAX SnmpAdminString (SIZE (1..32)) 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION 508 "A textual name for the APS group. 510 " 511 ::= { apsConfigEntry 1 } 513 apsConfigRowStatus OBJECT-TYPE 514 SYNTAX RowStatus 515 MAX-ACCESS read-create 516 STATUS current 517 DESCRIPTION 518 "The status of this APS group entry. 520 An entry may not exist in the active state unless all 521 objects in the entry have an appropriate value. Also, 522 all associated apsChanConfigEntry rows must represent 523 a set of consecutive channel numbers beginning with 524 0 or 1, depending on the selected architecture. 526 When set to notInService changes may be made to apsConfigMode, 527 apsConfigRevert, apsConfigDirection, apsConfigExtraTraffic, 528 apsConfigSdBerThreshold, apsConfigSfBerThreshold, 529 and apsConfigWaitToRestore. Also, associated apsChanConfigTable 530 objects may be added, deleted and modified. 531 " 532 ::= { apsConfigEntry 2 } 534 apsConfigMode OBJECT-TYPE 535 SYNTAX INTEGER { 536 onePlusOne(1), 537 oneToN(2), 538 onePlusOneCompatible(3), 539 onePlusOneOptimized(4) 540 } 541 MAX-ACCESS read-create 542 STATUS current 543 DESCRIPTION 544 "The architecture of the APS group. 546 onePlusOne 548 The 1+1 architecture permanently bridges the working 549 line to the protection line. 551 oneToN 553 The 1:n architecture allows one protection channel to 554 protect up to n working channels. When a fault is detected 555 on one of the n working channels that channel is bridged 556 over the protection channel. 558 onePlusOneCompatible 560 This refers to 1 + 1 bidirectional switching compatible with 561 1:n bidirectional switching as specified in ITU-T 562 Recommendation G.783 (04/97) section A.3.4.1. Since this 563 mode necessitates bidirectional switching, apsConfigDirection 564 must be set to bidirectional whenever onePlusOneCompatible is set. 566 onePlusOneOptimized 568 This refers to 1 + 1 bidirectional switching optimized 569 for a network using predominantly 1 + 1 bidirectional 570 switching as specified in ITU-T Recommendation G.783 (04/97) 571 section B.1. Since this mode necessitates bidirectional 572 switching, apsConfigDirection must be set to bidirectional 573 whenever onePlusOneOptimized is set. 575 This object may not be modified if the associated 576 apsConfigRowStatus object is equal to active(1)." 577 DEFVAL {onePlusOne} 578 ::= { apsConfigEntry 3 } 580 apsConfigRevert OBJECT-TYPE 581 SYNTAX INTEGER { nonrevertive(1), revertive(2) } 582 MAX-ACCESS read-create 583 STATUS current 584 DESCRIPTION 585 "The revertive mode of the APS group. 587 nonrevertive 589 Traffic remains on the protection line until another switch 590 request is received. 592 revertive 594 When the condition that caused a switch to the protection 595 line has been cleared the signal is switched back to the 596 working line. Since switching is revertive with the 1:n 597 architecture, apsConfigRevert must be set to revertive if 598 apsConfigMode is set to oneToN. 600 Switching may optionally be revertive with the 1+1 architecture. 602 This object may not be modified if the associated 603 apsConfigRowStatus object is equal to active(1). 604 " 606 DEFVAL { nonrevertive } 607 ::= { apsConfigEntry 4 } 609 apsConfigDirection OBJECT-TYPE 610 SYNTAX INTEGER { unidirectional(1), bidirectional(2) } 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "The directional mode of the APS group. 616 unidirectional 618 The unidirectional mode provides protection in one direction. 620 bidirectional 622 The bidirectional mode provides protection in both 623 directions. 625 This object may not be modified if the associated 626 apsConfigRowStatus object is equal to active(1). 627 " 628 DEFVAL {unidirectional} 629 ::= { apsConfigEntry 5 } 631 apsConfigExtraTraffic OBJECT-TYPE 632 SYNTAX INTEGER { enabled(1), disabled(2) } 633 MAX-ACCESS read-create 634 STATUS current 635 DESCRIPTION 636 "This object enables or disables the transfer of extra traffic 637 on the protection channel in a 1:n architecture. This object 638 must be set to disabled if the architecture is 1+1. It may be 639 necessary to disable this in order to interwork with other SONET 640 network elements that don't support extra traffic. 642 This object may not be modified if the associated 643 apsConfigRowStatus object is equal to active(1). 644 " 645 DEFVAL { disabled } 646 ::= { apsConfigEntry 6 } 648 apsConfigSdBerThreshold OBJECT-TYPE 649 SYNTAX Integer32 (5..9) 650 MAX-ACCESS read-create 651 STATUS current 652 DESCRIPTION 653 "The Signal Degrade Bit Error Rate. 655 The negated value of this number is used as the exponent of 656 10 for computing the threshold value for the Bit Error Rate 657 (BER). For example, a value of 5 indicates a BER threshold of 658 10^-5. 660 This object may be modified if the associated 661 apsConfigRowStatus object is equal to active(1)." 662 DEFVAL { 5 } 663 ::= { apsConfigEntry 7 } 665 apsConfigSfBerThreshold OBJECT-TYPE 666 SYNTAX Integer32 (3..5) 667 MAX-ACCESS read-create 668 STATUS current 669 DESCRIPTION 670 "The Signal Failure Bit Error Rate. 672 The negated value of this number is used as the exponent of 673 10 for computing the threshold value for the Bit Error Rate 674 (BER). For example, a value of 5 indicates a BER threshold of 675 10^-5. 677 This object may be modified if the associated 678 apsConfigRowStatus object is equal to active(1)." 679 DEFVAL { 3 } 680 ::= { apsConfigEntry 8 } 682 apsConfigWaitToRestore OBJECT-TYPE 683 SYNTAX Integer32 (0..720) 684 UNITS "seconds" 685 MAX-ACCESS read-create 686 STATUS current 687 DESCRIPTION 688 "The Wait To Restore period in seconds. 690 After clearing of a condition that necessitated an 691 automatic switch, the wait to restore period must elapse 692 before reverting. This is intended to avoid rapid switch 693 oscillations. 695 GR-253-CORE specifies a Wait To Restore range of 5 to 12 696 minutes. G.783 defines a 5 to 12 minute Wait To Restore 697 range in section 5.4.1.1.3, but also allows for a shorter 698 WTR period in Table 2-1, 699 WaitToRestore value (MI_WTRtime: 0..(5)..12 minutes). 701 This object may not be modified if the associated 702 apsConfigRowStatus object is equal to active(1)." 703 DEFVAL { 300 } 704 ::= { apsConfigEntry 9 } 706 apsConfigCreationTime OBJECT-TYPE 707 SYNTAX TimeTicks 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "The value of sysUpTime at the time the row was 712 created" 713 ::= { apsConfigEntry 10 } 715 -- 716 -- APS Status Table 717 -- 718 -- This table provides APS group statistics. 719 -- 721 apsStatusTable OBJECT-TYPE 722 SYNTAX SEQUENCE OF ApsStatusEntry 723 MAX-ACCESS not-accessible 724 STATUS current 725 DESCRIPTION 726 "This table provides status information about APS groups that have 727 been configured on the system." 728 ::= { apsMIBObjects 2 } 730 apsStatusEntry OBJECT-TYPE 731 SYNTAX ApsStatusEntry 732 MAX-ACCESS not-accessible 733 STATUS current 734 DESCRIPTION 735 "A conceptual row in the apsStatusTable. Entries in this 736 table are created as a side effect of row addition in 737 apsConfigTable." 738 INDEX { IMPLIED apsConfigName} 739 ::= { apsStatusTable 1 } 741 ApsStatusEntry ::= SEQUENCE { 742 apsStatusK1K2Rcv ApsK1K2, 743 apsStatusK1K2Trans ApsK1K2, 744 apsStatusCurrent BITS, 745 apsStatusModeMismatches Counter32, 746 apsStatusChannelMismatches Counter32, 747 apsStatusPSBFs Counter32, 748 apsStatusFEPLFs Counter32, 749 apsStatusSwitchedChannel Integer32 750 } 752 apsStatusK1K2Rcv OBJECT-TYPE 753 SYNTAX ApsK1K2 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The current value of the K1 and K2 bytes received on the 758 protection channel." 759 ::= { apsStatusEntry 1 } 761 apsStatusK1K2Trans OBJECT-TYPE 762 SYNTAX ApsK1K2 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "The current value of the K1 and K2 bytes transmitted on the 767 protection channel." 768 ::= { apsStatusEntry 2 } 770 apsStatusCurrent OBJECT-TYPE 771 SYNTAX BITS { 772 modeMismatch(0), 773 channelMismatch(1), 774 psbf(2), 775 feplf(3), 776 extraTraffic(4) 777 } 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "The current status of the APS group. 783 modeMismatch 785 Modes other than 1+1 unidirectional monitor protection line 786 K2 bit 5, which indicates the architecture and K2 bits 787 6-8, which indicate if the mode is unidirectional or 788 bidirectional. A conflict between the current local mode 789 and the received K2 mode information constitutes a 790 mode mismatch. 792 channelMismatch 794 This bit indicates a mismatch between the transmitted K1 channel 795 and the received K2 channel has been detected. 797 psbf 799 This bit indicates a Protection Switch Byte Failure (PSBF) is 800 in effect. This condition occurs when either an inconsistent 801 APS byte or an invalid code is detected. An inconsistent APS 802 byte occurs when no three consecutive K1 bytes of the last 12 803 successive frames are identical, starting with the last frame 804 containing a previously consistent byte. An invalid code occurs 805 when the incoming K1 byte contains an unused code or a code 806 irrelevant for the specific switching operation (e.g., Reverse 807 Request while no switching request is outstanding) in three 808 consecutive frames. An invalid code also occurs when the incoming 809 K1 byte contains an invalid channel number in three consecutive 810 frames. 812 feplf 814 Modes other than 1+1 unidirectional monitor the K1 byte 815 for Far-End Protection-Line failures. A Far-End 816 Protection-Line defect is declared based on receiving 817 SF on the protection line. 819 extraTraffic 821 This bit indicates whether extra traffic is currently being 822 accepted on the protection line. 823 " 824 ::= { apsStatusEntry 3 } 826 apsStatusModeMismatches OBJECT-TYPE 827 SYNTAX Counter32 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "A count of Mode Mismatch conditions." 832 ::= { apsStatusEntry 4 } 834 apsStatusChannelMismatches OBJECT-TYPE 835 SYNTAX Counter32 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "A count of Channel Mismatch conditions." 840 ::= { apsStatusEntry 5 } 842 apsStatusPSBFs OBJECT-TYPE 843 SYNTAX Counter32 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION 847 "A count of Protection Switch Byte Failure conditions. 848 This condition occurs when either an inconsistent APS 849 byte or an invalid code is detected. An inconsistent APS 850 byte occurs when no three consecutive K1 bytes of the last 851 12 successive frames are identical, starting with the last 852 frame containing a previously consistent byte. An invalid 853 code occurs when the incoming K1 byte contains an unused 854 code or a code irrelevant for the specific switching operation 855 (e.g., Reverse Request while no switching request is outstanding) 856 in three consecutive frames. An invalid code also occurs 857 when the incoming K1 byte contains an invalid channel number 858 in three consecutive frames." 859 ::= { apsStatusEntry 6 } 861 apsStatusFEPLFs OBJECT-TYPE 862 SYNTAX Counter32 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "A count of Far-End Protection-Line Failure conditions. 867 This condition is declared based on receiving SF on 868 the protection line in the K1 byte." 869 ::= { apsStatusEntry 7 } 871 apsStatusSwitchedChannel OBJECT-TYPE 872 SYNTAX Integer32 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "This field is set to the number of the channel that is currently 877 switched to protection. The value 0 indicates no channel is 878 switched to protection. The values 1-14 indicate that working 879 channel is switched to protection." 880 ::= { apsStatusEntry 8 } 882 -- 883 -- APS Map Group 884 -- 885 -- Lists the SONET LTE interfaces that may be used to create APS groups. 886 -- 888 apsMap OBJECT IDENTIFIER ::= { apsMIBObjects 3 } 890 apsChanLTEs OBJECT-TYPE 891 SYNTAX Gauge32 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "The count of SONET LTE interfaces on the system. 896 Each interface that is included has an ifType value of sonet(39)." 897 ::= { apsMap 1 } 899 apsMapTable OBJECT-TYPE 900 SYNTAX SEQUENCE OF ApsMapEntry 901 MAX-ACCESS not-accessible 902 STATUS current 903 DESCRIPTION 904 "This table lists the SONET LTE interfaces on the system. 905 Each interface that is listed has an ifType value of sonet(39)." 906 ::= { apsMap 2 } 908 apsMapEntry OBJECT-TYPE 909 SYNTAX ApsMapEntry 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "A conceptual row in the apsMapTable." 914 INDEX { apsMapIfIndex } 915 ::= { apsMapTable 1 } 917 ApsMapEntry ::= SEQUENCE { 918 apsMapIfIndex InterfaceIndex, 919 apsMapGroupName SnmpAdminString, 920 apsMapChanNumber Integer32 921 } 923 apsMapIfIndex OBJECT-TYPE 924 SYNTAX InterfaceIndex 925 MAX-ACCESS not-accessible 926 STATUS current 927 DESCRIPTION 928 "The Interface Index assigned to a SONET LTE. This is an interface 929 with ifType sonet(39)." 930 ::= { apsMapEntry 1 } 932 apsMapGroupName OBJECT-TYPE 933 SYNTAX SnmpAdminString (SIZE (0..32)) 934 MAX-ACCESS read-only 935 STATUS current 936 DESCRIPTION 937 "A textual name for the APS group which this channel is 938 included in. If the channel is not part of an APS group 939 this value is set to a string of size 0. 941 When an instance of apsChanConfigIfIndex is set equal to an 942 instance of apsMapIfIndex, apsMapGroupName is set equal 943 to the corresponding value of apsChanConfigGroupName. 945 If the apsMapIfIndex ceases to be equal to an instance of 946 apsChanConfigIfIndex, either because of a change in the value of 947 apsChanConfigIfIndex, or because of row deletion in the 948 ApsChanConfigTable, apsMapGroupName is set to a string of 949 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. If the SONET LTE is not part of an APS group this 961 value is set to -1. 963 When an instance of apsChanConfigIfIndex is set equal to an instance of 964 apsMapIfIndex, apsMapChanNumber is set equal to the corresponding 965 value of apsChanConfigNumber. 967 If the apsMapIfIndex ceases to be equal to an instance of 968 apsChanConfigIfIndex, either because of a change in the value of 969 apsChanConfigIfIndex, or because of row deletion in the 970 ApsChanConfigTable, apsMapChanNumber is set to -1. 971 " 972 ::= { apsMapEntry 3 } 974 -- 975 -- APS Channel Configuration Table 976 -- 977 -- This table supports the addition, configuration and deletion of channels 978 -- in APS groups. 979 -- 981 apsChanConfigTable OBJECT-TYPE 982 SYNTAX SEQUENCE OF ApsChanConfigEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "This table lists the APS channels that have been configured 987 in APS groups." 988 ::= { apsMIBObjects 4 } 990 apsChanConfigEntry OBJECT-TYPE 991 SYNTAX ApsChanConfigEntry 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "A conceptual row in the apsChanConfigTable." 996 INDEX {apsChanConfigGroupName, apsChanConfigNumber} 997 ::= { apsChanConfigTable 1 } 999 ApsChanConfigEntry ::= SEQUENCE { 1000 apsChanConfigGroupName SnmpAdminString, 1001 apsChanConfigNumber Integer32, 1002 apsChanConfigRowStatus RowStatus, 1003 apsChanConfigIfIndex InterfaceIndex, 1004 apsChanConfigPriority INTEGER 1005 } 1007 apsChanConfigGroupName OBJECT-TYPE 1008 SYNTAX SnmpAdminString (SIZE (1..32)) 1009 MAX-ACCESS not-accessible 1010 STATUS current 1011 DESCRIPTION 1012 "A textual name for the APS group which this channel is 1013 included in." 1014 ::= { apsChanConfigEntry 1 } 1016 apsChanConfigNumber OBJECT-TYPE 1017 SYNTAX Integer32 (0..14) 1018 MAX-ACCESS not-accessible 1019 STATUS current 1020 DESCRIPTION 1021 "This field is set to a unique channel number within an APS group. 1022 The value 0 indicates the null channel. The values 1-14 define a 1023 working channel. 1025 This field must be assigned a unique number within the group." 1026 ::= { apsChanConfigEntry 2 } 1028 apsChanConfigRowStatus OBJECT-TYPE 1029 SYNTAX RowStatus 1030 MAX-ACCESS read-create 1031 STATUS current 1032 DESCRIPTION 1033 "The status of this APS channel entry. 1035 An entry may not exist in the active state unless all 1036 objects in the entry have an appropriate value. 1038 A row in the apsChanConfigTable may not be created, 1039 deleted, set to notInService or otherwise modified 1040 if the apsChanConfigGroupName value is equal to an 1041 apsConfigName value and the associated apsConfigRowStatus 1042 object is equal to active. However, if the apsConfigRowStatus 1043 object is equal to notInService, a row may be created, deleted 1044 or modified. In other words, a channel may not be added, deleted 1045 or modified if the group is active. 1047 A row may be created with an apsChanConfigGroupName value 1048 that is not equal to any existing instance of apsConfigName. 1049 This action is the initial step in adding a SONET LTE to a 1050 new APS group. 1052 If this object is set to destroy, the associated instance 1053 of apsMapGroupName will be set to a string of size 0 and 1054 the apsMapChanNumber will be set to -1. The channel status 1055 entry will also be deleted by this action. 1057 apsChanConfigNumber must be set to a unique channel number within 1058 the APS group. The value 0 indicates the null channel. 1059 The values 1-14 define a working channel. When an attempt is 1060 made to set the corresponding apsConfigRowStatus field to 1061 active the apsChanConfigNumber values of all entries with equal 1062 apsChanConfigGroupName fields must represent a set of consecutive 1063 integer values beginning with 0 or 1, depending on the architecture 1064 of the group, and ending with n, where n is greater than or 1065 equal to 1 and less than or equal to 14. Otherwise, the error 1066 inconsistentValue is returned to the apsConfigRowStatus 1067 set attempt. 1068 " 1070 ::= { apsChanConfigEntry 3 } 1072 apsChanConfigIfIndex OBJECT-TYPE 1073 SYNTAX InterfaceIndex 1074 MAX-ACCESS read-create 1075 STATUS current 1076 DESCRIPTION 1077 "The Interface Index assigned to a SONET LTE. This is an 1078 interface with ifType sonet(39). The value of this object 1079 must be unique among all instances of apsChanConfigIfIndex. 1080 In other words, a particular SONET LTE can only be configured in 1081 one APS group. 1083 This object cannot be set if the apsChanConfigGroupName instance 1084 associated with this row is equal to an instance of apsConfigName and 1085 the corresponding apsConfigRowStatus object is set to active. In other 1086 words this value cannot be changed if the APS group is active. However, 1087 This value may be changed if the apsConfigRowStatus value is equal to 1088 notInService. 1089 " 1091 ::= { apsChanConfigEntry 4 } 1093 apsChanConfigPriority OBJECT-TYPE 1094 SYNTAX INTEGER {low(1), high(2)} 1095 MAX-ACCESS read-create 1096 STATUS current 1097 DESCRIPTION 1098 "The priority of the channel. 1100 This field deterimines whether high or low priority 1101 SD and SF codes are used in K1 requests. 1103 This field is only applicable if the channel is to be included in 1104 a group using the 1:n architecture. It is not applicable if the 1105 channel is to be included in a group using the 1+1 architecture, 1106 and is ignored in that case. 1108 This object cannot be set if the apsChanConfigGroupName instance 1109 associated with this row is equal to an instance of apsConfigName 1110 and the corresponding apsConfigRowStatus object is set to active. 1111 In other words this value cannot be changed if the APS group is 1112 active. However, This value may be changed if the 1113 apsConfigRowStatus value is equal to notInService. 1114 " 1115 DEFVAL { low } 1116 ::= { apsChanConfigEntry 5 } 1118 -- 1119 -- APS Command Table 1120 -- 1121 -- This table provides the ability to initiate APS commands. 1122 -- 1124 apsCommandTable OBJECT-TYPE 1125 SYNTAX SEQUENCE OF ApsCommandEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "This table allows commands to be sent to configured APS groups." 1130 ::= { apsMIBObjects 5 } 1132 apsCommandEntry OBJECT-TYPE 1133 SYNTAX ApsCommandEntry 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "A conceptual row in the apsCommandTable. This row exists only if 1138 the associated apsConfigEntry is active." 1139 INDEX {apsChanConfigGroupName, apsChanConfigNumber} 1140 ::= { apsCommandTable 1 } 1142 ApsCommandEntry ::= SEQUENCE { 1143 apsCommandSwitch ApsSwitchCommand, 1144 apsCommandControl ApsControlCommand 1145 } 1147 apsCommandSwitch OBJECT-TYPE 1148 SYNTAX ApsSwitchCommand 1149 MAX-ACCESS read-write 1150 STATUS current 1151 DESCRIPTION 1152 "Allows the initiation of an APS switch command on the 1153 APS group and channel specified by the index values. 1155 When read this object returns the last command written 1156 or noCmd if no command has been written to this 1157 channel since initialization. The return of the last command 1158 written does not imply that this command is currently in effect. 1159 This request may have been preempted by a higer priority 1160 local or remote request. In order to determine the 1161 current state of the APS group it is necessary to read 1162 the objects apsStatusK1K2Rcv and apsStatusK1K2Trans. 1164 The value lockoutOfProtection should only be applied 1165 to the protection line channel since that switch command 1166 prevents any of the working channels from switching to the protection 1167 line. Following the same logic, forcedSwitchProtectToWork and 1168 manualSwitchProtectToWork should only be applied to the protection 1169 line channel. 1171 forcedSwitchWorkToProtect and manualSwitchWorkToProtect 1172 should only be applied to a working channel. 1173 " 1174 ::= { apsCommandEntry 1 } 1176 apsCommandControl OBJECT-TYPE 1177 SYNTAX ApsControlCommand 1178 MAX-ACCESS read-write 1179 STATUS current 1180 DESCRIPTION 1181 "Allows the initiation of an APS control command on the 1182 APS group and channel specified by the index values. 1184 When read this object returns the last command written 1185 or noCmd if no command has been 1186 written to this channel since initialization. 1188 This object does not apply to the protection line. 1189 " 1190 ::= { apsCommandEntry 2 } 1192 -- 1193 -- APS Channel Status Table 1194 -- 1195 -- This table provides APS channel statistics. 1196 -- 1198 apsChanStatusTable OBJECT-TYPE 1199 SYNTAX SEQUENCE OF ApsChanStatusEntry 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "This table contains status information for all SONET LTE 1204 interfaces that are included in APS groups." 1205 ::= { apsMIBObjects 6 } 1207 apsChanStatusEntry OBJECT-TYPE 1208 SYNTAX ApsChanStatusEntry 1209 MAX-ACCESS not-accessible 1210 STATUS current 1211 DESCRIPTION 1212 "A conceptual row in the apsChanStatusTable. A row in this 1213 table is created as a side effect of row addition in the 1214 apsChanConfigTable. The apsChanStatusTable row exists 1215 as long as the apsChanConfigTable entry exists, regardless 1216 of whether the associated apsChanConfigRowStatus is active. 1217 " 1218 INDEX {apsChanConfigGroupName, apsChanConfigNumber} 1219 ::= { apsChanStatusTable 1 } 1221 ApsChanStatusEntry ::= SEQUENCE { 1222 apsChanStatusCurrent BITS, 1223 apsChanStatusSignalDegrades Counter32, 1224 apsChanStatusSignalFailures Counter32, 1225 apsChanStatusSwitchovers Counter32, 1226 apsChanStatusLastSwitchover TimeTicks 1227 } 1229 apsChanStatusCurrent OBJECT-TYPE 1230 SYNTAX BITS { 1231 lockedOut(0), 1232 sd(1), 1233 sf(2), 1234 switched(3) 1235 } 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "Indicates the current state of the port. 1241 lockedOut 1243 This bit, when applied to a working channel, indicates that 1244 the channel is prevented from switching to the protection line. 1245 When applied to the null channel, this bit indicates that no 1246 working channel may switch to the protection line. 1248 sd 1250 A signal degrade condition is in effect. 1252 sf 1254 A signal failure condition is in effect. 1256 switched 1258 The switched bit is applied to a working channel if that 1259 channel is currently switched to the protection line. 1260 " 1261 ::= { apsChanStatusEntry 1 } 1263 apsChanStatusSignalDegrades OBJECT-TYPE 1264 SYNTAX Counter32 1265 MAX-ACCESS read-only 1266 STATUS current 1267 DESCRIPTION 1268 "A count of Signal Degrade conditions. This 1269 condition occurs when the line Bit Error Rate 1270 exceeds the currently configured threshold." 1271 ::= { apsChanStatusEntry 2 } 1273 apsChanStatusSignalFailures OBJECT-TYPE 1274 SYNTAX Counter32 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "A count of Signal Failure conditions that have been 1279 detected on the incoming signal. This condition occurs 1280 when a loss of signal, loss of frame, AIS-L or a Line 1281 bit error rate exceeding 10^-3 is detected on an 1282 incoming line." 1283 ::= { apsChanStatusEntry 3 } 1285 apsChanStatusSwitchovers OBJECT-TYPE 1286 SYNTAX Counter32 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "The number of times this channel has switched to the protection 1291 line. When queried with index value apsChanConfigNumber set to 0, 1292 which is the protection line, this object will return 0." 1293 ::= { apsChanStatusEntry 4 } 1295 apsChanStatusLastSwitchover OBJECT-TYPE 1296 SYNTAX TimeTicks 1297 MAX-ACCESS read-only 1298 STATUS current 1299 DESCRIPTION 1300 "The value of sysUpTime when this channel last completed a switch 1301 to the protection line. If this channel has never switched to the 1302 protection line, or this channel is the protection line, the value 1303 0 will be returned." 1304 ::= { apsChanStatusEntry 5 } 1306 -- 1307 -- APS EVENTS 1308 -- 1310 apsNotificationsPrefix OBJECT IDENTIFIER 1311 ::= { apsMIBNotifications 0 } 1313 apsEventSwitchover NOTIFICATION-TYPE 1314 OBJECTS { apsChanStatusSwitchovers, apsChanStatusCurrent } 1315 STATUS current 1316 DESCRIPTION 1317 "An apsEventSwitchover notification is sent when the 1318 value of an instance of apsChanStatusSwitchovers increments." 1319 ::= { apsNotificationsPrefix 1 } 1321 apsEventModeMismatch NOTIFICATION-TYPE 1322 OBJECTS { apsStatusModeMismatches, apsStatusCurrent } 1323 STATUS current 1324 DESCRIPTION 1325 "An apsEventModeMismatch notification is sent when the 1326 value of an instance of apsStatusModeMismatches increments." 1327 ::= { apsNotificationsPrefix 2 } 1329 apsEventChannelMismatch NOTIFICATION-TYPE 1330 OBJECTS { apsStatusChannelMismatches, apsStatusCurrent } 1331 STATUS current 1332 DESCRIPTION 1333 "An apsEventChannelMismatch notification is sent when the 1334 value of an instance of apsStatusChannelMismatches increments." 1335 ::= { apsNotificationsPrefix 3 } 1337 apsEventPSBF NOTIFICATION-TYPE 1338 OBJECTS { apsStatusPSBFs, apsStatusCurrent } 1339 STATUS current 1340 DESCRIPTION 1341 "An apsEventPSBF notification is sent when the 1342 value of an instance of apsStatusPSBFs increments." 1343 ::= { apsNotificationsPrefix 4 } 1345 apsEventFEPLF NOTIFICATION-TYPE 1346 OBJECTS { apsStatusFEPLFs, apsStatusCurrent } 1347 STATUS current 1348 DESCRIPTION 1349 "An apsEventFEPLFs notification is sent when the 1350 value of an instance of apsStatusFEPLFs increments." 1351 ::= { apsNotificationsPrefix 5 } 1353 -- conformance information 1355 apsGroups OBJECT IDENTIFIER ::= { apsMIBConformance 1 } 1356 apsCompliances OBJECT IDENTIFIER ::= { apsMIBConformance 2 } 1357 apsCompliance MODULE-COMPLIANCE 1358 STATUS current 1359 DESCRIPTION 1360 "The compliance statement for linear APS groups." 1362 MODULE 1363 MANDATORY-GROUPS { apsConfigGeneral, apsStatusGeneral, apsChanGeneral } 1365 OBJECT apsConfigMode 1366 MIN-ACCESS read-only 1367 DESCRIPTION 1368 "Write access is not required." 1370 OBJECT apsConfigRevert 1371 MIN-ACCESS read-only 1372 DESCRIPTION 1373 "Write access is not required." 1375 OBJECT apsConfigDirection 1376 MIN-ACCESS read-only 1377 DESCRIPTION 1378 "Write access is not required." 1380 OBJECT apsConfigExtraTraffic 1381 MIN-ACCESS read-only 1382 DESCRIPTION 1383 "Write access is not required." 1385 OBJECT apsConfigSdBerThreshold 1386 MIN-ACCESS read-only 1387 DESCRIPTION 1388 "Write access is not required." 1390 OBJECT apsConfigSfBerThreshold 1391 MIN-ACCESS read-only 1392 DESCRIPTION 1393 "Write access is not required." 1395 OBJECT apsConfigWaitToRestore 1396 MIN-ACCESS read-only 1397 DESCRIPTION 1398 "Write access is not required." 1400 OBJECT apsConfigRowStatus 1401 MIN-ACCESS read-only 1402 DESCRIPTION 1403 "Write access is not required." 1405 OBJECT apsChanConfigIfIndex 1406 MIN-ACCESS read-only 1407 DESCRIPTION 1408 "Write access is not required." 1410 OBJECT apsChanConfigPriority 1411 MIN-ACCESS read-only 1412 DESCRIPTION 1413 "Write access is not required." 1415 OBJECT apsChanConfigRowStatus 1416 MIN-ACCESS read-only 1417 DESCRIPTION 1418 "Write access is not required." 1420 GROUP apsConfigWtr 1421 DESCRIPTION 1422 "Implementation of this group is optional for all 1423 linear APS implementations. The information is 1424 applicable to groups supporting a configurable 1425 WTR period." 1427 GROUP apsCommandOnePlusOne 1428 DESCRIPTION 1429 "Implementation of this group is optional for all 1430 linear APS implementations. The information is 1431 applicable to groups implementing the linear 1432 APS 1+1 architecture and supporting set operations." 1434 GROUP apsCommandOneToN 1435 DESCRIPTION 1436 "Implementation of this group is optional for all 1437 linear APS implementations. The information is 1438 applicable to groups implementing the linear 1439 APS 1:n architecture and supporting set operations." 1441 GROUP apsChanOneToN 1442 DESCRIPTION 1443 "Implementation of this group is optional for all 1444 linear APS implementations. The information is 1445 applicable to groups implementing the linear 1446 APS 1:n architecture." 1448 GROUP apsTotalsGroup 1449 DESCRIPTION 1450 "Implementation of this group is optional for all 1451 linear APS implementations." 1453 GROUP apsMapGroup 1454 DESCRIPTION 1455 "Implementation of this group is optional for all 1456 linear APS implementations." 1458 ::= { apsCompliances 1 } 1460 -- units of conformance 1462 apsConfigGeneral OBJECT-GROUP 1463 OBJECTS 1464 { 1465 apsConfigMode, 1466 apsConfigRevert, 1467 apsConfigDirection, 1468 apsConfigExtraTraffic, 1469 apsConfigSdBerThreshold, 1470 apsConfigSfBerThreshold, 1471 apsConfigCreationTime, 1472 apsConfigRowStatus 1473 } 1474 STATUS current 1475 DESCRIPTION 1476 "A collection of apsConfigTable objects providing configuration 1477 information applicable to all linear APS groups." 1478 ::= { apsGroups 1 } 1480 apsConfigWtr OBJECT-GROUP 1481 OBJECTS 1482 { 1483 apsConfigWaitToRestore 1484 } 1485 STATUS current 1486 DESCRIPTION 1487 "The apsConfigTable object that provides information which is 1488 applicable to groups supporting a configurable WTR period." 1489 ::= { apsGroups 2 } 1491 -- If set operations are not supported neither of the following two groups 1492 -- are implemented. If sets are supported only one of these groups is 1493 -- implemented for a linear APS group instance. 1495 apsCommandOnePlusOne OBJECT-GROUP 1496 OBJECTS 1497 { 1498 apsCommandSwitch 1499 } 1500 STATUS current 1501 DESCRIPTION 1502 "The apsCommandTable object which is applicable to groups 1503 implementing the linear APS 1+1 architecture. Also, set operations 1504 must be supported." 1505 ::= { apsGroups 3 } 1507 apsCommandOneToN OBJECT-GROUP 1508 OBJECTS 1509 { 1510 apsCommandSwitch, 1511 apsCommandControl 1512 } 1513 STATUS current 1514 DESCRIPTION 1515 "A collection of apsCommandTable objects which are applicable to 1516 groups implementing the linear APS 1:n architecture. Also, set 1517 operations must be supported." 1518 ::= { apsGroups 4 } 1520 apsStatusGeneral OBJECT-GROUP 1521 OBJECTS 1522 { 1523 apsStatusK1K2Rcv, 1524 apsStatusK1K2Trans, 1525 apsStatusCurrent, 1526 apsStatusModeMismatches, 1527 apsStatusChannelMismatches, 1528 apsStatusPSBFs, 1529 apsStatusFEPLFs, 1530 apsStatusSwitchedChannel 1531 } 1532 STATUS current 1533 DESCRIPTION 1534 "A collection of apsStatusTable objects providing status information 1535 applicable to all linear APS groups." 1536 ::= { apsGroups 5 } 1538 apsChanGeneral OBJECT-GROUP 1539 OBJECTS 1540 { 1541 apsChanConfigIfIndex, 1542 apsChanConfigRowStatus, 1543 apsChanStatusCurrent, 1544 apsChanStatusSignalDegrades, 1545 apsChanStatusSignalFailures, 1546 apsChanStatusSwitchovers, 1547 apsChanStatusLastSwitchover 1549 } 1550 STATUS current 1551 DESCRIPTION 1552 "A collection of channel objects providing information applicable to 1553 all linear APS channels." 1554 ::= { apsGroups 6 } 1556 apsChanOneToN OBJECT-GROUP 1557 OBJECTS 1558 { 1559 apsChanConfigPriority 1560 } 1561 STATUS current 1562 DESCRIPTION 1563 "The apsChanConfigTable object that provides information which is only 1564 applicable to groups implementing the linear APS 1:n architecture." 1565 ::= { apsGroups 7 } 1567 apsTotalsGroup OBJECT-GROUP 1568 OBJECTS 1569 { 1570 apsConfigGroups, 1571 apsChanLTEs 1572 } 1573 STATUS current 1574 DESCRIPTION 1575 "A collection of objects providing optional counts of configured APS 1576 groups and SONET LTE interfaces." 1577 ::= { apsGroups 8 } 1579 apsMapGroup OBJECT-GROUP 1580 OBJECTS 1581 { 1582 apsMapGroupName, 1583 apsMapChanNumber 1584 } 1585 STATUS current 1586 DESCRIPTION 1587 "A collection of apsMapTable objects providing a mapping 1588 from sonet(39) InterfaceIndex to group name and channel 1589 number for assigned APS channels and a list of unassigned 1590 sonet(39) interfaces." 1591 ::= { apsGroups 9 } 1593 apsEventOptional NOTIFICATION-GROUP 1594 NOTIFICATIONS {apsEventSwitchover, apsEventModeMismatch, 1595 apsEventChannelMismatch, apsEventPSBF, 1596 apsEventFEPLF } 1597 STATUS current 1598 DESCRIPTION 1599 "A collection of SONET linear APS notifications that may optionally be 1600 implemented." 1601 ::= { apsGroups 10 } 1603 END 1605 6. Intellectual Property 1607 The IETF takes no position regarding the validity or scope of any 1608 intellectual property or other rights that might be claimed to 1609 pertain to the implementation or use of the technology described in 1610 this document or the extent to which any license under such rights 1611 might or might not be available; neither does it represent that it 1612 has made any effort to identify any such rights. Information on the 1613 IETF's procedures with respect to rights in standards-track and 1614 standards-related documentation can be found in BCP-11. Copies of 1615 claims of rights made available for publication and any assurances of 1616 licenses to be made available, or the result of an attempt made to 1617 obtain a general license or permission for the use of such 1618 proprietary rights by implementors or users of this specification can 1619 be obtained from the IETF Secretariat. 1621 7. Acknowledgments 1623 This document is a product of the AToMMIB Working Group. A number of 1624 constructs from a separate draft submission by Ken Chapman have been 1625 included here. Additionally, suggestions by Orly Nicklass, Faye Ly, 1626 Ron Carmona, Kaj Tesink and C. M. Heard have been incorporated, and a 1627 quality review was provided by Lauren Heintz. 1629 8. References 1631 [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for 1632 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1634 [2] Rose, M. and K. McCloghrie, "Structure and Identification of 1635 Management Information for TCP/IP-based Internets", STD 16, RFC 1636 1155, May 1990. 1638 [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, 1639 RFC 1212, March 1991. 1641 [4] Rose, M., "A Convention for Defining Traps for use with the 1642 SNMP", RFC 1215, March 1991. 1644 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1645 M. and S. Waldbusser, "Structure of Management Information 1646 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1648 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1649 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 1650 58, RFC 2579, April 1999. 1652 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1653 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 1654 58, RFC 2580, April 1999. 1656 [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 1657 Network Management Protocol", STD 15, RFC 1157, May 1990. 1659 [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1660 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1662 [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1663 "Transport Mappings for Version 2 of the Simple Network 1664 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1666 [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1667 Processing and Dispatching for the Simple Network Management 1668 Protocol (SNMP)", RFC 2572, April 1999. 1670 [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) 1671 for version 3 of the Simple Network Management Protocol 1672 (SNMPv3)", RFC 2574, April 1999. 1674 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol 1675 Operations for Version 2 of the Simple Network Management 1676 Protocol (SNMPv2)", RFC 1905, January 1996. 1678 [14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 1679 2573, April 1999. 1681 [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1682 Control Model (VACM) for the Simple Network Management Protocol 1683 (SNMP)", RFC 2575, April 1999. 1685 [16] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction 1686 to Version 3 of the Internet-standard Network Management 1687 Framework", RFC 2570, April 1999. 1689 [17] McCloghrie, K., and F. Kastenholz. "The Interfaces Group MIB", 1690 RFC 2863, June 2000. 1692 [18] GR-253-CORE Issue 2, December 1995, Revision 2, January 1999 1694 [19] ITU-T Recommendation G.783 (04/97) 1696 [20] K. Chapman, "Definitions of Managed Objects for SONET Linear 1697 Automatic Protection Switching (APS)", 1698 draft-kchapman-sonet-aps-00.txt, July 1999 1700 9.Security Considerations 1702 There are a number of management objects defined in this MIB 1703 that have a MAX-ACCESS clause of read-write and/or read-create. 1704 Such objects may be considered sensitive or vulnerable in some 1705 network environments. The support for SET operations in a 1706 non-secure environment without proper protection can have a 1707 negative effect on network operations. 1709 SNMPv1 by itself is not a secure environment. Even if the 1710 network itself is secure (for example by using IPSec), even then, 1711 there is no control as to who on the secure network is allowed 1712 to access and GET/SET (read/change/create/delete) the objects in 1713 this MIB. 1715 It is recommended that the implementers consider the security 1716 features as provided by the SNMPv3 framework. Specifically, the 1717 use of the User-based Security Model RFC 2574 [RFC2574] and the 1718 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1720 It is then a customer/user responsibility to ensure that the SNMP 1721 entity giving access to an instance of this MIB, is properly 1722 configured to give access to the objects only to those 1723 principals (users) that have legitimate rights to indeed GET or 1724 SET (change/create/delete) them. 1726 10. Editor's Address 1728 Jeff Johnson 1729 RedBack Networks. Inc. 1730 350 Holger Way 1731 San Jose, CA 95134-1362 1732 Phone: +1 408 571 5460 1733 Email: jeff@redback.com 1735 Michael Thatcher 1736 RedBack Networks. Inc. 1737 350 Holger Way 1738 San Jose, CA 95134-1362 1739 Phone: +1 408 571 5449 1740 Email: thatcher@redback.com 1742 Jim Kuhfeld 1743 RedBack Networks. Inc. 1744 350 Holger Way 1745 San Jose, CA 95134-1362 1746 Phone: +1 408 571 5465 1747 Email: jkuhfeld@redback.com 1749 11 Changes since draft-ietf-atommib-sonetaps-mib-03.txt 1751 The description of apsChanLTEs and apsMapEntry were updated. 1753 The syntax, description and conformance information regarding 1754 apsConfigWaitToRestore were updated to incorporate shorter wait to 1755 restore periods and the use of this parameter as defined in G.783. 1757 12. Full Copyright Statement 1759 Copyright (C) The Internet Society (1999). All Rights Reserved. 1761 This document and translations of it may be copied and furnished 1762 to others, and derivative works that comment on or otherwise 1763 explain it or assist in its implmentation may be prepared, copied, 1764 published and distributed, in whole or in part, without 1765 restriction of any kind, provided that the above copyright notice 1766 and this paragraph are included on all such copies and derivative 1767 works. However, this document itself may not be modified in any 1768 way, such as by removing the copyright notice or references to the 1769 Internet Society or other Internet organizations, except as needed 1770 for the purpose of developing Internet standards in which case the 1771 procedures for copyrights defined in the Internet Standards 1772 process must be followed, or as required to translate it into 1773 languages other than English. 1775 The limited permissions granted above are perpetual and will not 1776 be revoked by the Internet Society or its successors or assigns. 1778 This document and the information contained herein is provided on 1779 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 1780 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 1781 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 1782 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1783 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 1784 PURPOSE."