idnits 2.17.1 draft-ietf-atommib-sonetaps-mib-07.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 113 instances of too long lines in the document, the longest one being 9 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 945 has weird spacing: '... has an ifTyp...' == Line 949 has weird spacing: '... has an ifTyp...' == Line 967 has weird spacing: '... has an ifTyp...' == Line 971 has weird spacing: '... has an ifTyp...' == Line 1065 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 (April 22, 2002) is 8033 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 1963 -- 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 1964 -- Looks like a reference, but probably isn't: 'RFC2570' on line 87 == Unused Reference: '1' is defined on line 1869, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 1872, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 1876, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1879, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 1882, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 1886, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1890, but no explicit reference was found in the text == Unused Reference: '8' is defined on line 1894, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 1897, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1900, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 1904, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 1908, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 1912, but no explicit reference was found in the text == Unused Reference: '14' is defined on line 1916, but no explicit reference was found in the text == Unused Reference: '15' is defined on line 1919, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 1923, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 1927, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 1930, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 1932, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 1934, 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 October 22, 2002 M. Thatcher 4 J. Kuhfeld 5 Redback Networks 6 April 22, 2002 8 Definitions of Managed Objects 9 for SONET Linear APS architectures 11 draft-ietf-atommib-sonetaps-mib-07.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 two or more 130 entries in this table with a common group name index and consecutive 131 channel numbers is the first step in the creation and configuration 132 of an APS group. It is not necessary to create channel numbers in 133 order; however, before an APS group is made active, the set of 134 channels must begin with channel number 0 (for architectures other 135 than onePlusOneOptimized) or channel number 1 (for the 136 onePlusOneOptimized architecture) and must have consecutive channel 137 numbers not exceeding 14. Note that the term null channel, which is 138 used throughout this document, refers to the protection line. 140 The apsConfigTable supports addition, modification, and deletion of 141 entries representing linear APS groups. Entries are indexed by a text 142 group name. Each entry contains parameters that specify the 143 configuration of a particular linear APS group. Entries are created 144 in this table after a set of channels are created in the 145 apsChanConfigTable. To successfully set an instance of 146 apsConfigRowStatus to active the apsConfigEntry must contain valid 147 values and all associated apsChanConfigEntry rows must be valid and 148 produce a consecutive set of channels beginning with channel number 0 149 or 1, depending on the selected architecture. 151 The apsCommandTable provides linear APS commands that support 152 protection switching and the ability to modify APS operation. 153 Entries in this table are created as a side effect of setting the 154 associated apsConfigRowStatus object to active. Entries in this table 155 are deleted if the associated apsConfigRowStatus object is set to any 156 value except active. 158 The apsChanStatusTable provides individual channel statistics. 160 The apsStatusTable provides group level statistics. 162 An APS group is created and configured with the following sequence of 163 events: 165 CHANNEL CONFIGURATION 167 Create an entry in the apsChanConfigTable. Set the 168 apsChanConfigGroupName in an apsChanConfigEntry to a user-friendly 169 text string which will serve as the APS group name. The string must 170 not be equal to the apsConfigName of an existing apsConfigEntry with 171 apsConfigRowStatus set to active, since a channel cannot be added to 172 an active group. The string may be set equal to the apsConfigName of 173 a row which is currently not set to active, or it may be set to a 174 string which does not currently exist in any instance of 175 apsConfigName. A channel number is entered in apsChanConfigNumber. 176 A channel priority is entered in apsChanConfigPriority, if the 177 intended architecture is 1:n. apsChanConfigPriority is ignored if the 178 architecture is 1+1. The InterfaceIndex value of a SONET LTE 179 interface is entered in apsChanConfigIfIndex. 181 This step is repeated for all apsChanConfigEntry instances which are 182 to be included in the APS group. 184 ACTIVATING THE GROUP 186 If the apsChanConfigGroupName does not exist in an instance of 187 apsConfigName, an apsConfigEntry is created with the 188 apsChanConfigGroupName value used as the index for the row. The 189 apsConfigRowStatus value may be set to createAndGo. The 190 apsGroupConfigEntry and apsChanConfigEntry instances with matching 191 name fields will be checked for consistency. If any errors in the 192 channel numbers, architecture or configuration are uncovered the 193 apsConfigRowStatus set will return inconsistentValue, otherwise 194 noError is returned. 196 If the apsChanConfigGroupName value used in channel configuration 197 exists in a previously created, inactive apsConfigEntry instance, the 198 apsConfigRowStatus value may be set to active. 200 An agent is not required to process SNMP Set Requests that affect 201 multiple control objects within this MIB. This is intended to 202 simplify the processing of Set Requests for the various control 203 tables by eliminating the possibility that a single Set PDU will 204 contain multiple varbinds which are in conflict, such as a PDU which 205 both activates a given apsConfigEntry while at the same time it 206 deactivates an associated apsChanConfigEntry. 208 4. Definitions 210 APS-MIB DEFINITIONS ::= BEGIN 212 IMPORTS 213 MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, 214 Gauge32, Counter32, Integer32, transmission 215 FROM SNMPv2-SMI 217 TEXTUAL-CONVENTION, RowStatus, 218 TimeStamp, StorageType 219 FROM SNMPv2-TC 221 SnmpAdminString 222 FROM SNMP-FRAMEWORK-MIB 224 ifIndex, InterfaceIndex 225 FROM IF-MIB 227 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 228 FROM SNMPv2-CONF; 230 apsMIB MODULE-IDENTITY 231 LAST-UPDATED "200204222300Z" -- April 22, 2002 232 ORGANIZATION "IETF AToMMIB Working Group" 233 CONTACT-INFO 234 " Jeff Johnson 235 Postal: RedBack Networks. Inc. 236 300 Holger Way 237 San Jose, CA 95134-1362 238 Tel: +1 408 750 5460 239 Email: jeff@redback.com 241 Michael Thatcher 242 Postal: RedBack Networks. Inc. 243 300 Holger Way 244 San Jose, CA 95134-1362 245 Tel: +1 408 750 5449 246 Email: thatcher@redback.com 248 Jim Kuhfeld 249 Postal: RedBack Networks. Inc. 250 300 Holger Way 251 San Jose, CA 95134-1362 252 Tel: +1 408 750 5465 253 Email: jkuhfeld@redback.com" 254 DESCRIPTION 255 "This management information module supports the configuration 256 and management of SONET linear APS groups. The definitions and 257 descriptions used in this MIB have been derived from 258 Synchronous Optical Network (SONET) Transport Systems: 259 Common Generic Criteria, GR-253-CORE Revision 2, January 1999, 260 section 5.3. The MIB is also consistent with the Multiplex 261 Section Protection (MSP) protocol as specified in ITU-T 262 Recommendation G.783, Characteristics of synchronous digital 263 hierarchy (SDH) equipment function blocks, Annex A and B. " 264 REVISION "200204222300Z" -- April 22, 2002 265 DESCRIPTION 266 "Initial version of this MIB, published as RFC xxxx." 267 -- xxxx to be assigned by RFC-Editor 268 ::= { transmission XX } 269 -- assign XX 270 -- remove this notice from the MIB 272 apsMIBObjects OBJECT IDENTIFIER 273 ::= { apsMIB 1 } 275 apsMIBNotifications OBJECT IDENTIFIER 276 ::= { apsMIB 2 } 278 apsMIBConformance OBJECT IDENTIFIER 279 ::= { apsMIB 3 } 281 ApsK1K2 ::= TEXTUAL-CONVENTION 282 STATUS current 283 DESCRIPTION 284 "This Textual Convention describes an object that stores 285 a SONET K1 and K2 byte APS protocol field. 287 K1 is located in the first octet, K2 is located in 288 the second octet. Bits are numbered from left to right. 290 Bits 1-4 of the K1 byte indicate a request. 292 1111 Lockout of Protection 293 1110 Forced Switch 294 1101 SF - High Priority 295 1100 SF - Low Priority 296 1011 SD - High Priority 297 1010 SD - Low Priority 298 1001 not used 299 1000 Manual Switch 300 0111 not used 301 0110 Wait-to-Restore 302 0101 not used 303 0100 Exercise 304 0011 not used 305 0010 Reverse Request 306 0001 Do Not Revert 307 0000 No Request 309 Bits 5-8 of the K1 byte indicate the channel associated with the 310 request defined in bits 1-4. 312 0000 is the Null channel. 314 1-14 are working channels. 315 15 is the extra traffic channel 317 Bits 1-4 of the K2 byte indicate a channel. The channel is 318 defined with the same syntax as K1 Bits 5-8. 320 Bit 5 of the K2 byte indicates the 321 architecture. 323 0 if the architecture is 1+1 324 1 if the architecture is 1:n 326 Bits 6-8 of the K2 byte indicates the mode. 328 000 - 011 are reserved for future use 329 100 indicates the mode is unidirectional 330 101 indicates the mode is bidirectional 331 110 RDI-L 332 111 AIS-L 333 " 334 REFERENCE 335 "Bellcore (Telcordia Technologies) GR-253-CORE, Issue 2, 336 Revision 2 (January 1999), 5.3.5." 337 SYNTAX OCTET STRING (SIZE (2)) 339 ApsSwitchCommand ::= TEXTUAL-CONVENTION 340 STATUS current 341 DESCRIPTION 342 "An APS switch command allows a user to perform protection 343 switch actions. 345 The Switch command values are: 347 noCmd 349 This value should be returned by a read request when no switch 350 command has been written to the object in question since 351 initialization. This value may not be used in a write operation. 353 clear 355 Clears all of the switch commands listed below for the specified 356 channel. 358 lockoutOfProtection 360 Prevents any of the working channels from switching to the protection 361 line. The specified channel should be the protection channel. 363 forcedSwitchWorkToProtect 365 Switches the specified working channel to the protection line. 367 forcedSwitchProtectToWork 369 Switches the working channel back from the protection 370 line to the working line. The specified channel should be 371 the protection channel. 373 manualSwitchWorkToProtect 375 Switches the specified working channel to the protection line. 377 manualSwitchProtectToWork 379 Switches the working channel back from the protection 380 line to the working line. The specified channel should be 381 the protection channel. 383 exercise 385 Exercises the protocol for a protection switch of the specified 386 channel by issuing an Exercise request for that channel and 387 checking the response on the APS channel. " 388 SYNTAX INTEGER { 389 noCmd(1), 390 clear(2), 391 lockoutOfProtection(3), 392 forcedSwitchWorkToProtect(4), 393 forcedSwitchProtectToWork(5), 394 manualSwitchWorkToProtect(6), 395 manualSwitchProtectToWork(7), 396 exercise(8) 397 } 399 ApsControlCommand ::= TEXTUAL-CONVENTION 400 STATUS current 401 DESCRIPTION 402 "An APS control command applies only to LTE that support the 403 1:n architecture and performs the following actions. 405 The Control command values are: 407 noCmd 409 This value should be returned by a read request when no control 410 command has been written to the object in question since 411 initialization. This value may not be used in a write operation. 413 lockoutWorkingChannel 415 Prevents the specified working channel from switching to the 416 protection line. 418 clearLockoutWorkingChannel 420 Clears the lockout a working channel command for the channel 421 specified. " 422 SYNTAX INTEGER { 423 noCmd(1), 424 lockoutWorkingChannel(2), 425 clearLockoutWorkingChannel(3) 426 } 428 -- 429 -- APS Configuration Table 430 -- 431 -- This table supports the addition, configuration and deletion of APS 432 -- groups. 433 -- 435 apsConfig OBJECT IDENTIFIER ::= { apsMIBObjects 1 } 437 apsConfigGroups OBJECT-TYPE 438 SYNTAX Gauge32 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "The count of APS groups. This count includes all rows in 443 apsConfigTable, regardless of the value of apsConfigRowStatus." 444 ::= { apsConfig 1 } 446 apsConfigTable OBJECT-TYPE 447 SYNTAX SEQUENCE OF ApsConfigEntry 448 MAX-ACCESS not-accessible 449 STATUS current 450 DESCRIPTION 451 "This table lists the APS groups that have been configured 452 on the system." 453 ::= { apsConfig 2 } 455 apsConfigEntry OBJECT-TYPE 456 SYNTAX ApsConfigEntry 457 MAX-ACCESS not-accessible 458 STATUS current 459 DESCRIPTION 460 "A conceptual row in the apsConfigTable." 461 INDEX { IMPLIED apsConfigName } 462 ::= { apsConfigTable 1 } 464 ApsConfigEntry ::= SEQUENCE { 465 apsConfigName SnmpAdminString, 466 apsConfigRowStatus RowStatus, 467 apsConfigMode INTEGER, 468 apsConfigRevert INTEGER, 469 apsConfigDirection INTEGER, 470 apsConfigExtraTraffic INTEGER, 471 apsConfigSdBerThreshold Integer32, 472 apsConfigSfBerThreshold Integer32, 473 apsConfigWaitToRestore Integer32, 474 apsConfigCreationTime TimeStamp, 475 apsConfigStorageType StorageType 476 } 478 apsConfigName OBJECT-TYPE 479 SYNTAX SnmpAdminString (SIZE (1..32)) 480 MAX-ACCESS not-accessible 481 STATUS current 482 DESCRIPTION 483 "A textual name for the APS group." 484 ::= { apsConfigEntry 1 } 486 apsConfigRowStatus OBJECT-TYPE 487 SYNTAX RowStatus 488 MAX-ACCESS read-create 489 STATUS current 490 DESCRIPTION 491 "The status of this APS group entry. 493 An entry may not exist in the active state unless all 494 objects in the entry have an appropriate value. Also, 495 all associated apsChanConfigEntry rows must represent 496 a set of consecutive channel numbers beginning with 497 0 or 1, depending on the selected architecture. 499 When set to notInService changes may be made to apsConfigMode, 500 apsConfigRevert, apsConfigDirection, apsConfigExtraTraffic, 501 apsConfigSdBerThreshold, apsConfigSfBerThreshold, 502 and apsConfigWaitToRestore. Also, associated apsChanConfigTable 503 objects may be added, deleted and modified." 504 ::= { apsConfigEntry 2 } 506 apsConfigMode OBJECT-TYPE 507 SYNTAX INTEGER { 508 onePlusOne(1), 509 oneToN(2), 510 onePlusOneCompatible(3), 511 onePlusOneOptimized(4) 512 } 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "The architecture of the APS group. 518 onePlusOne 519 The 1+1 architecture permanently bridges the working 520 line to the protection line. 522 oneToN 524 The 1:n architecture allows one protection channel to 525 protect up to n working channels. When a fault is detected 526 on one of the n working channels that channel is bridged 527 over the protection channel. 529 onePlusOneCompatible 531 This refers to 1 + 1 bidirectional switching compatible with 532 1:n bidirectional switching as specified in ITU-T 533 Recommendation G.783 (04/97) section A.3.4.1. Since this 534 mode necessitates bidirectional switching, apsConfigDirection 535 must be set to bidirectional whenever onePlusOneCompatible is set. 537 onePlusOneOptimized 539 This refers to 1 + 1 bidirectional switching optimized 540 for a network using predominantly 1 + 1 bidirectional 541 switching as specified in ITU-T Recommendation G.783 (04/97) 542 section B.1. Since this mode necessitates bidirectional 543 switching, apsConfigDirection must be set to bidirectional 544 whenever onePlusOneOptimized is set. 546 This object may not be modified if the associated 547 apsConfigRowStatus object is equal to active(1)." 548 DEFVAL {onePlusOne} 549 ::= { apsConfigEntry 3 } 551 apsConfigRevert OBJECT-TYPE 552 SYNTAX INTEGER { nonrevertive(1), revertive(2) } 553 MAX-ACCESS read-create 554 STATUS current 555 DESCRIPTION 556 "The revertive mode of the APS group. 558 nonrevertive 560 Traffic remains on the protection line until another switch 561 request is received. 563 revertive 565 When the condition that caused a switch to the protection 566 line has been cleared the signal is switched back to the 567 working line. Since switching is revertive with the 1:n 568 architecture, apsConfigRevert must be set to revertive if 569 apsConfigMode is set to oneToN. 571 Switching may optionally be revertive with the 1+1 architecture. 573 This object may not be modified if the associated 574 apsConfigRowStatus object is equal to active(1). " 575 DEFVAL { nonrevertive } 576 ::= { apsConfigEntry 4 } 578 apsConfigDirection OBJECT-TYPE 579 SYNTAX INTEGER { unidirectional(1), bidirectional(2) } 580 MAX-ACCESS read-create 581 STATUS current 582 DESCRIPTION 583 "The directional mode of the APS group. 585 unidirectional 587 The unidirectional mode provides protection in one direction. 589 bidirectional 591 The bidirectional mode provides protection in both 592 directions. 594 This object may not be modified if the associated 595 apsConfigRowStatus object is equal to active(1). " 596 DEFVAL {unidirectional} 597 ::= { apsConfigEntry 5 } 599 apsConfigExtraTraffic OBJECT-TYPE 600 SYNTAX INTEGER { enabled(1), disabled(2) } 601 MAX-ACCESS read-create 602 STATUS current 603 DESCRIPTION 604 "This object enables or disables the transfer of extra traffic 605 on the protection channel in a 1:n architecture. This object 606 must be set to disabled if the architecture is 1+1. It may be 607 necessary to disable this in order to interwork with other SONET 608 network elements that don't support extra traffic. 610 This object may not be modified if the associated 611 apsConfigRowStatus object is equal to active(1). " 612 DEFVAL { disabled } 613 ::= { apsConfigEntry 6 } 615 apsConfigSdBerThreshold OBJECT-TYPE 616 SYNTAX Integer32 (5..9) 617 MAX-ACCESS read-create 618 STATUS current 619 DESCRIPTION 620 "The Signal Degrade Bit Error Rate. 622 The negated value of this number is used as the exponent of 623 10 for computing the threshold value for the Bit Error Rate 624 (BER). For example, a value of 5 indicates a BER threshold of 625 10^-5. 627 This object may be modified if the associated 628 apsConfigRowStatus object is equal to active(1)." 629 DEFVAL { 5 } 630 ::= { apsConfigEntry 7 } 632 apsConfigSfBerThreshold OBJECT-TYPE 633 SYNTAX Integer32 (3..5) 634 MAX-ACCESS read-create 635 STATUS current 636 DESCRIPTION 637 "The Signal Failure Bit Error Rate. 639 The negated value of this number is used as the exponent of 640 10 for computing the threshold value for the Bit Error Rate 641 (BER). For example, a value of 5 indicates a BER threshold of 642 10^-5. 644 This object may be modified if the associated 645 apsConfigRowStatus object is equal to active(1)." 646 DEFVAL { 3 } 647 ::= { apsConfigEntry 8 } 649 apsConfigWaitToRestore OBJECT-TYPE 650 SYNTAX Integer32 (0..720) 651 UNITS "seconds" 652 MAX-ACCESS read-create 653 STATUS current 654 DESCRIPTION 655 "The Wait To Restore period in seconds. 657 After clearing of a condition that necessitated an 658 automatic switch, the wait to restore period must elapse 659 before reverting. This is intended to avoid rapid switch 660 oscillations. 662 GR-253-CORE specifies a Wait To Restore range of 5 to 12 663 minutes. G.783 defines a 5 to 12 minute Wait To Restore 664 range in section 5.4.1.1.3, but also allows for a shorter 665 WTR period in Table 2-1, 666 WaitToRestore value (MI_WTRtime: 0..(5)..12 minutes). 668 This object may not be modified if the associated 669 apsConfigRowStatus object is equal to active(1)." 670 DEFVAL { 300 } 671 ::= { apsConfigEntry 9 } 673 apsConfigCreationTime OBJECT-TYPE 674 SYNTAX TimeStamp 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "The value of sysUpTime at the time the row was 679 created" 680 ::= { apsConfigEntry 10 } 682 apsConfigStorageType OBJECT-TYPE 683 SYNTAX StorageType 684 MAX-ACCESS read-create 685 STATUS current 686 DESCRIPTION 687 "The storage type for this conceptual row. 688 Conceptual rows having the value 'permanent' need not 689 allow write-access to any columnar objects in the row." 690 DEFVAL { nonVolatile } 691 ::= { apsConfigEntry 11 } 693 -- 694 -- APS Status Table 695 -- 696 -- This table provides APS group statistics. 697 -- 699 apsStatusTable OBJECT-TYPE 700 SYNTAX SEQUENCE OF ApsStatusEntry 701 MAX-ACCESS not-accessible 702 STATUS current 703 DESCRIPTION 704 "This table provides status information about APS groups that have 705 been configured on the system." 707 ::= { apsMIBObjects 2 } 709 apsStatusEntry OBJECT-TYPE 710 SYNTAX ApsStatusEntry 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "A conceptual row in the apsStatusTable." 715 AUGMENTS { apsConfigEntry } 716 ::= { apsStatusTable 1 } 718 ApsStatusEntry ::= SEQUENCE { 719 apsStatusK1K2Rcv ApsK1K2, 720 apsStatusK1K2Trans ApsK1K2, 721 apsStatusCurrent BITS, 722 apsStatusModeMismatches Counter32, 723 apsStatusChannelMismatches Counter32, 724 apsStatusPSBFs Counter32, 725 apsStatusFEPLFs Counter32, 726 apsStatusSwitchedChannel Integer32, 727 apsStatusDiscontinuityTime TimeStamp 728 } 730 apsStatusK1K2Rcv OBJECT-TYPE 731 SYNTAX ApsK1K2 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The current value of the K1 and K2 bytes received on the 736 protection channel." 737 ::= { apsStatusEntry 1 } 739 apsStatusK1K2Trans OBJECT-TYPE 740 SYNTAX ApsK1K2 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "The current value of the K1 and K2 bytes transmitted on the 745 protection channel." 746 ::= { apsStatusEntry 2 } 748 apsStatusCurrent OBJECT-TYPE 749 SYNTAX BITS { 750 modeMismatch(0), 751 channelMismatch(1), 752 psbf(2), 753 feplf(3), 754 extraTraffic(4) 756 } 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "The current status of the APS group. 762 modeMismatch 764 Modes other than 1+1 unidirectional monitor protection line 765 K2 bit 5, which indicates the architecture and K2 bits 766 6-8, which indicate if the mode is unidirectional or 767 bidirectional. A conflict between the current local mode 768 and the received K2 mode information constitutes a 769 mode mismatch. 771 channelMismatch 773 This bit indicates a mismatch between the transmitted K1 channel 774 and the received K2 channel has been detected. 776 psbf 778 This bit indicates a Protection Switch Byte Failure (PSBF) is 779 in effect. This condition occurs when either an inconsistent 780 APS byte or an invalid code is detected. An inconsistent APS 781 byte occurs when no three consecutive K1 bytes of the last 12 782 successive frames are identical, starting with the last frame 783 containing a previously consistent byte. An invalid code occurs 784 when the incoming K1 byte contains an unused code or a code 785 irrelevant for the specific switching operation (e.g., Reverse 786 Request while no switching request is outstanding) in three 787 consecutive frames. An invalid code also occurs when the incoming 788 K1 byte contains an invalid channel number in three consecutive 789 frames. 791 feplf 793 Modes other than 1+1 unidirectional monitor the K1 byte 794 for Far-End Protection-Line failures. A Far-End 795 Protection-Line defect is declared based on receiving 796 SF on the protection line. 798 extraTraffic 800 This bit indicates whether extra traffic is currently being 801 accepted on the protection line. " 802 ::= { apsStatusEntry 3 } 804 apsStatusModeMismatches OBJECT-TYPE 805 SYNTAX Counter32 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "A count of Mode Mismatch conditions. 811 Discontinuities in the value of this counter can occur at 812 re-initialization of the management system, and at other 813 times as indicated by the value of 814 apsStatusDiscontinuityTime." 815 ::= { apsStatusEntry 4 } 817 apsStatusChannelMismatches OBJECT-TYPE 818 SYNTAX Counter32 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "A count of Channel Mismatch conditions. 824 Discontinuities in the value of this counter can occur at 825 re-initialization of the management system, and at other 826 times as indicated by the value of 827 apsStatusDiscontinuityTime." 828 ::= { apsStatusEntry 5 } 830 apsStatusPSBFs OBJECT-TYPE 831 SYNTAX Counter32 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "A count of Protection Switch Byte Failure conditions. 836 This condition occurs when either an inconsistent APS 837 byte or an invalid code is detected. An inconsistent APS 838 byte occurs when no three consecutive K1 bytes of the last 839 12 successive frames are identical, starting with the last 840 frame containing a previously consistent byte. An invalid 841 code occurs when the incoming K1 byte contains an unused 842 code or a code irrelevant for the specific switching operation 843 (e.g., Reverse Request while no switching request is outstanding) 844 in three consecutive frames. An invalid code also occurs 845 when the incoming K1 byte contains an invalid channel number 846 in three consecutive frames. 848 Discontinuities in the value of this counter can occur at 849 re-initialization of the management system, and at other 850 times as indicated by the value of 851 apsStatusDiscontinuityTime." 853 ::= { apsStatusEntry 6 } 855 apsStatusFEPLFs OBJECT-TYPE 856 SYNTAX Counter32 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "A count of Far-End Protection-Line Failure conditions. 861 This condition is declared based on receiving SF on 862 the protection line in the K1 byte. 864 Discontinuities in the value of this counter can occur at 865 re-initialization of the management system, and at other 866 times as indicated by the value of 867 apsStatusDiscontinuityTime." 868 ::= { apsStatusEntry 7 } 870 apsStatusSwitchedChannel OBJECT-TYPE 871 SYNTAX Integer32 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "This field is set to the number of the channel that is currently 876 switched to protection. The value 0 indicates no channel is 877 switched to protection. The values 1-14 indicate that working 878 channel is switched to protection." 879 ::= { apsStatusEntry 8 } 881 apsStatusDiscontinuityTime OBJECT-TYPE 882 SYNTAX TimeStamp 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The value of sysUpTime on the most recent occasion at which 887 any one or more of this APS group's counters suffered a 888 discontinuity. The relevant counters are the specific 889 instances associated with this APS group of any Counter32 890 object contained in apsStatusTable. If no such 891 discontinuities have occurred since the last re-initialization 892 of the local management subsystem, then this object contains 893 a zero value." 894 ::= { apsStatusEntry 9 } 896 -- 897 -- APS Map Group 898 -- 899 -- Lists the SONET LTE interfaces that may be used to create APS groups. 900 -- 901 apsMap OBJECT IDENTIFIER ::= { apsMIBObjects 3 } 903 apsChanLTEs OBJECT-TYPE 904 SYNTAX Gauge32 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "The count of SONET LTE interfaces on the system. 909 Each interface that is included has an ifType value of sonet(39)." 910 ::= { apsMap 1 } 912 apsMapTable OBJECT-TYPE 913 SYNTAX SEQUENCE OF ApsMapEntry 914 MAX-ACCESS not-accessible 915 STATUS current 916 DESCRIPTION 917 "This table lists the SONET LTE interfaces on the system. 918 Each interface that is listed has an ifType value of sonet(39)." 919 ::= { apsMap 2 } 921 apsMapEntry OBJECT-TYPE 922 SYNTAX ApsMapEntry 923 MAX-ACCESS not-accessible 924 STATUS current 925 DESCRIPTION 926 "A conceptual row in the apsMapTable." 927 INDEX { ifIndex } 928 ::= { apsMapTable 1 } 930 ApsMapEntry ::= SEQUENCE { 931 apsMapGroupName SnmpAdminString, 932 apsMapChanNumber Integer32 933 } 935 apsMapGroupName OBJECT-TYPE 936 SYNTAX SnmpAdminString (SIZE (0..32)) 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "A textual name for the APS group which this channel is 941 included in. If the channel is not part of an APS group 942 this value is set to a string of size 0. 944 When an instance of apsChanConfigIfIndex is set equal to an 945 instance of ifIndex that has an ifType value of sonet(39), 946 apsMapGroupName is set equal to the corresponding value of 947 apsChanConfigGroupName. 949 If an instance of ifIndex that has an ifType value of sonet(39) 950 ceases to be equal to an instance of apsChanConfigIfIndex, either 951 because of a change in the value of apsChanConfigIfIndex, or 952 because of row deletion in the ApsChanConfigTable, apsMapGroupName 953 is set to a string of size 0." 954 ::= { apsMapEntry 2 } 956 apsMapChanNumber OBJECT-TYPE 957 SYNTAX Integer32 (-1..14) 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "This field is set to a unique channel number within an APS group. 962 The value 0 indicates the null channel. The values 1-14 define a 963 working channel. If the SONET LTE is not part of an APS group this 964 value is set to -1. 966 When an instance of apsChanConfigIfIndex is set equal to an 967 instance of ifIndex that has an ifType value of sonet(39), 968 apsMapChanNumber is set equal to the corresponding value of 969 apsChanConfigNumber. 971 If an instance of ifIndex that has an ifType value of sonet(39) 972 ceases to be equal to an instance of apsChanConfigIfIndex, either 973 because of a change in the value of apsChanConfigIfIndex, or 974 because of row deletion in the ApsChanConfigTable, 975 apsMapChanNumber is set to -1." 976 ::= { apsMapEntry 3 } 978 -- 979 -- APS Channel Configuration Table 980 -- 981 -- This table supports the addition, configuration and deletion of channels 982 -- in APS groups. 983 -- 985 apsChanConfigTable OBJECT-TYPE 986 SYNTAX SEQUENCE OF ApsChanConfigEntry 987 MAX-ACCESS not-accessible 988 STATUS current 989 DESCRIPTION 990 "This table lists the APS channels that have been configured 991 in APS groups." 992 ::= { apsMIBObjects 4 } 994 apsChanConfigEntry OBJECT-TYPE 995 SYNTAX ApsChanConfigEntry 996 MAX-ACCESS not-accessible 997 STATUS current 998 DESCRIPTION 999 "A conceptual row in the apsChanConfigTable." 1000 INDEX {apsChanConfigGroupName, apsChanConfigNumber} 1001 ::= { apsChanConfigTable 1 } 1003 ApsChanConfigEntry ::= SEQUENCE { 1004 apsChanConfigGroupName SnmpAdminString, 1005 apsChanConfigNumber Integer32, 1006 apsChanConfigRowStatus RowStatus, 1007 apsChanConfigIfIndex InterfaceIndex, 1008 apsChanConfigPriority INTEGER, 1009 apsChanConfigStorageType StorageType 1010 } 1012 apsChanConfigGroupName OBJECT-TYPE 1013 SYNTAX SnmpAdminString (SIZE (1..32)) 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "A textual name for the APS group which this channel is 1018 included in." 1019 ::= { apsChanConfigEntry 1 } 1021 apsChanConfigNumber OBJECT-TYPE 1022 SYNTAX Integer32 (0..14) 1023 MAX-ACCESS not-accessible 1024 STATUS current 1025 DESCRIPTION 1026 "This field is set to a unique channel number within an APS group. 1027 The value 0 indicates the null channel. The values 1-14 define a 1028 working channel. 1030 This field must be assigned a unique number within the group." 1031 ::= { apsChanConfigEntry 2 } 1033 apsChanConfigRowStatus OBJECT-TYPE 1034 SYNTAX RowStatus 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "The status of this APS channel entry. 1040 An entry may not exist in the active state unless all 1041 objects in the entry have an appropriate value. 1043 A row in the apsChanConfigTable may not be created, 1044 deleted, set to notInService or otherwise modified 1045 if the apsChanConfigGroupName value is equal to an 1046 apsConfigName value and the associated apsConfigRowStatus 1047 object is equal to active. However, if the apsConfigRowStatus 1048 object is equal to notInService, a row may be created, deleted 1049 or modified. In other words, a channel may not be added, deleted 1050 or modified if the group is active. 1052 A row may be created with an apsChanConfigGroupName value 1053 that is not equal to any existing instance of apsConfigName. 1054 This action is the initial step in adding a SONET LTE to a 1055 new APS group. 1057 If this object is set to destroy, the associated instance 1058 of apsMapGroupName will be set to a string of size 0 and 1059 the apsMapChanNumber will be set to -1. The channel status 1060 entry will also be deleted by this action. 1062 apsChanConfigNumber must be set to a unique channel number within 1063 the APS group. The value 0 indicates the null channel. 1064 The values 1-14 define a working channel. When an attempt is 1065 made to set the corresponding apsConfigRowStatus field to 1066 active the apsChanConfigNumber values of all entries with equal 1067 apsChanConfigGroupName fields must represent a set of consecutive 1068 integer values beginning with 0 or 1, depending on the architecture 1069 of the group, and ending with n, where n is greater than or 1070 equal to 1 and less than or equal to 14. Otherwise, the error 1071 inconsistentValue is returned to the apsConfigRowStatus 1072 set attempt." 1073 ::= { apsChanConfigEntry 3 } 1075 apsChanConfigIfIndex OBJECT-TYPE 1076 SYNTAX InterfaceIndex 1077 MAX-ACCESS read-create 1078 STATUS current 1079 DESCRIPTION 1080 "The Interface Index assigned to a SONET LTE. This is an 1081 interface with ifType sonet(39). The value of this object 1082 must be unique among all instances of apsChanConfigIfIndex. 1083 In other words, a particular SONET LTE can only be configured in 1084 one APS group. 1086 This object cannot be set if the apsChanConfigGroupName instance 1087 associated with this row is equal to an instance of apsConfigName 1088 and the corresponding apsConfigRowStatus object is set to active. 1089 In other words this value cannot be changed if the APS group is 1090 active. However, this value may be changed if the apsConfigRowStatus 1091 value is equal to notInService." 1092 ::= { apsChanConfigEntry 4 } 1094 apsChanConfigPriority OBJECT-TYPE 1095 SYNTAX INTEGER {low(1), high(2)} 1096 MAX-ACCESS read-create 1097 STATUS current 1098 DESCRIPTION 1099 "The priority of the channel. 1101 This field deterimines whether high or low priority 1102 SD and SF codes are used in K1 requests. 1104 This field is only applicable if the channel is to be included in 1105 a group using the 1:n architecture. It is not applicable if the 1106 channel is to be included in a group using the 1+1 architecture, 1107 and is ignored in that case. 1109 This object cannot be set if the apsChanConfigGroupName instance 1110 associated with this row is equal to an instance of apsConfigName 1111 and the corresponding apsConfigRowStatus object is set to active. 1112 In other words this value cannot be changed if the APS group is 1113 active. However, this value may be changed if the 1114 apsConfigRowStatus value is equal to notInService." 1115 DEFVAL { low } 1116 ::= { apsChanConfigEntry 5 } 1118 apsChanConfigStorageType OBJECT-TYPE 1119 SYNTAX StorageType 1120 MAX-ACCESS read-create 1121 STATUS current 1122 DESCRIPTION 1123 "The storage type for this conceptual row. 1124 Conceptual rows having the value 'permanent' need not 1125 allow write-access to any columnar objects in the row." 1126 DEFVAL { nonVolatile } 1127 ::= { apsChanConfigEntry 6 } 1129 -- 1130 -- APS Command Table 1131 -- 1132 -- This table provides the ability to initiate APS commands. 1133 -- 1135 apsCommandTable OBJECT-TYPE 1136 SYNTAX SEQUENCE OF ApsCommandEntry 1137 MAX-ACCESS not-accessible 1138 STATUS current 1139 DESCRIPTION 1140 "This table allows commands to be sent to configured APS groups." 1141 ::= { apsMIBObjects 5 } 1143 apsCommandEntry OBJECT-TYPE 1144 SYNTAX ApsCommandEntry 1145 MAX-ACCESS not-accessible 1146 STATUS current 1147 DESCRIPTION 1148 "A conceptual row in the apsCommandTable. This row exists only if 1149 the associated apsConfigEntry is active." 1150 INDEX {apsChanConfigGroupName, apsChanConfigNumber} 1151 ::= { apsCommandTable 1 } 1153 ApsCommandEntry ::= SEQUENCE { 1154 apsCommandSwitch ApsSwitchCommand, 1155 apsCommandControl ApsControlCommand 1156 } 1158 apsCommandSwitch OBJECT-TYPE 1159 SYNTAX ApsSwitchCommand 1160 MAX-ACCESS read-write 1161 STATUS current 1162 DESCRIPTION 1163 "Allows the initiation of an APS switch command on the 1164 APS group and channel specified by the index values. 1166 If the APS switch command cannot be executed because an 1167 equal or higer priority request is in effect, an error 1168 is returned. 1170 When read this object returns the last command written 1171 or noCmd if no command has been written to this 1172 channel since initialization. The return of the last command 1173 written does not imply that this command is currently in effect. 1174 This request may have been preempted by a higher priority 1175 local or remote request. In order to determine the 1176 current state of the APS group it is necessary to read 1177 the objects apsStatusK1K2Rcv and apsStatusK1K2Trans. 1179 The value lockoutOfProtection should only be applied to the 1180 protection line channel since that switch command prevents any of 1181 the working channels from switching to the protection line. 1182 Following the same logic, forcedSwitchProtectToWork and 1183 manualSwitchProtectToWork should only be applied to the protection 1184 line channel. 1186 forcedSwitchWorkToProtect and manualSwitchWorkToProtect 1187 should only be applied to a working channel." 1188 ::= { apsCommandEntry 1 } 1190 apsCommandControl OBJECT-TYPE 1191 SYNTAX ApsControlCommand 1192 MAX-ACCESS read-write 1193 STATUS current 1194 DESCRIPTION 1195 "Allows the initiation of an APS control command on the 1196 APS group and channel specified by the index values. 1198 When read this object returns the last command written or 1199 noCmd if no command has been written to this channel since 1200 initialization. 1202 This object does not apply to the protection line." 1203 ::= { apsCommandEntry 2 } 1205 -- 1206 -- APS Channel Status Table 1207 -- 1208 -- This table provides APS channel statistics. 1209 -- 1211 apsChanStatusTable OBJECT-TYPE 1212 SYNTAX SEQUENCE OF ApsChanStatusEntry 1213 MAX-ACCESS not-accessible 1214 STATUS current 1215 DESCRIPTION 1216 "This table contains status information for all SONET LTE 1217 interfaces that are included in APS groups." 1218 ::= { apsMIBObjects 6 } 1220 apsChanStatusEntry OBJECT-TYPE 1221 SYNTAX ApsChanStatusEntry 1222 MAX-ACCESS not-accessible 1223 STATUS current 1224 DESCRIPTION 1225 "A conceptual row in the apsChanStatusTable." 1226 AUGMENTS { apsChanConfigEntry } 1227 ::= { apsChanStatusTable 1 } 1229 ApsChanStatusEntry ::= SEQUENCE { 1230 apsChanStatusCurrent BITS, 1231 apsChanStatusSignalDegrades Counter32, 1232 apsChanStatusSignalFailures Counter32, 1233 apsChanStatusSwitchovers Counter32, 1234 apsChanStatusLastSwitchover TimeStamp, 1235 apsChanStatusSwitchoverSeconds Counter32, 1236 apsChanStatusDiscontinuityTime TimeStamp 1237 } 1238 apsChanStatusCurrent OBJECT-TYPE 1239 SYNTAX BITS { 1240 lockedOut(0), 1241 sd(1), 1242 sf(2), 1243 switched(3), 1244 wtr(4) 1245 } 1246 MAX-ACCESS read-only 1247 STATUS current 1248 DESCRIPTION 1249 "Indicates the current state of the port. 1251 lockedOut 1253 This bit, when applied to a working channel, indicates that 1254 the channel is prevented from switching to the protection line. 1255 When applied to the null channel, this bit indicates that no 1256 working channel may switch to the protection line. 1258 sd 1260 A signal degrade condition is in effect. 1262 sf 1264 A signal failure condition is in effect. 1266 switched 1268 The switched bit is applied to a working channel if that 1269 channel is currently switched to the protection line. 1271 wtr 1273 A Wait-to-Restore state is in effect." 1274 ::= { apsChanStatusEntry 1 } 1276 apsChanStatusSignalDegrades OBJECT-TYPE 1277 SYNTAX Counter32 1278 MAX-ACCESS read-only 1279 STATUS current 1280 DESCRIPTION 1281 "A count of Signal Degrade conditions. This condition 1282 occurs when the line Bit Error Rate exceeds the currently 1283 configured value of the relevant instance of 1284 apsConfigSdBerThreshold. 1286 Discontinuities in the value of this counter can occur at 1287 re-initialization of the management system, and at other 1288 times as indicated by the value of 1289 apsChanStatusDiscontinuityTime." 1291 ::= { apsChanStatusEntry 2 } 1293 apsChanStatusSignalFailures OBJECT-TYPE 1294 SYNTAX Counter32 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "A count of Signal Failure conditions that have been 1299 detected on the incoming signal. This condition occurs 1300 when a loss of signal, loss of frame, AIS-L or a Line 1301 bit error rate exceeding the currently configured value of 1302 the relevant instance of apsConfigSfBerThreshold. 1304 Discontinuities in the value of this counter can occur at 1305 re-initialization of the management system, and at other 1306 times as indicated by the value of 1307 apsChanStatusDiscontinuityTime." 1309 ::= { apsChanStatusEntry 3 } 1311 apsChanStatusSwitchovers OBJECT-TYPE 1312 SYNTAX Counter32 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "When queried with index value apsChanConfigNumber other than 0, 1317 this object will return the number of times this channel has 1318 switched to the protection line. 1320 When queried with index value apsChanConfigNumber set to 0, 1321 which is the protection line, this object will return the 1322 number of times that any working channel has been switched 1323 back to the working line from this protection line. 1325 Discontinuities in the value of this counter can occur at 1326 re-initialization of the management system, and at other 1327 times as indicated by the value of 1328 apsChanStatusDiscontinuityTime." 1330 ::= { apsChanStatusEntry 4 } 1332 apsChanStatusLastSwitchover OBJECT-TYPE 1333 SYNTAX TimeStamp 1334 MAX-ACCESS read-only 1335 STATUS current 1336 DESCRIPTION 1337 "When queried with index value apsChanConfigNumber other than 0, 1338 this object will return the value of sysUpTime when this 1339 channel last completed a switch to the protection line. If this 1340 channel has never switched to the protection line, the value 1341 0 will be returned. 1343 When queried with index value apsChanConfigNumber set to 0, 1344 which is the protection line, this object will return the 1345 value of sysUpTime the last time that a working channel was 1346 switched back to the working line from this protection line. 1347 If no working channel has ever switched back to the working 1348 line from this protection line, the value 0 will be returned." 1349 ::= { apsChanStatusEntry 5 } 1351 apsChanStatusSwitchoverSeconds OBJECT-TYPE 1352 SYNTAX Counter32 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "The cumulative Protection Switching Duration (PSD) time in 1357 seconds. For a working channel, this is the cumulative number 1358 of seconds that service was carried on the protection line. 1359 For the protection line, this is the cumulative number of 1360 seconds that the protection line has been used to carry any 1361 working channel traffic. This information is only valid if 1362 revertive switching is enabled. The value 0 will be returned 1363 otherwise. 1365 Discontinuities in the value of this counter can occur at 1366 re-initialization of the management system, and at other 1367 times as indicated by the value of 1368 apsChanStatusDiscontinuityTime. For example, if the value 1369 of an instance of apsChanStatusSwitchoverSeconds changes 1370 from a non-zero value to zero due to revertive switching 1371 being disabled, it is expected that the corresponding 1372 value of apsChanStatusDiscontinuityTime will be updated 1373 to reflect the time of the configuration change. 1374 " 1375 ::= { apsChanStatusEntry 6 } 1377 apsChanStatusDiscontinuityTime OBJECT-TYPE 1378 SYNTAX TimeStamp 1379 MAX-ACCESS read-only 1380 STATUS current 1381 DESCRIPTION 1382 "The value of sysUpTime on the most recent occasion at which 1383 any one or more of this channel's counters suffered a 1384 discontinuity. The relevant counters are the specific 1385 instances associated with this channel of any Counter32 1386 object contained in apsChanStatusTable. If no such 1387 discontinuities have occurred since the last re-initialization 1388 of the local management subsystem, then this object contains 1389 a zero value." 1390 ::= { apsChanStatusEntry 7 } 1392 apsNotificationEnable OBJECT-TYPE 1393 SYNTAX BITS { 1394 switchover(0), 1395 modeMismatch(1), 1396 channelMismatch(2), 1397 psbf(3), 1398 feplf(4) 1399 } 1400 MAX-ACCESS read-write 1401 STATUS current 1402 DESCRIPTION 1403 "Provides the ability to enable and disable notifications 1404 defined in this MIB. 1406 switchover 1408 Indicates apsEventSwitchover notifications 1409 should be generated. 1411 modeMismatch 1413 Indicates apsEventModeMismatch notifications 1414 should be generated. 1416 channelMismatch 1418 Indicates apsEventChannelMismatch notifications 1419 should be generated. 1421 psbf 1423 Indicates apsEventPSBF notifications 1424 should be generated. 1426 feplf 1428 Indicates apsEventFEPLF notifications 1429 should be generated. " 1431 DEFVAL { { } } 1432 ::= { apsMIBObjects 7 } 1434 -- 1435 -- APS EVENTS 1436 -- 1438 apsNotificationsPrefix OBJECT IDENTIFIER 1439 ::= { apsMIBNotifications 0 } 1441 apsEventSwitchover NOTIFICATION-TYPE 1442 OBJECTS { apsChanStatusSwitchovers, apsChanStatusCurrent } 1443 STATUS current 1444 DESCRIPTION 1445 "An apsEventSwitchover notification is sent when the 1446 value of an instance of apsChanStatusSwitchovers increments." 1447 ::= { apsNotificationsPrefix 1 } 1449 apsEventModeMismatch NOTIFICATION-TYPE 1450 OBJECTS { apsStatusModeMismatches, apsStatusCurrent } 1451 STATUS current 1452 DESCRIPTION 1453 "An apsEventModeMismatch notification is sent when the 1454 value of an instance of apsStatusModeMismatches increments." 1455 ::= { apsNotificationsPrefix 2 } 1457 apsEventChannelMismatch NOTIFICATION-TYPE 1458 OBJECTS { apsStatusChannelMismatches, apsStatusCurrent } 1459 STATUS current 1460 DESCRIPTION 1461 "An apsEventChannelMismatch notification is sent when the 1462 value of an instance of apsStatusChannelMismatches increments." 1463 ::= { apsNotificationsPrefix 3 } 1465 apsEventPSBF NOTIFICATION-TYPE 1466 OBJECTS { apsStatusPSBFs, apsStatusCurrent } 1467 STATUS current 1468 DESCRIPTION 1469 "An apsEventPSBF notification is sent when the 1470 value of an instance of apsStatusPSBFs increments." 1471 ::= { apsNotificationsPrefix 4 } 1473 apsEventFEPLF NOTIFICATION-TYPE 1474 OBJECTS { apsStatusFEPLFs, apsStatusCurrent } 1475 STATUS current 1476 DESCRIPTION 1477 "An apsEventFEPLFs notification is sent when the 1478 value of an instance of apsStatusFEPLFs increments." 1480 ::= { apsNotificationsPrefix 5 } 1482 -- conformance information 1484 apsGroups OBJECT IDENTIFIER ::= { apsMIBConformance 1 } 1485 apsCompliances OBJECT IDENTIFIER ::= { apsMIBConformance 2 } 1487 apsFullCompliance MODULE-COMPLIANCE 1488 STATUS current 1489 DESCRIPTION 1490 "When this MIB is implemented with support for read-create, then 1491 such an implementation can claim read/write compliance. Linear APS 1492 groups can then be both monitored and configured with this MIB. 1494 Note that An agent is not required to process SNMP Set Requests that 1495 affect multiple control objects within this MIB. This is intended to 1496 simplify the processing of Set Requests for the various control 1497 tables by eliminating the possibility that a single Set PDU will 1498 contain multiple varbinds which are in conflict. " 1500 MODULE 1501 MANDATORY-GROUPS { apsConfigGeneral, apsStatusGeneral, apsChanGeneral } 1503 OBJECT apsConfigRowStatus 1504 SYNTAX INTEGER { active(1) } 1505 WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) } 1506 DESCRIPTION 1507 "Support for createAndWait and notInService is not required." 1509 OBJECT apsChanConfigRowStatus 1510 SYNTAX INTEGER { active(1) } 1511 WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) } 1512 DESCRIPTION 1513 "Support for createAndWait and notInService is not required." 1515 GROUP apsConfigWtr 1516 DESCRIPTION 1517 "Implementation of this group is optional for all 1518 linear APS implementations. The information is 1519 applicable to groups supporting a configurable 1520 WTR period." 1522 GROUP apsCommandOnePlusOne 1523 DESCRIPTION 1524 "Implementation of this group is optional for all 1525 linear APS implementations. The information is 1526 applicable to groups implementing the linear 1527 APS 1+1 architecture and supporting set operations." 1529 GROUP apsCommandOneToN 1530 DESCRIPTION 1531 "Implementation of this group is optional for all 1532 linear APS implementations. The information is 1533 applicable to groups implementing the linear 1534 APS 1:n architecture and supporting set operations." 1536 GROUP apsChanOneToN 1537 DESCRIPTION 1538 "Implementation of this group is optional for all 1539 linear APS implementations. The information is 1540 applicable to groups implementing the linear 1541 APS 1:n architecture." 1543 GROUP apsTotalsGroup 1544 DESCRIPTION 1545 "Implementation of this group is optional for all 1546 linear APS implementations." 1548 GROUP apsMapGroup 1549 DESCRIPTION 1550 "Implementation of this group is optional for all 1551 linear APS implementations." 1553 GROUP apsEventGroup 1554 DESCRIPTION 1555 "Implementation of this group is optional for all 1556 linear APS implementations." 1558 ::= { apsCompliances 1 } 1560 -- 1561 -- Read-Only Compliance 1562 -- 1564 apsReadOnlyCompliance MODULE-COMPLIANCE 1565 STATUS current 1566 DESCRIPTION 1567 "When this MIB is implemented without support for read-create 1568 (i.e. in read-only mode), then that implementation can claim 1569 read-only compliance. In that case, linear APS groups can be 1570 monitored but cannot be configured with this MIB." 1572 MODULE 1573 MANDATORY-GROUPS { apsConfigGeneral, apsStatusGeneral, apsChanGeneral } 1574 OBJECT apsConfigMode 1575 MIN-ACCESS read-only 1576 DESCRIPTION 1577 "Write access is not required." 1579 OBJECT apsConfigRevert 1580 MIN-ACCESS read-only 1581 DESCRIPTION 1582 "Write access is not required." 1584 OBJECT apsConfigDirection 1585 MIN-ACCESS read-only 1586 DESCRIPTION 1587 "Write access is not required." 1589 OBJECT apsConfigExtraTraffic 1590 MIN-ACCESS read-only 1591 DESCRIPTION 1592 "Write access is not required." 1594 OBJECT apsConfigSdBerThreshold 1595 MIN-ACCESS read-only 1596 DESCRIPTION 1597 "Write access is not required." 1599 OBJECT apsConfigSfBerThreshold 1600 MIN-ACCESS read-only 1601 DESCRIPTION 1602 "Write access is not required." 1604 OBJECT apsConfigWaitToRestore 1605 MIN-ACCESS read-only 1606 DESCRIPTION 1607 "Write access is not required." 1609 OBJECT apsConfigRowStatus 1610 SYNTAX INTEGER { active(1) } 1611 MIN-ACCESS read-only 1612 DESCRIPTION 1613 "Write access is not required, and active is the only status 1614 that needs to be supported." 1616 OBJECT apsConfigStorageType 1617 MIN-ACCESS read-only 1618 DESCRIPTION 1619 "Write access is not required." 1621 OBJECT apsChanConfigIfIndex 1622 MIN-ACCESS read-only 1623 DESCRIPTION 1624 "Write access is not required." 1626 OBJECT apsChanConfigPriority 1627 MIN-ACCESS read-only 1628 DESCRIPTION 1629 "Write access is not required." 1631 OBJECT apsChanConfigRowStatus 1632 SYNTAX INTEGER { active(1) } 1633 MIN-ACCESS read-only 1634 DESCRIPTION 1635 "Write access is not required, and active is the only status 1636 that needs to be supported." 1638 OBJECT apsChanConfigStorageType 1639 MIN-ACCESS read-only 1640 DESCRIPTION 1641 "Write access is not required." 1643 OBJECT apsNotificationEnable 1644 MIN-ACCESS read-only 1645 DESCRIPTION 1646 "Write access is not required." 1648 GROUP apsConfigWtr 1649 DESCRIPTION 1650 "Implementation of this group is optional for all 1651 linear APS implementations. The information is 1652 applicable to groups supporting a configurable 1653 WTR period." 1655 GROUP apsCommandOnePlusOne 1656 DESCRIPTION 1657 "Implementation of this group is optional for all 1658 linear APS implementations. The information is 1659 applicable to groups implementing the linear 1660 APS 1+1 architecture and supporting set operations." 1662 GROUP apsCommandOneToN 1663 DESCRIPTION 1664 "Implementation of this group is optional for all 1665 linear APS implementations. The information is 1666 applicable to groups implementing the linear 1667 APS 1:n architecture and supporting set operations." 1669 GROUP apsChanOneToN 1670 DESCRIPTION 1671 "Implementation of this group is optional for all 1672 linear APS implementations. The information is 1673 applicable to groups implementing the linear 1674 APS 1:n architecture." 1676 GROUP apsTotalsGroup 1677 DESCRIPTION 1678 "Implementation of this group is optional for all 1679 linear APS implementations." 1681 GROUP apsMapGroup 1682 DESCRIPTION 1683 "Implementation of this group is optional for all 1684 linear APS implementations." 1686 GROUP apsEventGroup 1687 DESCRIPTION 1688 "Implementation of this group is optional for all 1689 linear APS implementations." 1691 ::= { apsCompliances 2 } 1693 -- units of conformance 1695 apsConfigGeneral OBJECT-GROUP 1696 OBJECTS 1697 { 1698 apsConfigMode, 1699 apsConfigRevert, 1700 apsConfigDirection, 1701 apsConfigExtraTraffic, 1702 apsConfigSdBerThreshold, 1703 apsConfigSfBerThreshold, 1704 apsConfigCreationTime, 1705 apsConfigRowStatus, 1706 apsConfigStorageType, 1707 apsNotificationEnable 1708 } 1709 STATUS current 1710 DESCRIPTION 1711 "A collection of apsConfigTable objects providing configuration 1712 information applicable to all linear APS groups." 1713 ::= { apsGroups 1 } 1715 apsConfigWtr OBJECT-GROUP 1716 OBJECTS 1717 { 1718 apsConfigWaitToRestore 1719 } 1720 STATUS current 1721 DESCRIPTION 1722 "The apsConfigTable object that provides information which is 1723 applicable to groups supporting a configurable WTR period." 1724 ::= { apsGroups 2 } 1726 -- If set operations are not supported neither of the following two groups 1727 -- are implemented. If sets are supported only one of these groups is 1728 -- implemented for a linear APS group instance. 1730 apsCommandOnePlusOne OBJECT-GROUP 1731 OBJECTS 1732 { 1733 apsCommandSwitch 1734 } 1735 STATUS current 1736 DESCRIPTION 1737 "The apsCommandTable object which is applicable to groups 1738 implementing the linear APS 1+1 architecture. Also, set operations 1739 must be supported." 1740 ::= { apsGroups 3 } 1742 apsCommandOneToN OBJECT-GROUP 1743 OBJECTS 1744 { 1745 apsCommandSwitch, 1746 apsCommandControl 1747 } 1748 STATUS current 1749 DESCRIPTION 1750 "A collection of apsCommandTable objects which are applicable to 1751 groups implementing the linear APS 1:n architecture. Also, set 1752 operations must be supported." 1753 ::= { apsGroups 4 } 1755 apsStatusGeneral OBJECT-GROUP 1756 OBJECTS 1757 { 1758 apsStatusK1K2Rcv, 1759 apsStatusK1K2Trans, 1760 apsStatusCurrent, 1761 apsStatusModeMismatches, 1762 apsStatusChannelMismatches, 1763 apsStatusPSBFs, 1764 apsStatusFEPLFs, 1765 apsStatusSwitchedChannel, 1766 apsStatusDiscontinuityTime 1767 } 1768 STATUS current 1769 DESCRIPTION 1770 "A collection of apsStatusTable objects providing status information 1771 applicable to all linear APS groups." 1772 ::= { apsGroups 5 } 1774 apsChanGeneral OBJECT-GROUP 1775 OBJECTS 1776 { 1777 apsChanConfigIfIndex, 1778 apsChanConfigRowStatus, 1779 apsChanConfigStorageType, 1780 apsChanStatusCurrent, 1781 apsChanStatusSignalDegrades, 1782 apsChanStatusSignalFailures, 1783 apsChanStatusSwitchovers, 1784 apsChanStatusLastSwitchover, 1785 apsChanStatusSwitchoverSeconds, 1786 apsChanStatusDiscontinuityTime 1787 } 1788 STATUS current 1789 DESCRIPTION 1790 "A collection of channel objects providing information applicable to 1791 all linear APS channels." 1792 ::= { apsGroups 6 } 1794 apsChanOneToN OBJECT-GROUP 1795 OBJECTS 1796 { 1797 apsChanConfigPriority 1798 } 1799 STATUS current 1800 DESCRIPTION 1801 "The apsChanConfigTable object that provides information which is only 1802 applicable to groups implementing the linear APS 1:n architecture." 1803 ::= { apsGroups 7 } 1805 apsTotalsGroup OBJECT-GROUP 1806 OBJECTS 1807 { 1808 apsConfigGroups, 1809 apsChanLTEs 1810 } 1811 STATUS current 1812 DESCRIPTION 1813 "A collection of objects providing optional counts of configured APS 1814 groups and SONET LTE interfaces." 1815 ::= { apsGroups 8 } 1817 apsMapGroup OBJECT-GROUP 1818 OBJECTS 1819 { 1820 apsMapGroupName, 1821 apsMapChanNumber 1822 } 1823 STATUS current 1824 DESCRIPTION 1825 "A collection of apsMapTable objects providing a mapping 1826 from sonet(39) InterfaceIndex to group name and channel 1827 number for assigned APS channels and a list of unassigned 1828 sonet(39) interfaces." 1829 ::= { apsGroups 9 } 1831 apsEventGroup NOTIFICATION-GROUP 1832 NOTIFICATIONS {apsEventSwitchover, apsEventModeMismatch, 1833 apsEventChannelMismatch, apsEventPSBF, 1834 apsEventFEPLF } 1835 STATUS current 1836 DESCRIPTION 1837 "A collection of SONET linear APS notifications." 1838 ::= { apsGroups 10 } 1840 END 1842 5. Intellectual Property 1844 The IETF takes no position regarding the validity or scope of any 1845 intellectual property or other rights that might be claimed to 1846 pertain to the implementation or use of the technology described in 1847 this document or the extent to which any license under such rights 1848 might or might not be available; neither does it represent that it 1849 has made any effort to identify any such rights. Information on the 1850 IETF's procedures with respect to rights in standards-track and 1851 standards-related documentation can be found in BCP-11. Copies of 1852 claims of rights made available for publication and any assurances of 1853 licenses to be made available, or the result of an attempt made to 1854 obtain a general license or permission for the use of such 1855 proprietary rights by implementors or users of this specification can 1856 be obtained from the IETF Secretariat. 1858 6. Acknowledgments 1860 This document is a product of the AToMMIB Working Group. A number of 1861 constructs from a separate draft submission by Ken Chapman have been 1862 included here. Suggestions by Orly Nicklass, Faye Ly, Ron Carmona, 1863 Kaj Tesink, C. M. Heard, Muly Ilan, and Mickey Spiegel have been 1864 incorporated. A quality review was provided by Lauren Heintz 1865 and an IESG review by John Flick and Bert Wijnen. 1867 7. References 1869 [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for 1870 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1872 [2] Rose, M. and K. McCloghrie, "Structure and Identification of 1873 Management Information for TCP/IP-based Internets", STD 16, RFC 1874 1155, May 1990. 1876 [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, 1877 RFC 1212, March 1991. 1879 [4] Rose, M., "A Convention for Defining Traps for use with the 1880 SNMP", RFC 1215, March 1991. 1882 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1883 M. and S. Waldbusser, "Structure of Management Information 1884 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1886 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1887 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 1888 58, RFC 2579, April 1999. 1890 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1891 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 1892 58, RFC 2580, April 1999. 1894 [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 1895 Network Management Protocol", STD 15, RFC 1157, May 1990. 1897 [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1898 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 1900 [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1901 "Transport Mappings for Version 2 of the Simple Network 1902 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1904 [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1905 Processing and Dispatching for the Simple Network Management 1906 Protocol (SNMP)", RFC 2572, April 1999. 1908 [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) 1909 for version 3 of the Simple Network Management Protocol 1910 (SNMPv3)", RFC 2574, April 1999. 1912 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol 1913 Operations for Version 2 of the Simple Network Management 1914 Protocol (SNMPv2)", RFC 1905, January 1996. 1916 [14] Levi, D., Meyer, P. and B. Stewart, "SNMP Applications", RFC 1917 2573, April 1999. 1919 [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1920 Control Model (VACM) for the Simple Network Management Protocol 1921 (SNMP)", RFC 2575, April 1999. 1923 [16] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction 1924 to Version 3 of the Internet-standard Network Management 1925 Framework", RFC 2570, April 1999. 1927 [17] McCloghrie, K., and F. Kastenholz. "The Interfaces Group MIB", 1928 RFC 2863, June 2000. 1930 [18] GR-253-CORE Issue 2, December 1995, Revision 2, January 1999 1932 [19] ITU-T Recommendation G.783 (04/97) 1934 [20] K. Chapman, "Definitions of Managed Objects for SONET Linear 1935 Automatic Protection Switching (APS)", 1936 draft-kchapman-sonet-aps-00.txt, July 1999 1938 8.Security Considerations 1940 There are a number of management objects defined in this MIB 1941 that have a MAX-ACCESS clause of read-write and/or read-create. 1942 Such objects may be considered sensitive or vulnerable in some 1943 network environments. The support for SET operations in a 1944 non-secure environment without proper protection can have a 1945 negative effect on network operations. In particular, the APS command 1946 objects apsCommandSwitch and apsCommandControl and the APS configuration 1947 objects apsConfigRowStatus, apsConfigMode, apsConfigRevert, 1948 apsConfigDirection, apsConfigExtraTraffic, apsConfigSdBerThreshold, 1949 apsConfigSfBerThreshold, apsConfigWaitToRestore, apsConfigStorageType, 1950 apsChanConfigRowStatus, apsChanConfigIfIndex, apsChanConfigPriority, 1951 apsChanConfigStorageType and apsNotificationEnable have the potential 1952 of disrupting APS operations if set operations are performed with 1953 malicious intent. 1955 SNMPv1 by itself is not a secure environment. Even if the 1956 network itself is secure (for example by using IPSec), even then, 1957 there is no control as to who on the secure network is allowed 1958 to access and GET/SET (read/change/create/delete) the objects in 1959 this MIB. 1961 It is recommended that the implementers consider the security 1962 features as provided by the SNMPv3 framework. Specifically, the 1963 use of the User-based Security Model RFC 2574 [RFC2574] and the 1964 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1966 It is then a customer/user responsibility to ensure that the SNMP 1967 entity giving access to an instance of this MIB, is properly 1968 configured to give access to the objects only to those 1969 principals (users) that have legitimate rights to indeed GET or 1970 SET (change/create/delete) them. 1972 9. Editor's Address 1974 Jeff Johnson 1975 RedBack Networks. Inc. 1976 300 Holger Way 1977 San Jose, CA 95134-1362 1978 Phone: +1 408 750 5460 1979 Email: jeff@redback.com 1981 Michael Thatcher 1982 RedBack Networks. Inc. 1983 300 Holger Way 1984 San Jose, CA 95134-1362 1985 Phone: +1 408 750 5449 1986 Email: thatcher@redback.com 1988 Jim Kuhfeld 1989 RedBack Networks. Inc. 1990 300 Holger Way 1991 San Jose, CA 95134-1362 1992 Phone: +1 408 750 5465 1993 Email: jkuhfeld@redback.com 1995 10. Full Copyright Statement 1996 Copyright (C) The Internet Society (2002). All Rights Reserved. 1998 This document and translations of it may be copied and furnished 1999 to others, and derivative works that comment on or otherwise 2000 explain it or assist in its implmentation may be prepared, copied, 2001 published and distributed, in whole or in part, without 2002 restriction of any kind, provided that the above copyright notice 2003 and this paragraph are included on all such copies and derivative 2004 works. However, this document itself may not be modified in any 2005 way, such as by removing the copyright notice or references to the 2006 Internet Society or other Internet organizations, except as needed 2007 for the purpose of developing Internet standards in which case the 2008 procedures for copyrights defined in the Internet Standards 2009 process must be followed, or as required to translate it into 2010 languages other than English. 2012 The limited permissions granted above are perpetual and will not 2013 be revoked by the Internet Society or its successors or assigns. 2015 This document and the information contained herein is provided on 2016 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2017 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2018 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2019 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2020 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 2021 PURPOSE."