idnits 2.17.1 draft-chisholm-entmib-state-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 5) being 60 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction 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 7 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 7 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 204 has weird spacing: '...receive packe...' == Line 837 has weird spacing: '...for the purpo...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (October 2002) is 7863 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) == Missing Reference: 'RFC2863' is mentioned on line 192, but not defined == Unused Reference: 'RFC2021' is defined on line 798, but no explicit reference was found in the text == Unused Reference: 'RFC2274' is defined on line 802, but no explicit reference was found in the text == Unused Reference: 'RFC2275' is defined on line 806, but no explicit reference was found in the text == Unused Reference: 'RFC2119' is defined on line 810, but no explicit reference was found in the text == Unused Reference: 'RFC2262' is defined on line 816, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2021 (Obsoleted by RFC 4502) ** Obsolete normative reference: RFC 2274 (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2262 (Obsoleted by RFC 2272) Summary: 22 errors (**), 0 flaws (~~), 11 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Entity MIB Working Group S. Chisholm 2 Internet Draft Nortel Networks 3 Document: draft-chisholm-entmib-state-00.txt 4 Category: Standards Track 5 Expiration Date: April 2002 October 2002 7 Entity State MIB 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance 12 with all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as 17 Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- 22 Drafts as reference material or to cite them other than as 23 "work in progress." 25 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in the Internet community. 36 In particular, it describes extensions to the entity MIB to that 37 provide information about the state of the entity. 39 Table of Contents 41 1. The SNMP Management Framework 42 2. Entity State 43 2.1. State Relationships 44 2.2. Physical Classes and State 45 2.3. Relation to Alarm MIB 46 3. Definitions 47 4. Security Considerations 48 5. Author's Address 49 6. Acknowledgements 50 7. References 51 8. Full Copyright Statement 53 1. The SNMP Management Framework 55 The SNMP Management Framework presently consists of five major 56 components: 58 o An overall architecture, described in RFC 2571 [RFC2571]. 60 o Mechanisms for describing and naming objects and events for the 61 purpose of management. The first version of this Structure of 62 Management Information (SMI) is called SMIv1 and described in 63 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 64 1215 [RFC1215]. The second version, called SMIv2, is described 65 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 66 STD 58, RFC 2580 [RFC2580]. 68 o Message protocols for transferring management information. The 69 first version of the SNMP message protocol is called SNMPv1 and 70 described in STD 15, RFC 1157 [RFC1157]. A second version of 71 the SNMP message protocol, which is not an Internet standards 72 track protocol, is called SNMPv2c and described in RFC 1901 73 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 74 message protocol is called SNMPv3 and described in RFC 1906 75 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 77 o Protocol operations for accessing management information. The 78 first set of protocol operations and associated PDU formats is 79 described in STD 15, RFC 1157 [RFC1157]. A second set of 80 protocol operations and associated PDU formats is described in 81 RFC 1905 [RFC1905]. 83 o A set of fundamental applications described in RFC 2573 84 [RFC2573] and the view-based access control mechanism described 85 in RFC 2575 [RFC2575]. 87 A more detailed introduction to the current SNMP Management Framework 88 can be found in RFC 2570 [RFC2570]. 90 Managed objects are accessed via a virtual information store, termed 91 the Management Information Base or MIB. Objects in the MIB are 92 defined using the mechanisms defined in the SMI. 94 This memo specifies a MIB module that is compliant to the SMIv2. A 95 MIB conforming to the SMIv1 can be produced through the appropriate 96 translations. The resulting translated MIB must be semantically 97 equivalent, except where objects or events are omitted because no 98 translation is possible (use of Counter64). Some machine readable 99 information in SMIv2 will be converted into textual descriptions in 100 SMIv1 during the translation process. However, this loss of machine 101 readable information is not considered to change the semantics of the 102 MIB. 104 2. Entity State 106 The goal in adding state objects to the Entity MIB was to define a 107 useful subset of the possible state attributes that could be tracked 108 for a given entity that both fit into the existing IETF model, as 109 well as leveraged existing well deployed models. The entStateTable 110 contains state objects that are a subset of ITU's X.731 state 111 objects. Objects are defined to capture administrative, operational 112 and usage states. In addition there are further state objects 113 defined to provide additional information for these three basic 114 states. 116 Administrative state indicates permission to use or prohibition 117 against using the entity and is imposed through the management 118 services. The administrative state defined for an entity is 119 independent of administrative states in its containment hierarchy. 120 This means that administratively locking an entity does not 121 automatically lock its children in the containment hierarchy. 123 Operational state indicates whether or not the entity is physically 124 installed and working. The operational state defined for an entity 125 is indirectly dependent on the operational state of the entities in 126 which it is contained. If its parent entities in its containment 127 hierarchy are disabled, and therefore totally inoperable, then it is 128 unlikely that the given entity will be operable. 130 Usage state indicates whether or not the entity is in use at a 131 specific instance, and if so, whether or not it currently has spare 132 capacity. 134 The terms state and status are used interchangeably in this memo. 136 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 137 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 138 document are to be interpreted as described in RFC 2119. 140 2.1 State Relationships 142 The following section outlines all of the combinations of the three 143 basic states - administrative, operational and usage -and briefly 144 describes what each of these combinations of states means. It also 145 compare this combination of states to that of the ifAdminStatus and 146 ifOperStatus objects of the Interfaces Group MIB [RFC2863] to both 147 provide insight to those familiar with these status objects as well 148 as to clarify the relationship between entities and interfaces, as 149 indicated by entAliasLogicalIndexOrZero. 151 2.1.1 Admin State Locked, Operational State Disabled and Usage State Idle 153 The entity is totally inoperable, it is not servicing any users and 154 it is also administratively prohibited from use. To make it 155 available for use, both management permission and some corrective 156 action are necessary. This is similar to an ifAdminStatus of down 157 and ifOperStatus of down. 159 2.1.2 Admin State Locked, Operational State Enabled and Usage State Idle 161 The entity is partially or fully operable, it is not servicing any 162 users but is administratively prohibited from use. To make it 163 available for use, only management permission is required. This is 164 similar to an ifAdminStatus of down and ifOperStatus of down. 166 2.1.3 Admin State Shutting Down, Operational State Enabled and Usage State 167 Active 169 The entity is partially or fully operable and in use, but usage is 170 administratively limited to current instances of use. For an 171 additional user to gain access, management permission is required. 172 Otherwise, when all current users have terminated their use of the 173 resource, the managed object will automatically transit to the 174 locked, enabled, and idle state. This is similar to the situation 175 described in [RFC2863] where ifAdminStatus transitions to down, but 176 the ifOperStatus's transition does not occur immediately, but rather 177 after a small time lag to complete certain operations before going 178 "down". 180 2.1.4 Admin State Shutting Down, Operational State Enabled and Usage State 181 Busy 183 The entity is partially or fully operable and in use, but usage is 184 administratively limited to current instances of use. In addition, 185 it has no spare capacity to provide for additional users. For an 186 additional user to gain access, besides waiting for an existing user 187 to terminate, management permission is also required. Otherwise, 188 when all current users have terminated their use of the resource, 190 the managed object will automatically transit to the locked, 191 enabled, idle state. This is similar to the situation described in 192 [RFC2863] where ifAdminStatus transitions to down, but the 193 ifOperStatus's transition does not occur immediately, but rather 194 after a small time lag to complete certain operations before going 195 "down". 197 2.1.5 Admin State Unlocked, Operational State Enabled and Usage State Idle 199 The entity is partially or fully operable, it is not actually in use 200 and is not administratively prohibited from use. This is similar to 201 an ifAdminStatus of up and ifOperStatus of up if the interface is 202 able to pass packets. If the interface is found to be operable, but 203 the interface is waiting for other, external, events to occur 204 before it can transmit or receive packets, then this is similar to 205 an ifAdminStatus of up and a ifOperStatus of dormant. 207 2.1.6 Admin State Unlocked, Operational State Enabled and Usage State Active 209 The entity is partially or fully operable, it is currently in use 210 and is not 212 administratively prohibited from use. It has sufficient spare 213 capacity to provide for additional users. This is similar to an 214 ifAdminStatus of up and ifOperStatus of up. 216 2.1.7 Admin State Unlocked, Operational State Enabled and Usage State Busy 218 The entity is partially or fully operable, it is currently in use 219 and it is not administratively prohibited from use. Currently it has 220 no spare capacity to provide for additional users. For an additional 221 user to gain access, it is necessary to wait for an existing user to 222 terminate or for some capacity increase to occur. This is similar 223 to an ifAdminStatus of up and ifOperStatus of up. 225 2.1.8 Admin State Unlocked, Operational State Disabled and Usage State Idle 227 The entity is totally inoperable, it is servicing no users but it is 228 not administratively prohibited from use. To make it available for 229 use, some corrective action is required. This is similar to an 230 ifAdminStatus of up and ifOperStatus of down. If the cause of the 231 interface being down is because of a lower layer being down, then 232 this is similar to an ifAdminStatus of up and an ifOperStatus of 233 lowerLayerDown. 235 2.2 Physical Classes and States 237 2.2.1 Chassis 239 A value of unlocked for entStateAdmin means that this system is on. 240 A value of shuttingDown for entStateAdmin means that this system is 241 in the process of shutting down. A value of enabled for entStateOper 242 indicates that basic functions of this system are functioning. A 243 value of disabled for entStateOper indicates a problem with basic 244 functions on the system. A value of idle for entStateUsage may not 245 make sense since responding to a SNMP query may constitute service. 246 A value of active for entStateUsage indicates the system is 247 functioning, but is able to provide more services. A value of busy 248 for entStateUsage indicates that the system is functioning at 249 maximum capacity and is unable to provide more services at the 250 present time. 252 A value of hotStandby for enStateStandby indicates that the entire 253 system contained within this chassis is running as a hot standby for 254 another complete system, possibly contained within the same stack. A 255 value of coldStandby for enStateStandby indicates that the entire 256 system contained within this chassis is running as a cold standby 257 for another complete system, possibly contained within the same 258 stack. A value of providingService for enStateStandby indicates that 259 the entire system contained within this chassis is currently 260 providing service. 262 If this chassis is not contained in within a stack, the alarm counts 263 indicated by entStateAlarm will be those alarms that are against the 264 general system, as appose sub-components within the containment 265 hierarchy. 267 2.2.2 BackPlane 269 A value of unlocked for entStateAdmin means that the backplane is 270 not administratively prevented from aggregating and forwarding 271 network traffic. A value of shutting down for entStateAdmin means 272 that the backplane will finish aggregating and forwarding the 273 network traffic is currently handling, but then transition to be 274 administratively locked. A value of locked for entStateAdmin means 275 that backplane is administratively prohibited from aggregating and 276 forwarding any network traffic. A value of enabled for entStateOper 277 means that the backplane is partially or fully capable of 278 aggregating and forwarding network traffic. A value of disabled for 279 entStateOper means that the backplane is unable to aggregate and 280 forward any network traffic. A value of idle for entStateUsage means 281 that the backplane is not currently aggregating and forwarding any 282 network traffic. A value of active for entStateUsage means that the 283 backplane is currently aggregating and forwarding some network 284 traffic, but has capacity to handle more traffic. A value of busy 285 for entStateUsage means that the backplane is aggregating and 286 forwarding network traffic at full capacity. 288 A value of hotStandby for enStateStandby indicates that the 289 backplane is running as a hot standby for another backplane within 290 this system. A value of coldStandby for enStateStandby indicates 291 that the backplane is running as a cold standby for another 292 backplane, possibly within this system. A value of providingService 293 for enStateStandby indicates that the backplane is currently 294 providing service. Looking at the entStateAlarm gives a convenient 295 way to see if there are any alarms currently active against this 296 backplane. 298 2.2.3 Container 300 A value of unlocked for entStateAdmin means it is administratively 301 possible to insert things into this container. A value of 302 shuttingDown for entStateAdmin could be used to reflect that 303 inserting objects into this container is administratively 304 prohibited. This value could also be used for systems that do not 305 support hot insertion of components. 307 The container physical class could be used to indicate, among other 308 things, chassis slots or daughter-card holders. If the container is 309 empty, for example it has no modules in its slots, then 310 entStateUsage would have a value of idle. If the container is 311 partially used, for example it has modules in some but now all of 312 its slots, then entStateUsage would have a value of busy. If the 313 container is full, for example it has no empty slots, then 314 entStateUsage would have a value of busy. 316 If it is not possible to raise alarms against this chassis, the 317 entStateAlarm will have no alarms set. It may not make sense for the 318 entStateOper to have values other than enabled. 320 2.2.4 PowerSupply 322 If this power supply is the currently providing power to the system, 323 then entStateStandyby would have a value of providing service. If 324 this power supply is serving as a backup to a primary power supply, 325 then entStateStandyby would have a value of hotstandby. 327 A value of locked for entStateAdmin means that the power supply has 328 been turned off. This only makes sense in the situation where there 329 is a backup power supply. A value of unlocked for entStateAdmin 330 means that the power supply is turned on. A value of enabled for 331 entStateOper means that the power supply is operational. A value of 332 disabled for entStateOper means that the power supply is not 333 functioning. A value of idle for entStateUsage means that the power 334 supply is providing no power to the system. A value of active for 335 entStateUsage means that the power supply is providing power to the 336 system, but could possibly provide more. A value of busy for 337 entStateUsage means that the power supply is providing the maximum 338 power to the system that it is capable of. Looking at the 339 entStateAlarm gives a convenient way to see if there are any alarms 340 currently active against this power supply. 342 2.2.5 Fan 344 If this fan is serving as a backup to a primary fan, then 345 entStateStandyby would have a value of hotstandby. If this fan is 346 the currently providing service to the system, then entStateStandyby 347 would have a value of providing service. A value of idle for 348 entStateUsage would indicate that the fan was not actually running. 349 A value of active for entStateUsage would indicate that the fan was 350 running, but not at its maximum capacity. A value of busy for 351 entStateUsage would indicate that the fan was running at maximum 352 capacity. 354 Looking at the entStateAdmin and entStateOper provide useful 355 information to determine why a fan is not running. A value of locked 356 for entStateAdmin means that the fan is not running because it has 357 been administratively disabled. A value of disabled for the 358 entOperStatus indicates that the fan itself is not operational. A 359 value of enabled for the entOperStatus indicates that the fan is 360 working in theory and that cause of it not operator may lie 361 elsewhere. Looking at the entStateAlarm gives a convenient way to 362 see if there are any alarms currently active against this fan. 364 2.2.6 Sensor 366 A value of unlocked for entStateAdmin indicates that the sensor is 367 not administratively prohibited from sensing. A value of shutting 368 down for entStateAdmin indicates that the sensor will complete its 369 current readings and then shut down. A value of locked for 370 entStateAdmin indicates that the sensor is administratively 371 prohibited from sensing. A value of enabled for entStateOper 372 indicates that the sensor is functioning properly. A value of 373 disable for entStateOper indicates that the sensor is totally 374 inoperable. A value of idle for entStateUsage indicates that the 375 sensor is not currently sensing. A value of active for entStateUsage 376 indicates that the sensor is currently sensing things, but could 377 sense more, more often or other types of information for example. A 378 value of busy for entStateUsage indicates that the sensor is sensing 379 everything it knows how to sense and at its fastest possible rate. 381 Looking at the entStateStandby indicates whether this sensor is 382 currently providing service or acting as a backup for another 383 sensor. Looking at the entStateAlarm gives a convenient way to see 384 if there are any alarms currently active against this sensor. 386 2.2.7 Module 388 For modules that support the functionality of being administratively 389 disabled, entStateAdmin object indicates whether the module is 390 administratively locked (disabled) or unlocked (enabled). Modules 391 that do not support disabling will always have a value of unlocked 392 for entStateAdmin. A value of enabled for entStateOper indicates 393 that this module is partially or fully operational. A value of 394 disabled for entStateOper indicates that this module is totally 395 inoperable. A value of idle for entStateUsage indicates that this 396 module is currently not performing any functions. A value of active 397 entStateUsage indicates that this module is currently performing 398 functions, but capable of performing more. A value of busy for 399 entStateUsage indicates that the module is functioning at full 400 capacity and unable to perform further functions at this current 401 time. 403 Looking at the entStateStandby indicates whether this module is 404 currently providing service or acting as a backup for another 405 module. Looking at the entStateAlarm gives a convenient way to see 406 if there are any alarms currently active against this module. 408 2.2.8 Port 410 A value of enabled for entStateAdmin means the port is not 411 administratively prohibited from passing network traffic. A value of 412 shutting down for entStateAdmin indicates that the port will pass 413 its current traffic and then transition to the locked state. A value 414 of locked for entStateAdmin indicates that the port is 415 administratively prohibited from passing network traffic. A value of 416 enabled for entStateOper means that the port is partially or fully 417 capable of forwarding network traffic. A value of disabled for 418 entStateOper means that the port is totally unable to forward 419 network traffic. A value of idle for entStateUsage indicates that 420 the port is not currently forwarding any network traffic. A value of 421 active means that the port is currently forwarding network traffic, 422 but has capacity to forward more. A value of busy for entStateUsage 423 indicates that the port is forwarding network traffic at its maximum 424 capacity. 426 Looking at the entStateStandby indicates whether this port is 427 currently providing service or acting as a backup for another port. 428 Looking at the entStateAlarm gives a convenient way to see if there 429 are any alarms currently active against this port. 431 2.2.9 Stack 433 A value of unlocked for entStateAdmin means that this system is on. 434 A value of shuttingDown for entStateAdmin means that this system is 435 in the process of shutting down. A value of enabled for entStateOper 436 indicates that basic functions of this system are functioning. A 437 value of disabled for entStateOper indicates a problem with basic 438 functions on the system. A value of idle for entStateUsage may not 439 make sense since responding to a SNMP query may constitute service. 440 A value of active for entStateUsage indicates the system is 441 functioning, but is able to provide more services. A value of busy 442 for entStateUsage indicates that the system is functioning at 443 maximum capacity and is unable to provide more services at the 444 present time. 446 A value of hotStandby for enStateStandby indicates that the entire 447 system contained within this stack is running as a hot standby for 448 another complete system, possibly contained within the same parent 449 stack. A value of coldStandby for enStateStandby indicates that the 450 entire system contained within this stack is running as a cold 451 standby for another complete system, possibly contained within the 452 same parent stack. A value of providingService for enStateStandby 453 indicates that the entire system contained within this chassis is 454 currently providing service. 456 If this stack is not contained in within a parent stack, the alarm 457 counts indicated by entStateAlarm will be those alarms that are 458 against the general system, as appose sub-components within the 459 containment hierarchy. 461 2.3 Relation to Alarm MIB 463 The entStateAlarm object indicates whether or not there are any 464 active alarms against this entity. If there are active alarms, then 465 the alarmActiveTable should be searched for alarmActiveResourceId 466 that match this entPhysicalIndex 468 3. Definitions 470 ENTITY-STATE-MIB DEFINITIONS ::= BEGIN 472 IMPORTS 473 MODULE-IDENTITY, Unsigned32, mib-2 474 FROM SNMPv2-SMI 475 TEXTUAL-CONVENTION, DisplayString, TruthValue 476 FROM SNMPv2-TC; 478 entityStateMIB MODULE-IDENTITY 479 LAST-UPDATED "200210260000Z" 480 ORGANIZATION "IETF Entity MIB Working Group" 481 CONTACT-INFO 482 " Sharon Chisholm 483 Nortel Networks 484 PO Box 3511 Station C 485 Ottawa, Ont. K1Y 4H7 486 Canada 487 schishol@nortelnetworks.com 488 " 489 DESCRIPTION 490 "This MIB defines a state extension to the entity MIB " 491 REVISION "200210260000Z" 492 DESCRIPTION 493 "" 494 ::= { mib-2 xx } 496 -- Textual conventions 498 ItuAdminState ::= TEXTUAL-CONVENTION 499 STATUS current 500 DESCRIPTION 501 " Represents the various possible administrative states 502 (ITU-T X.731). 504 A value of locked means the resource is administratively 505 prohibited from use. A value of shuttingDown means that 506 usage is administratively limited to current instances of 507 use. A value of unlocked means the resource is not 508 administratively prohibited from use." 509 SYNTAX INTEGER 510 { 511 locked(1), 512 shuttingDown(2), 513 unlocked(3) 514 } 516 ItuOperState ::= TEXTUAL-CONVENTION 517 STATUS current 518 DESCRIPTION 519 " Represents the possible values of operational states 520 (ITU-T X.731). 522 A value of disabled means the resource is totally 523 inoperable. A value of enabled means the resource 524 is partially or fully operable." 525 SYNTAX INTEGER 526 { 527 disabled(1), 528 enabled(2) 529 } 531 ItuUsageState ::= TEXTUAL-CONVENTION 532 STATUS current 533 DESCRIPTION 534 " Represents the possible values of usage states 535 (ITU-T X.731). 537 A value of idle means the resource is servicing no users. 538 A value of active means the resource is currently in use 539 and it has sufficient spare capacity to provide for 540 additional users. A value of busy means the resource is 541 currently in use, but it currently has no spare capacity 542 to provide for additional users." 543 SYNTAX INTEGER 544 { 545 idle(1), 546 active(2), 547 busy(3) 548 } 550 ItuAlarmStatus ::= TEXTUAL-CONVENTION 551 STATUS current 552 DESCRIPTION 553 " Represents the possible values of alarm status 554 (ITU-T X.731). 556 When no values of this attribute are set, then none of the 557 status conditions described below are present. When the 558 value of under repair is set, the resource is currently 559 being repaired. 561 When the value of critical is set, one or more critical 562 alarms are active against the resource. When the value of 563 major is set, one or more major alarms are active against 564 the resource. When the value of minor is set, one or more 565 minor alarms are active against the resource. 567 When the value of alarm outstanding is set,one or more 568 alarms is active against the resource. The fault may or may 569 not be disabling. " 570 SYNTAX BITS 571 { 572 underRepair(1), 573 critical(2), 574 major(3), 575 minor(4), 576 alarmOutstanding(5), 577 warning (6), -- Not defined in X.731 578 indeterminate (7) -- Not defined in X.731 579 } 581 ItuStandbyStatus ::= TEXTUAL-CONVENTION 582 STATUS current 583 DESCRIPTION 584 " Represents the possible values of standby status 585 (IU-T X.731). 587 A value of hotStandby means the resource is not providing 588 service, but is will be immediately able to take over the 589 role of the resource to be backed-up, without the need for 590 initialization activity, and will contain the same 591 information as the resource to be backed up. A value of 592 coldStandy means that the resource is to back-up another 593 resource, but will not be immediately able to take over 594 the role of a resource to be backed up, and will require 595 some initialization activity. A value of providingService 596 means the resource is providing service. 597 " 599 SYNTAX INTEGER 600 { 601 hotStandby(1), 602 coldStandby(2), 603 providingService(3) 604 } 606 -- Entity State Objects 608 entStateObjects OBJECT IDENTIFIER ::= { entityStateMIB 1 } 610 entStateTable OBJECT-TYPE 611 SYNTAX SEQUENCE OF EntStateEntry 612 MAX-ACCESS not-accessible 613 STATUS current 614 DESCRIPTION 615 "A table of information about state/status of entities. 616 " 617 ::= { entStateObjects 1 } 619 entStateEntry OBJECT-TYPE 620 SYNTAX EntStateEntry 621 MAX-ACCESS not-accessible 622 STATUS current 623 DESCRIPTION "" 624 AUGMENTS { entPhysicaEntry } 625 ::= { entStateTable 1 } 627 EntStateEntry ::= SEQUENCE { 628 entStateAdmin ItuAdminState, 629 entStateOper ItuOperState, 630 entStateUsage ItuUsageState, 631 entStateAlarm ItuAlarmStatus, 632 entStateStandby ItuStandbyStatus 633 } 635 entStateAdmin OBJECT-TYPE 636 SYNTAX ItuAdminState 637 MAX-ACCESS read-write 638 STATUS current 639 DESCRIPTION 640 "The administrative state for this entity." 641 ::= { entStateEntry 1 } 643 entStateOper OBJECT-TYPE 644 SYNTAX ItuOperState 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "The operational state for this entity." 649 ::= { entStateEntry 2 } 651 entStateUsage OBJECT-TYPE 652 SYNTAX ItuUsageState 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "The usage state for this entity." 657 ::= { entStateEntry 3 } 659 entStateAlarm OBJECT-TYPE 660 SYNTAX ItuAlarmStatus 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION 664 "The alarm state for this entity. It does not include 665 the severity of alarms raised on child components." 666 ::= { entStateEntry 4 } 668 entStateStandby OBJECT-TYPE 669 SYNTAX ItuStandbyStatus 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "" 674 ::= { entStateEntry 5 } 676 -- Conformance and Compliance 678 entStateConformance OBJECT IDENTIFIER ::= { entityStateMIB 3 } 680 entStateCompliances OBJECT IDENTIFIER 681 ::= { entStateConformance 1 } 683 entStateCompliance MODULE-COMPLIANCE 684 STATUS current 685 DESCRIPTION 686 "The compliance statement for systems supporting 687 the snmpXProto MIB." 688 MODULE -- this module 689 MANDATORY-GROUPS { 690 entStateGroups 691 } 692 ::= { entStateCompliances 1 } 694 entStateGroups OBJECT IDENTIFIER ::= { entStateConformance 2 } 696 entStateGroup OBJECT-GROUP 697 OBJECTS { 698 entStateAdmin, 699 entStateOper, 700 entStateUsage, 701 entStateAlarm, 702 entStateStandby 703 } 704 STATUS current 705 DESCRIPTION 706 "Standard Entity State group." 707 ::= { entStateGroups 1} 709 END 711 4. Security Considerations 713 There are no management objects defined in this MIB that have a 714 MAX-ACCESS clause of read-write and/or read-create. So, if this MIB 715 is implemented correctly, then there is no risk that an intruder can 716 alter or create any management objects of this MIB via direct SNMP 717 SET operations. 719 5. Author's Address 721 Sharon Chisholm 722 Nortel Networks 723 PO Box 3511, Station C 724 Ottawa, Ontario, K1Y 4H7 725 Canada 726 Email: schishol@nortelnetworks.com 728 6. Acknowledgments 730 This document is a product of the Entity MIB Group. 731 ... 733 7. References 735 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 736 Architecture for Describing SNMP Management Frameworks", 737 RFC 2571, April 41999. 739 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 740 of Management Information for TCP/IP-based Internets", STD 741 16, RFC 1155, May 1990. 743 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 744 STD 16, RFC 1212, March 1991. 746 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 747 SNMP", RFC 1215, March 1991. 749 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 750 Rose, M., and S. Waldbusser, "Structure of Management 751 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 752 1999. 754 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 755 Rose, M., and S. Waldbusser, "Textual Conventions for 756 SMIv2", STD 58, RFC 2579, April 1999. 758 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 759 Rose, M., and S. Waldbusser, "Conformance Statements for 760 SMIv2", STD 58, RFC 2580, April 1999. 762 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 763 "Simple Network Management Protocol", STD 15, RFC 1157, 764 May 1990. 766 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 767 "Introduction to Community-based SNMPv2", RFC 1901, 768 January 1996. 770 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 771 "Transport Mappings for Version 2 of the Simple Network 772 Management Protocol (SNMPv2)", RFC 1906, January 1996. 774 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 775 "Message Processing and Dispatching for the Simple 776 Network Management Protocol (SNMP)", RFC 2572, April 777 1999. 779 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 780 (USM) for version 3 of the Simple Network Management 781 Protocol (SNMPv3)", RFC 2574, April 1999. 783 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 784 "Protocol Operations for Version 2 of the Simple Network 785 Management Protocol (SNMPv2)", RFC 1905, January 1996. 787 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 788 Applications", RFC 2573, April 1999. 790 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 791 Access Control Model (VACM) for the Simple Network 792 Management Protocol (SNMP)", RFC 2575, April 1999. 794 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 795 "Introduction to Version 3 of the Internet-standard 796 Network Management Framework", RFC 2570, April 1999. 798 [RFC2021] Waldbusser, S. "Remote Network Monitoring Management 799 Information Base Version 2 using SMIv2", RFC 2021, 800 January 1997 802 [RFC2274] Blumenthal, U. and B. Wijnen, "User-based Security 803 Model (USM) for version 3 of the Simple Network Management 804 Protocol (SNMPv3)", RFC 2274, January 1998. 806 [RFC2275] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 807 Access Control Model (VACM) for the Simple Network 808 Management Protocol (SNMP)", RFC 2275, January 1998. 810 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 811 Requirement Levels", BCP 14, RFC 2119, March 1997. 813 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 814 "Protocol Operations for SNMPv2", RFC 1905, January 1996 816 [RFC2262] Case, J., Harrington, D, Presuhn, R., Wijnen, B., 817 "Message Processing and Dispatching for the 818 Simple Network Management Protocol (SNMP)", RFC 2262, 819 January 1998 821 [X.731] ITU Recommendation X.731, "Information Technology - Open 822 Systems Interconnection - System Management: State 823 Management Function", 1992 825 8. Full Copyright Statement 827 Copyright (C) The Internet Society (2002). All Rights Reserved. 829 This document and translations of it may be copied and furnished to 830 others, and derivative works that comment on or otherwise explain it 831 or assist in its implementation may be prepared, copied, published 832 and distributed, in whole or in part, without restriction of any kind, 833 provided that the above copyright notice and this paragraph are 834 included on all such copies and derivative works. However, this 835 document itself may not be modified in any way, such as by removing 836 the copyright notice or references to the Internet Society or other 837 Internet organizations, except as needed for the purpose of 838 developing Internet standards in which case the procedures for 839 copyrights defined in the Internet Standards process must be followed, 840 or as required to translate it into languages other than English. 842 The limited permissions granted above are perpetual and will not be 843 revoked by the Internet Society or its successors or assigns. 845 This document and the information contained herein is provided on an 846 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 847 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 848 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 849 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 850 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.