idnits 2.17.1 draft-ietf-atommib-sonetaps-mib-06.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 90 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 960 has weird spacing: '... has an ifTyp...' == Line 964 has weird spacing: '... has an ifTyp...' == Line 983 has weird spacing: '... has an ifTyp...' == Line 986 has weird spacing: '... has an ifTyp...' == Line 1080 has weird spacing: '...set the corre...' == (7 more instances...) -- 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 (March 18, 2002) is 8065 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 57 -- Looks like a reference, but probably isn't: 'RFC1155' on line 62 -- Looks like a reference, but probably isn't: 'RFC1212' on line 62 -- Looks like a reference, but probably isn't: 'RFC1215' on line 63 -- Looks like a reference, but probably isn't: 'RFC2578' on line 64 -- Looks like a reference, but probably isn't: 'RFC2579' on line 64 -- Looks like a reference, but probably isn't: 'RFC2580' on line 65 -- Looks like a reference, but probably isn't: 'RFC1157' on line 78 -- Looks like a reference, but probably isn't: 'RFC1901' on line 72 -- Looks like a reference, but probably isn't: 'RFC1906' on line 74 -- Looks like a reference, but probably isn't: 'RFC2572' on line 74 -- Looks like a reference, but probably isn't: 'RFC2574' on line 1986 -- Looks like a reference, but probably isn't: 'RFC1905' on line 80 -- Looks like a reference, but probably isn't: 'RFC2573' on line 83 -- Looks like a reference, but probably isn't: 'RFC2575' on line 1987 -- Looks like a reference, but probably isn't: 'RFC2570' on line 87 == Unused Reference: '1' is defined on line 1892, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 1895, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 1899, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1902, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 1905, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 1909, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1913, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 1917, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1920, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1923, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 1927, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 1931, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 1935, but no explicit reference was found in the text == Unused Reference: '14' is defined on line 1939, but no explicit reference was found in the text == Unused Reference: '15' is defined on line 1942, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 1946, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 1950, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1953, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1955, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1957, 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 (~~), 29 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 September 18, 2002 M. Thatcher 4 J. Kuhfeld 5 Redback Networks 6 March 18, 2002 8 Definitions of Managed Objects 9 for SONET Linear APS architectures 11 draft-ietf-atommib-sonetaps-mib-06.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 2002. 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 1. Introduction 47 This memo defines a portion of the Management Information Base (MIB) 48 used for managing SONET linear Automatic Protection Switching (APS) 49 architectures. Two linear APS architectures are supported, the 1+1 50 architecture and the 1:n architecture. 52 2. The SNMP Management Framework 54 The SNMP Management Framework presently consists of five major 55 components: 57 An overall architecture, described in RFC 2571 [RFC2571]. 59 Mechanisms for describing and naming objects and events for the 60 purpose of management. The first version of this Structure of 61 Management Information (SMI) is called SMIv1 and described in 62 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 63 1215 [RFC1215]. The second version, called SMIv2, is described 64 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 65 STD 58, RFC 2580 [RFC2580]. 67 Message protocols for transferring management information. The 68 first version of the SNMP message protocol is called SNMPv1 and 69 described in STD 15, RFC 1157 [RFC1157]. A second version of 70 the SNMP message protocol, which is not an Internet standards 71 track protocol, is called SNMPv2c and described in RFC 1901 72 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 73 message protocol is called SNMPv3 and described in RFC 1906 74 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 76 Protocol operations for accessing management information. The 77 first set of protocol operations and associated PDU formats is 78 described in STD 15, RFC 1157 [RFC1157]. A second set of 79 protocol operations and associated PDU formats is described in 80 RFC 1905 [RFC1905]. 82 A set of fundamental applications described in RFC 2573 83 [RFC2573] and the view-based access control mechanism described 84 in RFC 2575 [RFC2575]. 86 A more detailed introduction to the current SNMP Management Framework 87 can be found in RFC 2570 [RFC2570]. 89 Managed objects are accessed via a virtual information store, termed 90 the Management Information Base or MIB. Objects in the MIB are 91 defined using the mechanisms defined in the SMI. 93 This memo specifies a MIB module that is compliant to the SMIv2. A 94 MIB conforming to the SMIv1 can be produced through the appropriate 95 translations. The resulting translated MIB must be semantically 96 equivalent, except where objects or events are omitted because no 97 translation is possible (use of Counter64). Some machine readable 98 information in SMIv2 will be converted into textual descriptions in 99 SMIv1 during the translation process. However, this loss of machine 100 readable information is not considered to change the semantics of the 101 MIB. 103 3. Overview 105 These objects are used to control and manage SONET linear APS 106 architectures. Ring APS groups are not currently supported by this 107 MIB. 109 The MIB includes three scalars, containing counts of APS groups and 110 SONET LTEs, a notification enable object, and six tables. 112 The apsMapTable contains entries for each SONET LTE interface 113 available on the system. The table serves two purposes. It can be 114 used to locate SONET LTE interfaces that are not currently included 115 in APS groups. It also provides a mapping from InterfaceIndex to 116 group name and channel number for those SONET LTE interfaces that are 117 included in APS groups. Entries in apsMapTable cannot be added or 118 deleted through operations defined in this MIB. However, an 119 apsMapEntry may be added or deleted through other system mechanisms, 120 such as hot swap. Also, existing entries cannot be directly modified 121 and instead, such modifications occur as a result of side-effects of 122 operations on the apsChanConfigTable. 124 The apsChanConfigTable supports addition, modification and deletion 125 of entries representing linear APS channels. Entries are indexed by 126 a text group name and integer channel number. Each entry contains an 127 InterfaceIndex value identifying the SONET LTE used for the channel 128 and the priority of the channel. A side effect of row creation or 129 deletion is the setting of map entry fields. Creation of 2-14 entries 130 in this table with a common group name index and consecutive channel 131 numbers beginning with zero is the first step in the creation and 132 configuration of an APS group. It is not necessary to create channel 133 numbers in order, however the resulting set of channels must begin 134 with channel number 0 and must be consecutive. However, if the 135 onePlusOneOptimized architecture is selected, the set of channel 136 numbers begins with 1 instead of 0. Note that the term null channel, 137 which is used throughout this document refers to the protection line. 139 The apsConfigTable supports addition, modification and deletion of 140 entries representing linear APS groups. Entries are indexed by a text 141 group name. Each entry contains parameters that specify the 142 configuration of a particular linear APS group. Entries are created 143 in this table after a set of channels are created in the 144 apsChanConfigTable. In order to successfully set an instance of 145 apsConfigRowStatus to active the apsConfigEntry must contain valid 146 values and all associated apsChanConfigEntry rows must be valid and 147 produce a consecutive set of channels beginning with channel number 0 148 or 1, depending on the selected architecture. 150 The apsCommandTable provides linear APS commands that support 151 protection switching and the ability to modify APS operation. 152 Entries in this table are created as a side effect of setting the 153 associated apsConfigRowStatus object to active. Entries in this table 154 are deleted if the associated apsConfigRowStatus object is set to any 155 value except active. 157 The apsChanStatusTable provides individual channel statistics. 159 The apsStatusTable provides group level statistics. 161 An APS group is created and configured with the following sequence of 162 events: 164 CHANNEL CONFIGURATION 166 Create an entry in the apsChanConfigTable. Set the 167 apsChanConfigGroupName in an apsChanConfigEntry to a user-friendly 168 text string which will serve as the APS group name. The string must 169 not be equal to the apsConfigName of an existing apsConfigEntry with 170 apsConfigRowStatus set to active, since a channel cannot be added to 171 an active group. The string may be set equal to the apsConfigName of 172 a row which is currently not set to active, or it may be set to a 173 string which does not currently exist in any instance of 174 apsConfigName. A channel number is entered in apsChanConfigNumber. 175 A channel priority is entered in apsChanConfigPriority, if the 176 intended architecture is 1:n. apsChanConfigPriority is ignored if the 177 architecture is 1+1. The InterfaceIndex value of a SONET LTE 178 interface is entered in apsChanConfigIfIndex. 180 This step is repeated for all apsChanConfigEntry instances which are 181 to be included in the APS group. 183 ACTIVATING THE GROUP 185 If the apsChanConfigGroupName does not exist in an instance of 186 apsConfigName, an apsConfigEntry is created with the 187 apsChanConfigGroupName value used as the index for the row. The 188 apsConfigRowStatus value may be set to createAndGo. The 189 apsGroupConfigEntry and apsChanConfigEntry instances with matching 190 name fields will be checked for consistency. If any errors in the 191 channel numbers, architecture or configuration are uncovered the 192 apsConfigRowStatus set will return inconsistentValue, otherwise 193 noError is returned. 195 If the apsChanConfigGroupName value used in channel configuration 196 exists in a previously created, inactive apsConfigEntry instance, the 197 apsConfigRowStatus value may be set to active. 199 An agent is not required to process SNMP Set Requests that affect 200 multiple control objects within this MIB. This is intended to 201 simplify the processing of Set Requests for the various control 202 tables by eliminating the possibility that a single Set PDU will 203 contain multiple varbinds which are in conflict, such as a PDU which 204 both activates a given apsConfigEntry while at the same time it 205 deactivates an associated apsChanConfigEntry. 207 4. Definitions 209 APS-MIB DEFINITIONS ::= BEGIN 211 IMPORTS 212 MODULE-IDENTITY, NOTIFICATION-TYPE, 213 OBJECT-TYPE, 214 Gauge32, Counter32, Integer32, 215 transmission 216 FROM SNMPv2-SMI 218 TEXTUAL-CONVENTION, RowStatus, 219 TimeStamp, StorageType 220 FROM SNMPv2-TC 222 SnmpAdminString 223 FROM SNMP-FRAMEWORK-MIB 225 ifIndex, InterfaceIndex 226 FROM IF-MIB 228 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 229 FROM SNMPv2-CONF; 231 apsMIB MODULE-IDENTITY 232 LAST-UPDATED "200203182300Z" -- March 18, 2002 233 ORGANIZATION "IETF AToMMIB Working Group" 234 CONTACT-INFO 235 " Jeff Johnson 236 Postal: RedBack Networks. Inc. 237 300 Holger Way 238 San Jose, CA 95134-1362 239 Tel: +1 408 750 5460 240 Email: jeff@redback.com 242 Michael Thatcher 243 Postal: RedBack Networks. Inc. 244 300 Holger Way 245 San Jose, CA 95134-1362 246 Tel: +1 408 750 5449 247 Email: thatcher@redback.com 249 Jim Kuhfeld 250 Postal: RedBack Networks. Inc. 251 300 Holger Way 252 San Jose, CA 95134-1362 253 Tel: +1 408 750 5465 254 Email: jkuhfeld@redback.com" 255 DESCRIPTION 256 "This management information module supports the configuration and 257 management of SONET linear APS groups. The definitions and 258 descriptions used in this MIB have been derived from 259 Synchronous Optical Network (SONET) Transport Systems: 260 Common Generic Criteria, GR-253-CORE Revision 2, January 1999, 261 section 5.3. The MIB is also consistent with the Multiplex 262 Section Protection (MSP) protocol as specified in ITU-T 263 Recommendation G.783, Characteristics of synchronous digital 264 hierarchy (SDH) equipment function blocks, Annex A and B. 265 " 267 REVISION "200203182300Z" -- March 18, 2002 268 DESCRIPTION 269 "Initial version of this MIB, published as RFC xxxx." 270 -- xxxx to be assigned by RFC-Editor 271 ::= { transmission XX } 272 -- assign XX 273 -- remove this notice from the MIB 275 apsMIBObjects OBJECT IDENTIFIER 276 ::= { apsMIB 1 } 278 apsMIBNotifications OBJECT IDENTIFIER 279 ::= { apsMIB 2 } 281 apsMIBConformance OBJECT IDENTIFIER 282 ::= { apsMIB 3 } 284 ApsK1K2 ::= TEXTUAL-CONVENTION 285 STATUS current 286 DESCRIPTION 287 "This Textual Convention describes an object that stores 288 a SONET K1 and K2 byte APS protocol field. 290 K1 is located in the first octet, K2 is located in 291 the second octet. Bits are numbered from left to right. 293 Bits 1-4 of the K1 byte indicate a request. 295 1111 Lockout of Protection 296 1110 Forced Switch 297 1101 SF - High Priority 298 1100 SF - Low Priority 299 1011 SD - High Priority 300 1010 SD - Low Priority 301 1001 not used 302 1000 Manual Switch 303 0111 not used 304 0110 Wait-to-Restore 305 0101 not used 306 0100 Exercise 307 0011 not used 308 0010 Reverse Request 309 0001 Do Not Revert 310 0000 No Request 312 Bits 5-8 of the K1 byte indicate the channel associated with the 313 request defined in bits 1-4. 315 0000 is the Null channel. 317 1-14 are working channels. 318 15 is the extra traffic channel 320 Bits 1-4 of the K2 byte indicate a channel. The channel is 321 defined with the same syntax as K1 Bits 5-8. 323 Bit 5 of the K2 byte indicates the 324 architecture. 326 0 if the architecture is 1+1 327 1 if the architecture is 1:n 329 Bits 6-8 of the K2 byte indicates the 330 mode. 332 000 - 011 are reserved for future use 334 100 indicates the mode is unidirectional 335 101 indicates the mode is bidirectional 337 110 RDI-L 339 111 AIS-L 340 " 341 REFERENCE 342 "Bellcore (Telcordia Technologies) GR-253-CORE, Issue 2, 343 Revision 2 (January 1999), 5.3.5." 344 SYNTAX OCTET STRING (SIZE (2)) 346 ApsSwitchCommand ::= TEXTUAL-CONVENTION 347 STATUS current 348 DESCRIPTION 349 "An APS switch command allows a user to perform protection 350 switch actions. 352 The Switch command values are: 354 noCmd 356 This value should be returned by a read request when no switch 357 command has been written to the object in question since 358 initialization. This value may not be used in a write operation. 360 clear 362 Clears all of the switch commands listed below for the specified 363 channel. 365 lockoutOfProtection 367 Prevents any of the working channels from switching to the protection 368 line. The specified channel should be the protection channel. 370 forcedSwitchWorkToProtect 372 Switches the specified working channel to the protection line. 374 forcedSwitchProtectToWork 376 Switches the working channel back from the protection 377 line to the working line. The specified channel should be 378 the protection channel. 380 manualSwitchWorkToProtect 382 Switches the specified working channel to the protection line. 384 manualSwitchProtectToWork 386 Switches the working channel back from the protection 387 line to the working line. The specified channel should be 388 the protection channel. 390 exercise 392 Exercises the protocol for a protection switch of the specified 393 channel by issuing an Exercise request for that channel and 394 checking the response on the APS channel. 395 " 396 SYNTAX INTEGER { 397 noCmd(1), 398 clear(2), 399 lockoutOfProtection(3), 400 forcedSwitchWorkToProtect(4), 401 forcedSwitchProtectToWork(5), 402 manualSwitchWorkToProtect(6), 403 manualSwitchProtectToWork(7), 404 exercise(8) 405 } 407 ApsControlCommand ::= TEXTUAL-CONVENTION 408 STATUS current 409 DESCRIPTION 410 "An APS control command applies only to LTE that support the 411 1:n architecture and performs the following actions. 413 The Control command values are: 415 noCmd 417 This value should be returned by a read request when no control 418 command has been written to the object in question since 419 initialization. This value may not be used in a write operation. 421 lockoutWorkingChannel 423 Prevents the specified working channel from switching to the protection 424 line. 426 clearLockoutWorkingChannel 428 Clears the lockout a working channel command for the channel specified. 429 " 430 SYNTAX INTEGER { 431 noCmd(1), 432 lockoutWorkingChannel(2), 433 clearLockoutWorkingChannel(3) 434 } 436 -- 437 -- APS Configuration Table 438 -- 439 -- This table supports the addition, configuration and deletion of APS 440 -- groups. 441 -- 443 apsConfig OBJECT IDENTIFIER ::= { apsMIBObjects 1 } 445 apsConfigGroups OBJECT-TYPE 446 SYNTAX Gauge32 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The count of APS groups. This count includes all rows in 451 apsConfigTable, regardless of the value of apsConfigRowStatus." 452 ::= { apsConfig 1 } 454 apsConfigTable OBJECT-TYPE 455 SYNTAX SEQUENCE OF ApsConfigEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "This table lists the APS groups that have been configured 460 on the system." 461 ::= { apsConfig 2 } 463 apsConfigEntry OBJECT-TYPE 464 SYNTAX ApsConfigEntry 465 MAX-ACCESS not-accessible 466 STATUS current 467 DESCRIPTION 468 "A conceptual row in the apsConfigTable." 469 INDEX { IMPLIED apsConfigName } 470 ::= { apsConfigTable 1 } 472 ApsConfigEntry ::= SEQUENCE { 473 apsConfigName SnmpAdminString, 474 apsConfigRowStatus RowStatus, 475 apsConfigMode INTEGER, 476 apsConfigRevert INTEGER, 477 apsConfigDirection INTEGER, 478 apsConfigExtraTraffic INTEGER, 479 apsConfigSdBerThreshold Integer32, 480 apsConfigSfBerThreshold Integer32, 481 apsConfigWaitToRestore Integer32, 482 apsConfigCreationTime TimeStamp, 483 apsConfigStorageType StorageType 484 } 486 apsConfigName OBJECT-TYPE 487 SYNTAX SnmpAdminString (SIZE (1..32)) 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "A textual name for the APS group. 492 " 493 ::= { apsConfigEntry 1 } 495 apsConfigRowStatus OBJECT-TYPE 496 SYNTAX RowStatus 497 MAX-ACCESS read-create 498 STATUS current 499 DESCRIPTION 500 "The status of this APS group entry. 502 An entry may not exist in the active state unless all 503 objects in the entry have an appropriate value. Also, 504 all associated apsChanConfigEntry rows must represent 505 a set of consecutive channel numbers beginning with 506 0 or 1, depending on the selected architecture. 508 When set to notInService changes may be made to apsConfigMode, 509 apsConfigRevert, apsConfigDirection, apsConfigExtraTraffic, 510 apsConfigSdBerThreshold, apsConfigSfBerThreshold, 511 and apsConfigWaitToRestore. Also, associated apsChanConfigTable 512 objects may be added, deleted and modified. 513 " 515 ::= { apsConfigEntry 2 } 517 apsConfigMode OBJECT-TYPE 518 SYNTAX INTEGER { 519 onePlusOne(1), 520 oneToN(2), 521 onePlusOneCompatible(3), 522 onePlusOneOptimized(4) 523 } 524 MAX-ACCESS read-create 525 STATUS current 526 DESCRIPTION 527 "The architecture of the APS group. 529 onePlusOne 531 The 1+1 architecture permanently bridges the working 532 line to the protection line. 534 oneToN 536 The 1:n architecture allows one protection channel to 537 protect up to n working channels. When a fault is detected 538 on one of the n working channels that channel is bridged 539 over the protection channel. 541 onePlusOneCompatible 543 This refers to 1 + 1 bidirectional switching compatible with 544 1:n bidirectional switching as specified in ITU-T 545 Recommendation G.783 (04/97) section A.3.4.1. Since this 546 mode necessitates bidirectional switching, apsConfigDirection 547 must be set to bidirectional whenever onePlusOneCompatible is set. 549 onePlusOneOptimized 551 This refers to 1 + 1 bidirectional switching optimized 552 for a network using predominantly 1 + 1 bidirectional 553 switching as specified in ITU-T Recommendation G.783 (04/97) 554 section B.1. Since this mode necessitates bidirectional 555 switching, apsConfigDirection must be set to bidirectional 556 whenever onePlusOneOptimized is set. 558 This object may not be modified if the associated 559 apsConfigRowStatus object is equal to active(1)." 560 DEFVAL {onePlusOne} 561 ::= { apsConfigEntry 3 } 563 apsConfigRevert OBJECT-TYPE 564 SYNTAX INTEGER { nonrevertive(1), revertive(2) } 565 MAX-ACCESS read-create 566 STATUS current 567 DESCRIPTION 568 "The revertive mode of the APS group. 570 nonrevertive 572 Traffic remains on the protection line until another switch 573 request is received. 575 revertive 577 When the condition that caused a switch to the protection 578 line has been cleared the signal is switched back to the 579 working line. Since switching is revertive with the 1:n 580 architecture, apsConfigRevert must be set to revertive if 581 apsConfigMode is set to oneToN. 583 Switching may optionally be revertive with the 1+1 architecture. 585 This object may not be modified if the associated 586 apsConfigRowStatus object is equal to active(1). 587 " 588 DEFVAL { nonrevertive } 589 ::= { apsConfigEntry 4 } 591 apsConfigDirection OBJECT-TYPE 592 SYNTAX INTEGER { unidirectional(1), bidirectional(2) } 593 MAX-ACCESS read-create 594 STATUS current 595 DESCRIPTION 596 "The directional mode of the APS group. 598 unidirectional 600 The unidirectional mode provides protection in one direction. 602 bidirectional 604 The bidirectional mode provides protection in both 605 directions. 607 This object may not be modified if the associated 608 apsConfigRowStatus object is equal to active(1). 610 " 611 DEFVAL {unidirectional} 612 ::= { apsConfigEntry 5 } 614 apsConfigExtraTraffic OBJECT-TYPE 615 SYNTAX INTEGER { enabled(1), disabled(2) } 616 MAX-ACCESS read-create 617 STATUS current 618 DESCRIPTION 619 "This object enables or disables the transfer of extra traffic 620 on the protection channel in a 1:n architecture. This object 621 must be set to disabled if the architecture is 1+1. It may be 622 necessary to disable this in order to interwork with other SONET 623 network elements that don't support extra traffic. 625 This object may not be modified if the associated 626 apsConfigRowStatus object is equal to active(1). 627 " 628 DEFVAL { disabled } 629 ::= { apsConfigEntry 6 } 631 apsConfigSdBerThreshold OBJECT-TYPE 632 SYNTAX Integer32 (5..9) 633 MAX-ACCESS read-create 634 STATUS current 635 DESCRIPTION 636 "The Signal Degrade Bit Error Rate. 638 The negated value of this number is used as the exponent of 639 10 for computing the threshold value for the Bit Error Rate 640 (BER). For example, a value of 5 indicates a BER threshold of 641 10^-5. 643 This object may be modified if the associated 644 apsConfigRowStatus object is equal to active(1)." 645 DEFVAL { 5 } 646 ::= { apsConfigEntry 7 } 648 apsConfigSfBerThreshold OBJECT-TYPE 649 SYNTAX Integer32 (3..5) 650 MAX-ACCESS read-create 651 STATUS current 652 DESCRIPTION 653 "The Signal Failure 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 { 3 } 663 ::= { apsConfigEntry 8 } 665 apsConfigWaitToRestore OBJECT-TYPE 666 SYNTAX Integer32 (0..720) 667 UNITS "seconds" 668 MAX-ACCESS read-create 669 STATUS current 670 DESCRIPTION 671 "The Wait To Restore period in seconds. 673 After clearing of a condition that necessitated an 674 automatic switch, the wait to restore period must elapse 675 before reverting. This is intended to avoid rapid switch 676 oscillations. 678 GR-253-CORE specifies a Wait To Restore range of 5 to 12 679 minutes. G.783 defines a 5 to 12 minute Wait To Restore 680 range in section 5.4.1.1.3, but also allows for a shorter 681 WTR period in Table 2-1, 682 WaitToRestore value (MI_WTRtime: 0..(5)..12 minutes). 684 This object may not be modified if the associated 685 apsConfigRowStatus object is equal to active(1)." 686 DEFVAL { 300 } 687 ::= { apsConfigEntry 9 } 689 apsConfigCreationTime OBJECT-TYPE 690 SYNTAX TimeStamp 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "The value of sysUpTime at the time the row was 695 created" 696 ::= { apsConfigEntry 10 } 698 apsConfigStorageType OBJECT-TYPE 699 SYNTAX StorageType 700 MAX-ACCESS read-create 701 STATUS current 702 DESCRIPTION 703 "The storage type for this conceptual row. 704 Conceptual rows having the value 'permanent' need not 705 allow write-access to any columnar objects in the row." 706 DEFVAL { nonVolatile } 707 ::= { apsConfigEntry 11 } 709 -- 710 -- APS Status Table 711 -- 712 -- This table provides APS group statistics. 713 -- 715 apsStatusTable OBJECT-TYPE 716 SYNTAX SEQUENCE OF ApsStatusEntry 717 MAX-ACCESS not-accessible 718 STATUS current 719 DESCRIPTION 720 "This table provides status information about APS groups that have 721 been configured on the system." 722 ::= { apsMIBObjects 2 } 724 apsStatusEntry OBJECT-TYPE 725 SYNTAX ApsStatusEntry 726 MAX-ACCESS not-accessible 727 STATUS current 728 DESCRIPTION 729 "A conceptual row in the apsStatusTable." 730 AUGMENTS { apsConfigEntry } 731 ::= { apsStatusTable 1 } 733 ApsStatusEntry ::= SEQUENCE { 734 apsStatusK1K2Rcv ApsK1K2, 735 apsStatusK1K2Trans ApsK1K2, 736 apsStatusCurrent BITS, 737 apsStatusModeMismatches Counter32, 738 apsStatusChannelMismatches Counter32, 739 apsStatusPSBFs Counter32, 740 apsStatusFEPLFs Counter32, 741 apsStatusSwitchedChannel Integer32, 742 apsStatusDiscontinuityTime TimeStamp 743 } 745 apsStatusK1K2Rcv OBJECT-TYPE 746 SYNTAX ApsK1K2 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The current value of the K1 and K2 bytes received on the 751 protection channel." 752 ::= { apsStatusEntry 1 } 754 apsStatusK1K2Trans OBJECT-TYPE 755 SYNTAX ApsK1K2 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "The current value of the K1 and K2 bytes transmitted on the 760 protection channel." 761 ::= { apsStatusEntry 2 } 763 apsStatusCurrent OBJECT-TYPE 764 SYNTAX BITS { 765 modeMismatch(0), 766 channelMismatch(1), 767 psbf(2), 768 feplf(3), 769 extraTraffic(4) 770 } 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "The current status of the APS group. 776 modeMismatch 778 Modes other than 1+1 unidirectional monitor protection line 779 K2 bit 5, which indicates the architecture and K2 bits 780 6-8, which indicate if the mode is unidirectional or 781 bidirectional. A conflict between the current local mode 782 and the received K2 mode information constitutes a 783 mode mismatch. 785 channelMismatch 787 This bit indicates a mismatch between the transmitted K1 channel 788 and the received K2 channel has been detected. 790 psbf 792 This bit indicates a Protection Switch Byte Failure (PSBF) is 793 in effect. This condition occurs when either an inconsistent 794 APS byte or an invalid code is detected. An inconsistent APS 795 byte occurs when no three consecutive K1 bytes of the last 12 796 successive frames are identical, starting with the last frame 797 containing a previously consistent byte. An invalid code occurs 798 when the incoming K1 byte contains an unused code or a code 799 irrelevant for the specific switching operation (e.g., Reverse 800 Request while no switching request is outstanding) in three 801 consecutive frames. An invalid code also occurs when the incoming 802 K1 byte contains an invalid channel number in three consecutive 803 frames. 805 feplf 807 Modes other than 1+1 unidirectional monitor the K1 byte 808 for Far-End Protection-Line failures. A Far-End 809 Protection-Line defect is declared based on receiving 810 SF on the protection line. 812 extraTraffic 814 This bit indicates whether extra traffic is currently being 815 accepted on the protection line. 816 " 817 ::= { apsStatusEntry 3 } 819 apsStatusModeMismatches OBJECT-TYPE 820 SYNTAX Counter32 821 MAX-ACCESS read-only 822 STATUS current 823 DESCRIPTION 824 "A count of Mode Mismatch conditions. 826 Discontinuities in the value of this counter can occur at 827 re-initialization of the management system, and at other 828 times as indicated by the value of 829 apsStatusDiscontinuityTime." 830 ::= { apsStatusEntry 4 } 832 apsStatusChannelMismatches OBJECT-TYPE 833 SYNTAX Counter32 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "A count of Channel Mismatch conditions. 839 Discontinuities in the value of this counter can occur at 840 re-initialization of the management system, and at other 841 times as indicated by the value of 842 apsStatusDiscontinuityTime." 843 ::= { apsStatusEntry 5 } 845 apsStatusPSBFs OBJECT-TYPE 846 SYNTAX Counter32 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "A count of Protection Switch Byte Failure conditions. 851 This condition occurs when either an inconsistent APS 852 byte or an invalid code is detected. An inconsistent APS 853 byte occurs when no three consecutive K1 bytes of the last 854 12 successive frames are identical, starting with the last 855 frame containing a previously consistent byte. An invalid 856 code occurs when the incoming K1 byte contains an unused 857 code or a code irrelevant for the specific switching operation 858 (e.g., Reverse Request while no switching request is outstanding) 859 in three consecutive frames. An invalid code also occurs 860 when the incoming K1 byte contains an invalid channel number 861 in three consecutive frames. 863 Discontinuities in the value of this counter can occur at 864 re-initialization of the management system, and at other 865 times as indicated by the value of 866 apsStatusDiscontinuityTime." 867 ::= { apsStatusEntry 6 } 869 apsStatusFEPLFs OBJECT-TYPE 870 SYNTAX Counter32 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "A count of Far-End Protection-Line Failure conditions. 875 This condition is declared based on receiving SF on 876 the protection line in the K1 byte. 878 Discontinuities in the value of this counter can occur at 879 re-initialization of the management system, and at other 880 times as indicated by the value of 881 apsStatusDiscontinuityTime." 882 ::= { apsStatusEntry 7 } 884 apsStatusSwitchedChannel OBJECT-TYPE 885 SYNTAX Integer32 886 MAX-ACCESS read-only 887 STATUS current 888 DESCRIPTION 889 "This field is set to the number of the channel that is currently 890 switched to protection. The value 0 indicates no channel is 891 switched to protection. The values 1-14 indicate that working 892 channel is switched to protection." 893 ::= { apsStatusEntry 8 } 895 apsStatusDiscontinuityTime OBJECT-TYPE 896 SYNTAX TimeStamp 897 MAX-ACCESS read-only 898 STATUS current 899 DESCRIPTION 900 "The value of sysUpTime on the most recent occasion at which 901 any one or more of this APS group's counters suffered a 902 discontinuity. The relevant counters are the specific 903 instances associated with this APS group of any Counter32 904 object contained in apsStatusTable. If no such 905 discontinuities have occurred since the last re-initialization 906 of the local management subsystem, then this object contains 907 a zero value." 908 ::= { apsStatusEntry 9 } 910 -- 911 -- APS Map Group 912 -- 913 -- Lists the SONET LTE interfaces that may be used to create APS groups. 914 -- 916 apsMap OBJECT IDENTIFIER ::= { apsMIBObjects 3 } 918 apsChanLTEs OBJECT-TYPE 919 SYNTAX Gauge32 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "The count of SONET LTE interfaces on the system. 924 Each interface that is included has an ifType value of sonet(39)." 925 ::= { apsMap 1 } 927 apsMapTable OBJECT-TYPE 928 SYNTAX SEQUENCE OF ApsMapEntry 929 MAX-ACCESS not-accessible 930 STATUS current 931 DESCRIPTION 932 "This table lists the SONET LTE interfaces on the system. 933 Each interface that is listed has an ifType value of sonet(39)." 934 ::= { apsMap 2 } 936 apsMapEntry OBJECT-TYPE 937 SYNTAX ApsMapEntry 938 MAX-ACCESS not-accessible 939 STATUS current 940 DESCRIPTION 941 "A conceptual row in the apsMapTable." 942 INDEX { ifIndex } 943 ::= { apsMapTable 1 } 945 ApsMapEntry ::= SEQUENCE { 946 apsMapGroupName SnmpAdminString, 947 apsMapChanNumber Integer32 948 } 950 apsMapGroupName OBJECT-TYPE 951 SYNTAX SnmpAdminString (SIZE (0..32)) 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "A textual name for the APS group which this channel is 956 included in. If the channel is not part of an APS group 957 this value is set to a string of size 0. 959 When an instance of apsChanConfigIfIndex is set equal to an 960 instance of ifIndex that has an ifType value of sonet(39), 961 apsMapGroupName is set equal to the corresponding value of 962 apsChanConfigGroupName. 964 If an instance of ifIndex that has an ifType value of sonet(39) 965 ceases to be equal to an instance of apsChanConfigIfIndex, either 966 because of a change in the value of apsChanConfigIfIndex, or 967 because of row deletion in the ApsChanConfigTable, apsMapGroupName 968 is set to a string of size 0. 969 " 970 ::= { apsMapEntry 2 } 972 apsMapChanNumber OBJECT-TYPE 973 SYNTAX Integer32 (-1..14) 974 MAX-ACCESS read-only 975 STATUS current 976 DESCRIPTION 977 "This field is set to a unique channel number within an APS group. 978 The value 0 indicates the null channel. The values 1-14 define a 979 working channel. If the SONET LTE is not part of an APS group this 980 value is set to -1. 982 When an instance of apsChanConfigIfIndex is set equal to an instance of 983 ifIndex that has an ifType value of sonet(39), apsMapChanNumber is set 984 equal to the corresponding value of apsChanConfigNumber. 986 If an instance of ifIndex that has an ifType value of sonet(39) 987 ceases to be equal to an instance of apsChanConfigIfIndex, either 988 because of a change in the value of apsChanConfigIfIndex, or because 989 of row deletion in the ApsChanConfigTable, apsMapChanNumber is set to -1. 990 " 991 ::= { apsMapEntry 3 } 993 -- 994 -- APS Channel Configuration Table 995 -- 996 -- This table supports the addition, configuration and deletion of channels 997 -- in APS groups. 998 -- 1000 apsChanConfigTable OBJECT-TYPE 1001 SYNTAX SEQUENCE OF ApsChanConfigEntry 1002 MAX-ACCESS not-accessible 1003 STATUS current 1004 DESCRIPTION 1005 "This table lists the APS channels that have been configured 1006 in APS groups." 1007 ::= { apsMIBObjects 4 } 1009 apsChanConfigEntry OBJECT-TYPE 1010 SYNTAX ApsChanConfigEntry 1011 MAX-ACCESS not-accessible 1012 STATUS current 1013 DESCRIPTION 1014 "A conceptual row in the apsChanConfigTable." 1015 INDEX {apsChanConfigGroupName, apsChanConfigNumber} 1016 ::= { apsChanConfigTable 1 } 1018 ApsChanConfigEntry ::= SEQUENCE { 1019 apsChanConfigGroupName SnmpAdminString, 1020 apsChanConfigNumber Integer32, 1021 apsChanConfigRowStatus RowStatus, 1022 apsChanConfigIfIndex InterfaceIndex, 1023 apsChanConfigPriority INTEGER, 1024 apsChanConfigStorageType StorageType 1025 } 1027 apsChanConfigGroupName OBJECT-TYPE 1028 SYNTAX SnmpAdminString (SIZE (1..32)) 1029 MAX-ACCESS not-accessible 1030 STATUS current 1031 DESCRIPTION 1032 "A textual name for the APS group which this channel is 1033 included in." 1034 ::= { apsChanConfigEntry 1 } 1036 apsChanConfigNumber OBJECT-TYPE 1037 SYNTAX Integer32 (0..14) 1038 MAX-ACCESS not-accessible 1039 STATUS current 1040 DESCRIPTION 1041 "This field is set to a unique channel number within an APS group. 1042 The value 0 indicates the null channel. The values 1-14 define a 1043 working channel. 1045 This field must be assigned a unique number within the group." 1046 ::= { apsChanConfigEntry 2 } 1048 apsChanConfigRowStatus OBJECT-TYPE 1049 SYNTAX RowStatus 1050 MAX-ACCESS read-create 1051 STATUS current 1052 DESCRIPTION 1053 "The status of this APS channel entry. 1055 An entry may not exist in the active state unless all 1056 objects in the entry have an appropriate value. 1058 A row in the apsChanConfigTable may not be created, 1059 deleted, set to notInService or otherwise modified 1060 if the apsChanConfigGroupName value is equal to an 1061 apsConfigName value and the associated apsConfigRowStatus 1062 object is equal to active. However, if the apsConfigRowStatus 1063 object is equal to notInService, a row may be created, deleted 1064 or modified. In other words, a channel may not be added, deleted 1065 or modified if the group is active. 1067 A row may be created with an apsChanConfigGroupName value 1068 that is not equal to any existing instance of apsConfigName. 1069 This action is the initial step in adding a SONET LTE to a 1070 new APS group. 1072 If this object is set to destroy, the associated instance 1073 of apsMapGroupName will be set to a string of size 0 and 1074 the apsMapChanNumber will be set to -1. The channel status 1075 entry will also be deleted by this action. 1077 apsChanConfigNumber must be set to a unique channel number within 1078 the APS group. The value 0 indicates the null channel. 1079 The values 1-14 define a working channel. When an attempt is 1080 made to set the corresponding apsConfigRowStatus field to 1081 active the apsChanConfigNumber values of all entries with equal 1082 apsChanConfigGroupName fields must represent a set of consecutive 1083 integer values beginning with 0 or 1, depending on the architecture 1084 of the group, and ending with n, where n is greater than or 1085 equal to 1 and less than or equal to 14. Otherwise, the error 1086 inconsistentValue is returned to the apsConfigRowStatus 1087 set attempt. 1088 " 1089 ::= { apsChanConfigEntry 3 } 1091 apsChanConfigIfIndex OBJECT-TYPE 1092 SYNTAX InterfaceIndex 1093 MAX-ACCESS read-create 1094 STATUS current 1095 DESCRIPTION 1096 "The Interface Index assigned to a SONET LTE. This is an 1097 interface with ifType sonet(39). The value of this object 1098 must be unique among all instances of apsChanConfigIfIndex. 1099 In other words, a particular SONET LTE can only be configured in 1100 one APS group. 1102 This object cannot be set if the apsChanConfigGroupName instance 1103 associated with this row is equal to an instance of apsConfigName and 1104 the corresponding apsConfigRowStatus object is set to active. In other 1105 words this value cannot be changed if the APS group is active. However, 1106 this value may be changed if the apsConfigRowStatus value is equal to 1107 notInService. 1108 " 1110 ::= { apsChanConfigEntry 4 } 1112 apsChanConfigPriority OBJECT-TYPE 1113 SYNTAX INTEGER {low(1), high(2)} 1114 MAX-ACCESS read-create 1115 STATUS current 1116 DESCRIPTION 1117 "The priority of the channel. 1119 This field deterimines whether high or low priority 1120 SD and SF codes are used in K1 requests. 1122 This field is only applicable if the channel is to be included in 1123 a group using the 1:n architecture. It is not applicable if the 1124 channel is to be included in a group using the 1+1 architecture, 1125 and is ignored in that case. 1127 This object cannot be set if the apsChanConfigGroupName instance 1128 associated with this row is equal to an instance of apsConfigName 1129 and the corresponding apsConfigRowStatus object is set to active. 1130 In other words this value cannot be changed if the APS group is 1131 active. However, this value may be changed if the 1132 apsConfigRowStatus value is equal to notInService. 1133 " 1134 DEFVAL { low } 1135 ::= { apsChanConfigEntry 5 } 1137 apsChanConfigStorageType OBJECT-TYPE 1138 SYNTAX StorageType 1139 MAX-ACCESS read-create 1140 STATUS current 1141 DESCRIPTION 1142 "The storage type for this conceptual row. 1143 Conceptual rows having the value 'permanent' need not 1144 allow write-access to any columnar objects in the row." 1145 DEFVAL { nonVolatile } 1146 ::= { apsChanConfigEntry 6 } 1148 -- 1149 -- APS Command Table 1150 -- 1151 -- This table provides the ability to initiate APS commands. 1152 -- 1154 apsCommandTable OBJECT-TYPE 1155 SYNTAX SEQUENCE OF ApsCommandEntry 1156 MAX-ACCESS not-accessible 1157 STATUS current 1158 DESCRIPTION 1159 "This table allows commands to be sent to configured APS groups." 1160 ::= { apsMIBObjects 5 } 1162 apsCommandEntry OBJECT-TYPE 1163 SYNTAX ApsCommandEntry 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION 1167 "A conceptual row in the apsCommandTable. This row exists only if 1168 the associated apsConfigEntry is active." 1169 INDEX {apsChanConfigGroupName, apsChanConfigNumber} 1170 ::= { apsCommandTable 1 } 1172 ApsCommandEntry ::= SEQUENCE { 1173 apsCommandSwitch ApsSwitchCommand, 1174 apsCommandControl ApsControlCommand 1175 } 1177 apsCommandSwitch OBJECT-TYPE 1178 SYNTAX ApsSwitchCommand 1179 MAX-ACCESS read-write 1180 STATUS current 1181 DESCRIPTION 1182 "Allows the initiation of an APS switch command on the 1183 APS group and channel specified by the index values. 1185 If the APS switch command cannot be executed because an 1186 equal or higer priority request is in effect, an error 1187 is returned. 1189 When read this object returns the last command written 1190 or noCmd if no command has been written to this 1191 channel since initialization. The return of the last command 1192 written does not imply that this command is currently in effect. 1193 This request may have been preempted by a higher priority 1194 local or remote request. In order to determine the 1195 current state of the APS group it is necessary to read 1196 the objects apsStatusK1K2Rcv and apsStatusK1K2Trans. 1198 The value lockoutOfProtection should only be applied 1199 to the protection line channel since that switch command 1200 prevents any of the working channels from switching to the protection 1201 line. Following the same logic, forcedSwitchProtectToWork and 1202 manualSwitchProtectToWork should only be applied to the protection 1203 line channel. 1205 forcedSwitchWorkToProtect and manualSwitchWorkToProtect 1206 should only be applied to a working channel. 1207 " 1208 ::= { apsCommandEntry 1 } 1210 apsCommandControl OBJECT-TYPE 1211 SYNTAX ApsControlCommand 1212 MAX-ACCESS read-write 1213 STATUS current 1214 DESCRIPTION 1215 "Allows the initiation of an APS control command on the 1216 APS group and channel specified by the index values. 1218 When read this object returns the last command written 1219 or noCmd if no command has been 1220 written to this channel since initialization. 1222 This object does not apply to the protection line. 1223 " 1224 ::= { apsCommandEntry 2 } 1226 -- 1227 -- APS Channel Status Table 1228 -- 1229 -- This table provides APS channel statistics. 1230 -- 1232 apsChanStatusTable OBJECT-TYPE 1233 SYNTAX SEQUENCE OF ApsChanStatusEntry 1234 MAX-ACCESS not-accessible 1235 STATUS current 1236 DESCRIPTION 1237 "This table contains status information for all SONET LTE 1238 interfaces that are included in APS groups." 1239 ::= { apsMIBObjects 6 } 1241 apsChanStatusEntry OBJECT-TYPE 1242 SYNTAX ApsChanStatusEntry 1243 MAX-ACCESS not-accessible 1244 STATUS current 1245 DESCRIPTION 1246 "A conceptual row in the apsChanStatusTable." 1247 AUGMENTS { apsChanConfigEntry } 1248 ::= { apsChanStatusTable 1 } 1250 ApsChanStatusEntry ::= SEQUENCE { 1251 apsChanStatusCurrent BITS, 1252 apsChanStatusSignalDegrades Counter32, 1253 apsChanStatusSignalFailures Counter32, 1254 apsChanStatusSwitchovers Counter32, 1255 apsChanStatusLastSwitchover TimeStamp, 1256 apsChanStatusSwitchoverSeconds Counter32, 1257 apsChanStatusDiscontinuityTime TimeStamp 1258 } 1260 apsChanStatusCurrent OBJECT-TYPE 1261 SYNTAX BITS { 1262 lockedOut(0), 1263 sd(1), 1264 sf(2), 1265 switched(3), 1266 wtr(4) 1267 } 1268 MAX-ACCESS read-only 1269 STATUS current 1270 DESCRIPTION 1271 "Indicates the current state of the port. 1273 lockedOut 1275 This bit, when applied to a working channel, indicates that 1276 the channel is prevented from switching to the protection line. 1277 When applied to the null channel, this bit indicates that no 1278 working channel may switch to the protection line. 1280 sd 1282 A signal degrade condition is in effect. 1284 sf 1286 A signal failure condition is in effect. 1288 switched 1290 The switched bit is applied to a working channel if that 1291 channel is currently switched to the protection line. 1293 wtr 1295 A Wait-to-Restore state is in effect. 1296 " 1297 ::= { apsChanStatusEntry 1 } 1299 apsChanStatusSignalDegrades OBJECT-TYPE 1300 SYNTAX Counter32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "A count of Signal Degrade conditions. This 1305 condition occurs when the line Bit Error Rate 1306 exceeds the currently configured threshold. 1308 Discontinuities in the value of this counter can occur at 1309 re-initialization of the management system, and at other 1310 times as indicated by the value of 1311 apsChanStatusDiscontinuityTime." 1313 ::= { apsChanStatusEntry 2 } 1315 apsChanStatusSignalFailures OBJECT-TYPE 1316 SYNTAX Counter32 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "A count of Signal Failure conditions that have been 1321 detected on the incoming signal. This condition occurs 1322 when a loss of signal, loss of frame, AIS-L or a Line 1323 bit error rate exceeding 10^-3 is detected on an 1324 incoming line. 1326 Discontinuities in the value of this counter can occur at 1327 re-initialization of the management system, and at other 1328 times as indicated by the value of 1329 apsChanStatusDiscontinuityTime." 1331 ::= { apsChanStatusEntry 3 } 1333 apsChanStatusSwitchovers OBJECT-TYPE 1334 SYNTAX Counter32 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "When queried with index value apsChanConfigNumber other than 0, 1339 this object will return the number of times this channel has 1340 switched to the protection line. 1342 When queried with index value apsChanConfigNumber set to 0, 1343 which is the protection line, this object will return the 1344 number of times that any working channel has been switched 1345 back to the working line from this protection line. 1347 Discontinuities in the value of this counter can occur at 1348 re-initialization of the management system, and at other 1349 times as indicated by the value of 1350 apsChanStatusDiscontinuityTime." 1352 ::= { apsChanStatusEntry 4 } 1354 apsChanStatusLastSwitchover OBJECT-TYPE 1355 SYNTAX TimeStamp 1356 MAX-ACCESS read-only 1357 STATUS current 1358 DESCRIPTION 1359 "When queried with index value apsChanConfigNumber other than 0, 1360 this object will return the value of sysUpTime when this 1361 channel last completed a switch to the protection line. If this 1362 channel has never switched to the protection line, the value 1363 0 will be returned. 1365 When queried with index value apsChanConfigNumber set to 0, 1366 which is the protection line, this object will return the 1367 value of sysUpTime the last time that a working channel was 1368 switched back to the working line from this protection line. 1369 If no working channel has ever switched back to the working 1370 line from this protection line, the value 0 will be returned." 1371 ::= { apsChanStatusEntry 5 } 1373 apsChanStatusSwitchoverSeconds OBJECT-TYPE 1374 SYNTAX Counter32 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "The cumulative Protection Switching Duration (PSD) time in 1379 seconds. For a working channel, this is the cumulative number 1380 of seconds that service was carried on the protection line. 1381 For the protection line, this is the cumulative number of 1382 seconds that the protection line has been used to carry any 1383 working channel traffic. This information is only valid if 1384 revertive switching is enabled. The value 0 will be returned 1385 otherwise. 1387 Discontinuities in the value of this counter can occur at 1388 re-initialization of the management system, and at other 1389 times as indicated by the value of 1390 apsChanStatusDiscontinuityTime. For example, if the value 1391 of an instance of apsChanStatusSwitchoverSeconds changes 1392 from a non-zero value to zero due to revertive switching 1393 being disabled, it is expected that the corresponding 1394 value of apsChanStatusDiscontinuityTime will be updated 1395 to reflect the time of the configuration change. 1396 " 1397 ::= { apsChanStatusEntry 6 } 1399 apsChanStatusDiscontinuityTime OBJECT-TYPE 1400 SYNTAX TimeStamp 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "The value of sysUpTime on the most recent occasion at which 1405 any one or more of this channel's counters suffered a 1406 discontinuity. The relevant counters are the specific 1407 instances associated with this channel of any Counter32 1408 object contained in apsChanStatusTable. If no such 1409 discontinuities have occurred since the last re-initialization 1410 of the local management subsystem, then this object contains 1411 a zero value." 1412 ::= { apsChanStatusEntry 7 } 1414 apsNotificationEnable OBJECT-TYPE 1415 SYNTAX BITS { 1416 switchover(0), 1417 modeMismatch(1), 1418 channelMismatch(2), 1419 psbf(3), 1420 feplf(4) 1421 } 1422 MAX-ACCESS read-write 1423 STATUS current 1424 DESCRIPTION 1425 "Provides the ability to enable and disable notifications 1426 defined in this MIB. 1428 switchover 1430 Indicates apsEventSwitchover notifications 1431 should be generated. 1433 modeMismatch 1435 Indicates apsEventModeMismatch notifications 1436 should be generated. 1438 channelMismatch 1440 Indicates apsEventChannelMismatch notifications 1441 should be generated. 1443 psbf 1445 Indicates apsEventPSBF notifications 1446 should be generated. 1448 feplf 1450 Indicates apsEventFEPLF notifications 1451 should be generated. 1452 " 1453 DEFVAL { { } } 1454 ::= { apsMIBObjects 7 } 1456 -- 1457 -- APS EVENTS 1458 -- 1460 apsNotificationsPrefix OBJECT IDENTIFIER 1461 ::= { apsMIBNotifications 0 } 1463 apsEventSwitchover NOTIFICATION-TYPE 1464 OBJECTS { apsChanStatusSwitchovers, apsChanStatusCurrent } 1465 STATUS current 1466 DESCRIPTION 1467 "An apsEventSwitchover notification is sent when the 1468 value of an instance of apsChanStatusSwitchovers increments." 1469 ::= { apsNotificationsPrefix 1 } 1471 apsEventModeMismatch NOTIFICATION-TYPE 1472 OBJECTS { apsStatusModeMismatches, apsStatusCurrent } 1473 STATUS current 1474 DESCRIPTION 1475 "An apsEventModeMismatch notification is sent when the 1476 value of an instance of apsStatusModeMismatches increments." 1477 ::= { apsNotificationsPrefix 2 } 1479 apsEventChannelMismatch NOTIFICATION-TYPE 1480 OBJECTS { apsStatusChannelMismatches, apsStatusCurrent } 1481 STATUS current 1482 DESCRIPTION 1483 "An apsEventChannelMismatch notification is sent when the 1484 value of an instance of apsStatusChannelMismatches increments." 1485 ::= { apsNotificationsPrefix 3 } 1487 apsEventPSBF NOTIFICATION-TYPE 1488 OBJECTS { apsStatusPSBFs, apsStatusCurrent } 1489 STATUS current 1490 DESCRIPTION 1491 "An apsEventPSBF notification is sent when the 1492 value of an instance of apsStatusPSBFs increments." 1493 ::= { apsNotificationsPrefix 4 } 1495 apsEventFEPLF NOTIFICATION-TYPE 1496 OBJECTS { apsStatusFEPLFs, apsStatusCurrent } 1497 STATUS current 1498 DESCRIPTION 1499 "An apsEventFEPLFs notification is sent when the 1500 value of an instance of apsStatusFEPLFs increments." 1501 ::= { apsNotificationsPrefix 5 } 1503 -- conformance information 1505 apsGroups OBJECT IDENTIFIER ::= { apsMIBConformance 1 } 1506 apsCompliances OBJECT IDENTIFIER ::= { apsMIBConformance 2 } 1508 apsFullCompliance MODULE-COMPLIANCE 1509 STATUS current 1510 DESCRIPTION 1511 "When this MIB is implemented with support for read-create, then 1512 such an implementation can claim read/write compliance. Linear APS 1513 groups can then be both monitored and configured with this MIB. 1515 Note that An agent is not required to process SNMP Set Requests that affect 1516 multiple control objects within this MIB. This is intended to 1517 simplify the processing of Set Requests for the various control tables 1518 by eliminating the possibility that a single Set PDU will contain 1519 multiple varbinds which are in conflict. 1520 " 1522 MODULE 1523 MANDATORY-GROUPS { apsConfigGeneral, apsStatusGeneral, apsChanGeneral } 1525 OBJECT apsConfigRowStatus 1526 SYNTAX INTEGER { active(1) } 1527 WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) } 1528 DESCRIPTION 1529 "Support for createAndWait and notInService is not required." 1531 OBJECT apsChanConfigRowStatus 1532 SYNTAX INTEGER { active(1) } 1533 WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) } 1534 DESCRIPTION 1535 "Support for createAndWait and notInService is not required." 1537 GROUP apsConfigWtr 1538 DESCRIPTION 1539 "Implementation of this group is optional for all 1540 linear APS implementations. The information is 1541 applicable to groups supporting a configurable 1542 WTR period." 1544 GROUP apsCommandOnePlusOne 1545 DESCRIPTION 1546 "Implementation of this group is optional for all 1547 linear APS implementations. The information is 1548 applicable to groups implementing the linear 1549 APS 1+1 architecture and supporting set operations." 1551 GROUP apsCommandOneToN 1552 DESCRIPTION 1553 "Implementation of this group is optional for all 1554 linear APS implementations. The information is 1555 applicable to groups implementing the linear 1556 APS 1:n architecture and supporting set operations." 1558 GROUP apsChanOneToN 1559 DESCRIPTION 1560 "Implementation of this group is optional for all 1561 linear APS implementations. The information is 1562 applicable to groups implementing the linear 1563 APS 1:n architecture." 1565 GROUP apsTotalsGroup 1566 DESCRIPTION 1567 "Implementation of this group is optional for all 1568 linear APS implementations." 1570 GROUP apsMapGroup 1571 DESCRIPTION 1572 "Implementation of this group is optional for all 1573 linear APS implementations." 1575 GROUP apsEventGroup 1576 DESCRIPTION 1577 "Implementation of this group is optional for all 1578 linear APS implementations." 1580 ::= { apsCompliances 1 } 1582 -- 1583 -- Read-Only Compliance 1584 -- 1586 apsReadOnlyCompliance MODULE-COMPLIANCE 1587 STATUS current 1588 DESCRIPTION 1589 "When this MIB is implemented without support for read-create 1590 (i.e. in read-only mode), then that implementation can claim 1591 read-only compliance. In that case, linear APS groups can be 1592 monitored but cannot be configured with this MIB." 1594 MODULE 1595 MANDATORY-GROUPS { apsConfigGeneral, apsStatusGeneral, apsChanGeneral } 1597 OBJECT apsConfigMode 1598 MIN-ACCESS read-only 1599 DESCRIPTION 1600 "Write access is not required." 1602 OBJECT apsConfigRevert 1603 MIN-ACCESS read-only 1604 DESCRIPTION 1605 "Write access is not required." 1607 OBJECT apsConfigDirection 1608 MIN-ACCESS read-only 1609 DESCRIPTION 1610 "Write access is not required." 1612 OBJECT apsConfigExtraTraffic 1613 MIN-ACCESS read-only 1614 DESCRIPTION 1615 "Write access is not required." 1617 OBJECT apsConfigSdBerThreshold 1618 MIN-ACCESS read-only 1619 DESCRIPTION 1620 "Write access is not required." 1622 OBJECT apsConfigSfBerThreshold 1623 MIN-ACCESS read-only 1624 DESCRIPTION 1625 "Write access is not required." 1627 OBJECT apsConfigWaitToRestore 1628 MIN-ACCESS read-only 1629 DESCRIPTION 1630 "Write access is not required." 1632 OBJECT apsConfigRowStatus 1633 SYNTAX INTEGER { active(1) } 1634 MIN-ACCESS read-only 1635 DESCRIPTION 1636 "Write access is not required, and active is the only status 1637 that needs to be supported." 1639 OBJECT apsConfigStorageType 1640 MIN-ACCESS read-only 1641 DESCRIPTION 1642 "Write access is not required." 1644 OBJECT apsChanConfigIfIndex 1645 MIN-ACCESS read-only 1646 DESCRIPTION 1647 "Write access is not required." 1649 OBJECT apsChanConfigPriority 1650 MIN-ACCESS read-only 1651 DESCRIPTION 1652 "Write access is not required." 1654 OBJECT apsChanConfigRowStatus 1655 SYNTAX INTEGER { active(1) } 1656 MIN-ACCESS read-only 1657 DESCRIPTION 1658 "Write access is not required, and active is the only status 1659 that needs to be supported." 1661 OBJECT apsChanConfigStorageType 1662 MIN-ACCESS read-only 1663 DESCRIPTION 1664 "Write access is not required." 1666 OBJECT apsNotificationEnable 1667 MIN-ACCESS read-only 1668 DESCRIPTION 1669 "Write access is not required." 1671 GROUP apsConfigWtr 1672 DESCRIPTION 1673 "Implementation of this group is optional for all 1674 linear APS implementations. The information is 1675 applicable to groups supporting a configurable 1676 WTR period." 1678 GROUP apsCommandOnePlusOne 1679 DESCRIPTION 1680 "Implementation of this group is optional for all 1681 linear APS implementations. The information is 1682 applicable to groups implementing the linear 1683 APS 1+1 architecture and supporting set operations." 1685 GROUP apsCommandOneToN 1686 DESCRIPTION 1687 "Implementation of this group is optional for all 1688 linear APS implementations. The information is 1689 applicable to groups implementing the linear 1690 APS 1:n architecture and supporting set operations." 1692 GROUP apsChanOneToN 1693 DESCRIPTION 1694 "Implementation of this group is optional for all 1695 linear APS implementations. The information is 1696 applicable to groups implementing the linear 1697 APS 1:n architecture." 1699 GROUP apsTotalsGroup 1700 DESCRIPTION 1701 "Implementation of this group is optional for all 1702 linear APS implementations." 1704 GROUP apsMapGroup 1705 DESCRIPTION 1706 "Implementation of this group is optional for all 1707 linear APS implementations." 1709 GROUP apsEventGroup 1710 DESCRIPTION 1711 "Implementation of this group is optional for all 1712 linear APS implementations." 1714 ::= { apsCompliances 2 } 1716 -- units of conformance 1718 apsConfigGeneral OBJECT-GROUP 1719 OBJECTS 1720 { 1721 apsConfigMode, 1722 apsConfigRevert, 1723 apsConfigDirection, 1724 apsConfigExtraTraffic, 1725 apsConfigSdBerThreshold, 1726 apsConfigSfBerThreshold, 1727 apsConfigCreationTime, 1728 apsConfigRowStatus, 1729 apsConfigStorageType, 1730 apsNotificationEnable 1731 } 1732 STATUS current 1733 DESCRIPTION 1734 "A collection of apsConfigTable objects providing configuration 1735 information applicable to all linear APS groups." 1736 ::= { apsGroups 1 } 1738 apsConfigWtr OBJECT-GROUP 1739 OBJECTS 1740 { 1741 apsConfigWaitToRestore 1742 } 1743 STATUS current 1744 DESCRIPTION 1745 "The apsConfigTable object that provides information which is 1746 applicable to groups supporting a configurable WTR period." 1747 ::= { apsGroups 2 } 1749 -- If set operations are not supported neither of the following two groups 1750 -- are implemented. If sets are supported only one of these groups is 1751 -- implemented for a linear APS group instance. 1753 apsCommandOnePlusOne OBJECT-GROUP 1754 OBJECTS 1755 { 1756 apsCommandSwitch 1757 } 1758 STATUS current 1759 DESCRIPTION 1760 "The apsCommandTable object which is applicable to groups 1761 implementing the linear APS 1+1 architecture. Also, set operations 1762 must be supported." 1763 ::= { apsGroups 3 } 1765 apsCommandOneToN OBJECT-GROUP 1766 OBJECTS 1767 { 1768 apsCommandSwitch, 1769 apsCommandControl 1770 } 1771 STATUS current 1772 DESCRIPTION 1773 "A collection of apsCommandTable objects which are applicable to 1774 groups implementing the linear APS 1:n architecture. Also, set 1775 operations must be supported." 1776 ::= { apsGroups 4 } 1778 apsStatusGeneral OBJECT-GROUP 1779 OBJECTS 1780 { 1781 apsStatusK1K2Rcv, 1782 apsStatusK1K2Trans, 1783 apsStatusCurrent, 1784 apsStatusModeMismatches, 1785 apsStatusChannelMismatches, 1786 apsStatusPSBFs, 1787 apsStatusFEPLFs, 1788 apsStatusSwitchedChannel, 1789 apsStatusDiscontinuityTime 1790 } 1791 STATUS current 1792 DESCRIPTION 1793 "A collection of apsStatusTable objects providing status information 1794 applicable to all linear APS groups." 1795 ::= { apsGroups 5 } 1797 apsChanGeneral OBJECT-GROUP 1798 OBJECTS 1799 { 1800 apsChanConfigIfIndex, 1801 apsChanConfigRowStatus, 1802 apsChanConfigStorageType, 1803 apsChanStatusCurrent, 1804 apsChanStatusSignalDegrades, 1805 apsChanStatusSignalFailures, 1806 apsChanStatusSwitchovers, 1807 apsChanStatusLastSwitchover, 1808 apsChanStatusSwitchoverSeconds, 1809 apsChanStatusDiscontinuityTime 1810 } 1811 STATUS current 1812 DESCRIPTION 1813 "A collection of channel objects providing information applicable to 1814 all linear APS channels." 1815 ::= { apsGroups 6 } 1817 apsChanOneToN OBJECT-GROUP 1818 OBJECTS 1819 { 1820 apsChanConfigPriority 1821 } 1822 STATUS current 1823 DESCRIPTION 1824 "The apsChanConfigTable object that provides information which is only 1825 applicable to groups implementing the linear APS 1:n architecture." 1826 ::= { apsGroups 7 } 1828 apsTotalsGroup OBJECT-GROUP 1829 OBJECTS 1830 { 1831 apsConfigGroups, 1832 apsChanLTEs 1833 } 1834 STATUS current 1835 DESCRIPTION 1836 "A collection of objects providing optional counts of configured APS 1837 groups and SONET LTE interfaces." 1838 ::= { apsGroups 8 } 1840 apsMapGroup OBJECT-GROUP 1841 OBJECTS 1842 { 1843 apsMapGroupName, 1844 apsMapChanNumber 1845 } 1846 STATUS current 1847 DESCRIPTION 1848 "A collection of apsMapTable objects providing a mapping 1849 from sonet(39) InterfaceIndex to group name and channel 1850 number for assigned APS channels and a list of unassigned 1851 sonet(39) interfaces." 1852 ::= { apsGroups 9 } 1854 apsEventGroup NOTIFICATION-GROUP 1855 NOTIFICATIONS {apsEventSwitchover, apsEventModeMismatch, 1856 apsEventChannelMismatch, apsEventPSBF, 1857 apsEventFEPLF } 1858 STATUS current 1859 DESCRIPTION 1860 "A collection of SONET linear APS notifications." 1861 ::= { apsGroups 10 } 1863 END 1865 5. Intellectual Property 1867 The IETF takes no position regarding the validity or scope of any 1868 intellectual property or other rights that might be claimed to 1869 pertain to the implementation or use of the technology described in 1870 this document or the extent to which any license under such rights 1871 might or might not be available; neither does it represent that it 1872 has made any effort to identify any such rights. Information on the 1873 IETF's procedures with respect to rights in standards-track and 1874 standards-related documentation can be found in BCP-11. Copies of 1875 claims of rights made available for publication and any assurances of 1876 licenses to be made available, or the result of an attempt made to 1877 obtain a general license or permission for the use of such 1878 proprietary rights by implementors or users of this specification can 1879 be obtained from the IETF Secretariat. 1881 6. Acknowledgments 1883 This document is a product of the AToMMIB Working Group. A number of 1884 constructs from a separate draft submission by Ken Chapman have been 1885 included here. Suggestions by Orly Nicklass, Faye Ly, Ron Carmona, 1886 Kaj Tesink, C. M. Heard, Muly Ilan, and Mickey Spiegel have been 1887 incorporated. A quality review was provided by Lauren Heintz 1888 and an IESG review by John Flick and Bert Wijnen. 1890 7. References 1892 [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for 1893 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1895 [2] Rose, M. and K. McCloghrie, "Structure and Identification of 1896 Management Information for TCP/IP-based Internets", STD 16, RFC 1897 1155, May 1990. 1899 [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, 1900 RFC 1212, March 1991. 1902 [4] Rose, M., "A Convention for Defining Traps for use with the 1903 SNMP", RFC 1215, March 1991. 1905 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1906 M. and S. Waldbusser, "Structure of Management Information 1907 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1909 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1910 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 1911 58, RFC 2579, April 1999. 1913 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1914 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 1915 58, RFC 2580, April 1999. 1917 [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 1918 Network Management Protocol", STD 15, RFC 1157, May 1990. 1920 [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1921 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1923 [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1924 "Transport Mappings for Version 2 of the Simple Network 1925 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1927 [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1928 Processing and Dispatching for the Simple Network Management 1929 Protocol (SNMP)", RFC 2572, April 1999. 1931 [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) 1932 for version 3 of the Simple Network Management Protocol 1933 (SNMPv3)", RFC 2574, April 1999. 1935 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol 1936 Operations for Version 2 of the Simple Network Management 1937 Protocol (SNMPv2)", RFC 1905, January 1996. 1939 [14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 1940 2573, April 1999. 1942 [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1943 Control Model (VACM) for the Simple Network Management Protocol 1944 (SNMP)", RFC 2575, April 1999. 1946 [16] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction 1947 to Version 3 of the Internet-standard Network Management 1948 Framework", RFC 2570, April 1999. 1950 [17] McCloghrie, K., and F. Kastenholz. "The Interfaces Group MIB", 1951 RFC 2863, June 2000. 1953 [18] GR-253-CORE Issue 2, December 1995, Revision 2, January 1999 1955 [19] ITU-T Recommendation G.783 (04/97) 1957 [20] K. Chapman, "Definitions of Managed Objects for SONET Linear 1958 Automatic Protection Switching (APS)", 1959 draft-kchapman-sonet-aps-00.txt, July 1999 1961 8.Security Considerations 1963 There are a number of management objects defined in this MIB 1964 that have a MAX-ACCESS clause of read-write and/or read-create. 1965 Such objects may be considered sensitive or vulnerable in some 1966 network environments. The support for SET operations in a 1967 non-secure environment without proper protection can have a 1968 negative effect on network operations. In particular, the APS command 1969 objects apsCommandSwitch and apsCommandControl and the APS configuration 1970 objects apsConfigRowStatus, apsConfigMode, apsConfigRevert, 1971 apsConfigDirection, apsConfigExtraTraffic, apsConfigSdBerThreshold, 1972 apsConfigSfBerThreshold, apsConfigWaitToRestore, apsConfigStorageType, 1973 apsChanConfigRowStatus, apsChanConfigIfIndex, apsChanConfigPriority, 1974 apsChanConfigStorageType and apsNotificationEnable have the potential 1975 of disrupting APS operations if set operations are performed with 1976 malicious intent. 1978 SNMPv1 by itself is not a secure environment. Even if the 1979 network itself is secure (for example by using IPSec), even then, 1980 there is no control as to who on the secure network is allowed 1981 to access and GET/SET (read/change/create/delete) the objects in 1982 this MIB. 1984 It is recommended that the implementers consider the security 1985 features as provided by the SNMPv3 framework. Specifically, the 1986 use of the User-based Security Model RFC 2574 [RFC2574] and the 1987 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1989 It is then a customer/user responsibility to ensure that the SNMP 1990 entity giving access to an instance of this MIB, is properly 1991 configured to give access to the objects only to those 1992 principals (users) that have legitimate rights to indeed GET or 1993 SET (change/create/delete) them. 1995 9. Editor's Address 1997 Jeff Johnson 1998 RedBack Networks. Inc. 1999 300 Holger Way 2000 San Jose, CA 95134-1362 2001 Phone: +1 408 750 5460 2002 Email: jeff@redback.com 2004 Michael Thatcher 2005 RedBack Networks. Inc. 2006 300 Holger Way 2007 San Jose, CA 95134-1362 2008 Phone: +1 408 750 5449 2009 Email: thatcher@redback.com 2011 Jim Kuhfeld 2012 RedBack Networks. Inc. 2013 300 Holger Way 2014 San Jose, CA 95134-1362 2015 Phone: +1 408 750 5465 2016 Email: jkuhfeld@redback.com 2018 10. Full Copyright Statement 2020 Copyright (C) The Internet Society (2002). All Rights Reserved. 2022 This document and translations of it may be copied and furnished 2023 to others, and derivative works that comment on or otherwise 2024 explain it or assist in its implmentation may be prepared, copied, 2025 published and distributed, in whole or in part, without 2026 restriction of any kind, provided that the above copyright notice 2027 and this paragraph are included on all such copies and derivative 2028 works. However, this document itself may not be modified in any 2029 way, such as by removing the copyright notice or references to the 2030 Internet Society or other Internet organizations, except as needed 2031 for the purpose of developing Internet standards in which case the 2032 procedures for copyrights defined in the Internet Standards 2033 process must be followed, or as required to translate it into 2034 languages other than English. 2036 The limited permissions granted above are perpetual and will not 2037 be revoked by the Internet Society or its successors or assigns. 2039 This document and the information contained herein is provided on 2040 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2041 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2042 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2043 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2044 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 2045 PURPOSE."