NTCIP1201-Global DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY FROM SNMPv2-SMI -- RFC 2578 devices, deviceAdmin FROM NTCIP8004-Transportation; global MODULE-IDENTITY LAST-UPDATED "202212120500Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION "This MIB defines the structure of management information under the global node. In particular, it defines the global and globalAdmin nodes that are used by other MIBs contained in NTCIP 1201. 1.3.6.1.4.1.1206.4.2.6 Copyright (C) 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202212120500Z" DESCRIPTION "NTCIP 1201 v04 - The first version of the NTCIP1201-Global MIB. The nodes defined within this MIB were previously defined in NTCIP1201- v03 in SMIv1 format. " ::= { devices 6 } -- 2.2 NODE DEFINITIONS adminGlobal OBJECT-IDENTITY STATUS current DESCRIPTION "A node used to group NTCIP 1201 objects that should only be accessible by users with administrator rights. Grouping these objects under the administrator node allows easy configuration of access control rights. 1.3.6.1.4.1.1206.4.2.126.6" ::= { deviceAdmin 6 } globalV2 OBJECT-IDENTITY STATUS current DESCRIPTION "A node used to group the MIBs associated with the second major version of global objects. 1.3.6.1.4.1.1206.4.2.6.9" ::= { global 9 } adminGlobalV2 OBJECT-IDENTITY STATUS current DESCRIPTION "A node used to group globalV2 objects that should only be accessible by users with administrator rights. 1.3.6.1.4.1.1206.4.2.126.6.9" ::= { adminGlobal 9 } END --NTCIP1201-Global -- Section 3 -- 3.1 DATABASE MANAGEMENT MIB HEADER NTCIP1201-DbMgmtV2 DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC 3411 globalV2, adminGlobalV2 FROM NTCIP1201-Global; dbMgmtV2 MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION "This MIB defines a mechanism to allow a manager to modify a potentially large number of interrelated configuration parameters within a field device as a single operation. 1.3.6.1.4.1.1206.4.2.6.9.1 Copyright 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - The first version of the NTCIP1201-DbMgmtV2 MIB The objects contained within this MIB replace similar objects that were previously defined in NTCIP1201-v03 in SMIv1 format. The previous objects have been deprecated, but are documented in SMIv2 format in NTCIP1201-DbMgmtV1." ::= {globalV2 1} -- 3.2 NODE DEFINITIONS adminDbMgmtV2 OBJECT-IDENTITY STATUS current DESCRIPTION " A node used to group administrative objects for the dbMgmtV2 feature. 1.3.6.1.4.1.1206.4.2.126.6.9.1" ::= {adminGlobalV2 1} dbMgmtV2Conformance OBJECT-IDENTITY STATUS current DESCRIPTION " A node used to contain conformance concepts for the dbMgmtV2 feature. 1.3.6.1.4.1.1206.4.2.6.9.1.127" ::= {dbMgmtV2 127} dbMgmtV2Compliances OBJECT-IDENTITY STATUS current DESCRIPTION " A node used to contain compliance statements for the dbMgmtV2 feature. 1.3.6.1.4.1.1206.4.2.6.9.1.127.1" ::= {dbMgmtV2Conformance 1} dbMgmtV2Groups OBJECT-IDENTITY STATUS current DESCRIPTION " A node used to contain object groups for the dbMgmtV2 feature. 1.3.6.1.4.1.1206.4.2.6.9.1.127.2" ::= {dbMgmtV2Conformance 2} -- 3.3 DATABASE TRANSACTION OBJECTS -- 3.3.1 Database Mode dbMgmtV2Mode OBJECT-TYPE SYNTAX INTEGER { normal (1), transaction (2), verify (3), done (4) } MAX-ACCESS read-write STATUS current DESCRIPTION " This object allows a manager (through its command generator) to modify a potentially large number of interrelated configuration parameters within a field device (through its command responder). In the normal state, set operations are processed without any special rules. In the transaction state, value assignments for parameter objects shall be buffered until the verify state performs a consistency check. When the consistency check completes, the command responder automatically transitions to the done state where a normal or transaction command may be issued. The normal state is the default state of this object upon initialization. All writable objects shall be treated as control objects unless otherwise specified (e.g., within a MIB or device-type standard). This object is a control object. Implementations shall not change the designation (e.g., control, parameter, or transaction) of any writable object type from that assigned in the standards to which it claims conformance. The following rules are applied during the processing of SetRequest-PDUs as defined in RFC 3416 Clause 4.2.5: NORMAL: When this object is in the 'normal' state: 1. An attempt to set a transaction object shall cause Step 9 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'notWritable' error. 2. An attempt to set this object to any value other than 'transaction' shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. 3. When setting this object to 'transition', the second phase of the set operation shall include the command responder copying all the parameter objects currently stored in the device into a buffer. A failure of this copy operation shall result in a failure in the second phase of the set operation and thereby result in a 'commitFailed' error and this object remaining in the 'normal' state. TRANSACTION: When this object is in the 'transaction' state: 1. An attempt to set a parameter object using a securityName other than the securityName that was used to start this transaction session shall cause Step 9 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'notWritable' error. 2. An attempt to set this object using a securityName other than the securityName that was used to start this transaction session shall cause Step 9 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'notWritable' error. 3. An attempt to set this object to any value other than 'normal' or 'verify' shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. 4. Within the second phase of the set operation, the command responder shall buffer the creation of and assignments to parameter objects rather than immediately implementing them. 5. Within the second phase of the set operation to set this object to 'normal', the agent shall discard all data in the transaction session buffer. NOTE: Control and status objects are processed normally given the above constraints. For example, another securityName can be used to set a control object without error. However, if that request also includes a parameter object, an 'inconsistentValue' error will be generated and neither the control object nor the parameter object will be altered. If the securityName used to initiate the transaction session is used to request setting both a control and a parameter object in a single request, the control object is immediately implemented while the parameter object request is buffered. GetRequest-PDUs are not affected by transaction sessions; they return the values currently implemented while ignoring any buffered values. VERIFY: Upon entry into the verify state, the command responder shall initiate the consistency check process. When this object is in the 'verify' state: 1. An attempt to set a parameter object using a securityName other than the securityName that was used to start this transaction session shall cause Step 9 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'notWritable' error. 2. An attempt to set this object using a securityName other than the securityName that was used to start this transaction session shall cause Step 9 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'notWritable' error. 3. An attempt to set a parameter object shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. 4. An attempt to set this object to any value shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. When consistency checks are complete the device shall update the values of dbVerifyStatusV2 and dbVerifyErrorV2 and automatically transition this object to the 'done' state. DONE: When this object is in the 'done' state: 1. The value of dbVerifyStatusV2 and dbVerifyErrorV2 shall indicate whether the consistency checks found any errors. 2. An attempt to set a parameter object using a securityName other than the securityName that was used to start this transaction session shall cause Step 9 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'notWritable' error. 3. An attempt to set this object using a securityName other than the securityName that was used to start this transaction session shall cause Step 9 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'notWritable' error. 4. An attempt to set a parameter object shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. 5. An attempt to set this object to any value other than 'normal' or 'transaction' shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. 6. An attempt to set this object to any value when this object is in the process of implementing the buffer while shifting from the 'done' state to the 'normal' state shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. 7. An attempt to set this object to a value of 'transaction' shall cause the command responder to re-enter the 'transaction' state without affecting the contents of the buffer. 8. An attempt to set this object to a value of 'normal' when dbVerifyStatusV2 has a value of 'doneWithNoError' shall result in the second phase of the set operation including the assignment of all the buffered data to the device's parameter objects. Any failure in the assignment process shall result in a failure in the second phase of the set operation and thereby result in the Response-PDU indicating either a 'commitFailed' or 'undoFailed' error, as appropriate, and this object remaining in the 'done' state. The values of dbVerifyStatusV2 and dbVerifyErrorV2 shall be updated at the end of the operation as appropriate. 9. An attempt to set this object to a value of 'normal' when dbVerifyStatusV2 has a value other than 'doneWithNoError' shall result in the transaction buffer being discarded during the second phase of the set operation. Usage Consistency checks are intended to analyze parameter objects 'in context' by treating them as an interrelated whole rather than separate non-related data items. Other standards (e.g., device-type standards) should define the minimum consistency check rules to be implemented for their context. Implementations may include additional, custom consistency checks beyond those standardized. NOTE: Other requests (e.g., GetRequest-PDUs and SetRequests containing only control objects) can be processed as normal regardless of the state of this object. 1.3.6.1.4.1.1206.4.2.6.9.1.1" DEFVAL {normal} ::= { dbMgmtV2 1 } -- 3.3.2 Database Status dbMgmtV2Status OBJECT-TYPE SYNTAX INTEGER { normal (1), transaction (2), verifying (3), doneWithNoError (4), doneWithError (5), commitFailed (6), undoFailed (7) } MAX-ACCESS read-only STATUS current DESCRIPTION " This object indicates the status of the consistency checking associated with the dbCreateTransactionV2 object. When dbCreateTransactionV2 is in the 'normal' or 'transaction' state, this object shall indicate the respective value. When dbCreateTransactionV2 is in the 'verify' state, this object shall indicate a value of 'verifying'. When in the 'done' state, this object shall have one of the following values: doneWithNoError: The consistency checks did not identify any inconsistencies with the buffered parameter objects. doneWithError: The consistency checks identified one or more inconsistencies with the buffered parameter objects. commitFailed: the attempt to assign the buffered parameter objects failed and the device has been restored to its previous state; dbCreateTransactionV2 can be set to 'transaction' and the process tried again undoFailed: the attempt to assign the buffered parameter objects failed and the device's database is in an unknown state with potential inconsistencies; dbCreateTransactionV2 can be set to 'transaction' and the process tried again. 1.3.6.1.4.1.1206.4.2.6.9.1.2" ::= { dbMgmtV2 2 } -- 3.3.3 Database Error dbMgmtV2Error OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains a textual description of or a reference to an error or condition that was found by the consistency checks implemented with the dbCreateTransactionV2 process. The value of this object shall be updated each time dbVerifyStatusV2 is updated. If dbCreateTransactionV2 is in the 'normal' state due to a reset command of dbTransactionReset, this field shall indicate 'Reset received' as the first characters in the string. Otherwise, unless the status reflects an error state (i.e., doneWithError, commitFailed, or undoFailed), this object shall indicate 'No error' as the first characters in the string. 1.3.6.1.4.1.1206.4.2.6.9.1.3" ::= { dbMgmtV2 3 } -- 3.3.4 Database Transaction Reset adminDbMgmtV2Reset OBJECT-TYPE SYNTAX INTEGER { normal (1), reset (2)} MAX-ACCESS read-write STATUS current DESCRIPTION " This object allows a user with sufficient rights to force the dbCreateTransactionV2 object back to the 'normal' state. An attempt to set this object to 'normal' shall cause Step 6 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in a 'wrongValue' error. An attempt to set this object to 'reset' when the dbCreateTransactionV2 is in the process of implementing the buffer while shifting from the 'done' state to the 'normal' state shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. An attempt to set this object to 'reset' when the dbCreateTransactionV2 is in the 'verify' state shall cause Step 10 of RFC 3416 Clause 4.2.5 to fail, thereby resulting in an 'inconsistentValue' error. Phase 2 of the set operation shall include discarding any information that is in the buffer. 1.3.6.1.4.1.1206.4.2.126.6.9.1.1" ::= { adminDbMgmtV2 1 } -- 3.4 DATABASE MANAGEMENT GROUP dbMgmtV2GroupR1 OBJECT-GROUP OBJECTS { dbMgmtV2Mode, dbMgmtV2Status, dbMgmtV2Error, adminDbMgmtV2Reset } STATUS current DESCRIPTION " The objects necessary for managing the database transaction feature. 1.3.6.1.4.1.1206.4.2.6.9.1.127.2.1" ::= {dbMgmtV2Groups 1} END --NTCIP1201-DbMgmtV2 -- Section 4 -- 4.1 MIB HEADER NTCIP1201-RecMechV2 DEFINITIONS ::= BEGIN IMPORTS zeroDotZero, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Unsigned32 FROM SNMPv2-SMI -- RFC 2578 RowPointer, RowStatus, StorageType, TruthValue, VariablePointer FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 SnmpAdminString, SnmpSecurityModel, SnmpSecurityLevel FROM SNMP-FRAMEWORK-MIB -- RFC 3411 ITSCounter16, ITSCounter32, ITSClear, ITSDateStamp, ITSDailyTimeStamp, ITSOerString, ITSPercent, ITSPositive8, ITSUnsigned8, ITSPositive16, ITSUnsigned16 FROM ISO20684-1-TC fdOwnerEntry, fdOwnerID FROM ISO20684-7-Owner globalV2, adminGlobalV2 FROM NTCIP1201-Global; recMechV2 MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION "The MIB that defines a high-resolution recording mechanism that allows a device to record information at a high rate for a defined period of time. 1.3.6.1.4.1.1206.4.2.6.9.2 Copyright (C) 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Original version of NTCIP1201-RecMechV2 MIB. The previous MIB module was renamed to NTCIP1201-RecMechV1. RecMechV2 was significantly revised to be triggered by the ISO 20684-3 trigger mechanism." REVISION "202007150000Z" DESCRIPTION "Updated IMPORTS statement to reference NTCIP8004v02 (electronic only)" REVISION "201611070000Z" DESCRIPTION "NTCIP 1103 v03 - Original version of recording mechanism in SMIv1 format." ::= {globalV2 2} -- 4.2 NODE DEFINITIONS adminRecMechV2 OBJECT-IDENTITY STATUS current DESCRIPTION "A node used to group administrative objects for the recMech feature. This node is intended to assist administrators in configuring access control. In general, administrator-level accounts can be given access to this node. In addition, it is envisioned that administrators may wish to grant owner-level accounts read-only access to the appropriate row within the adminRecMechTable so that owners can discover the amount of memory that they are allowed to access for recordings. 1.3.6.1.4.1.1206.4.2.126.6.9.2" ::= {adminGlobalV2 2} recMechV2Conformance OBJECT-IDENTITY STATUS current DESCRIPTION "A node used to contain conformance concepts for the rechMechV2 feature. 1.3.6.1.4.1.1206.4.2.6.9.2.127" ::= {recMechV2 127} recMechV2Compliances OBJECT-IDENTITY STATUS current DESCRIPTION "A node used to contain compliance statements for the recMechV2 feature. 1.3.6.1.4.1.1206.4.2.6.9.2.127.1" ::= {recMechV2Conformance 1} recMechV2Groups OBJECT-IDENTITY STATUS current DESCRIPTION "A node used to contain object groups for the recMechV2 feature. 1.3.6.1.4.1.1206.4.2.6.9.2.127.2" ::= {recMechV2Conformance 2} -- 4.3 ADMINISTRATIVE OBJECTS -- 4.3.1 Total Number of Recordings adminRecMechV2NumRecordings OBJECT-TYPE SYNTAX ITSUnsigned16 UNITS "recordings" MAX-ACCESS read-only STATUS current DESCRIPTION " The number of in-progress and completed recordings currently stored, regardless of adminRecMechV2Owner. 1.3.6.1.4.1.1206.4.2.126.6.9.2.1" ::= { adminRecMechV2 1 } -- 4.3.2 Recording Counter adminRecMechV2RecordingCtr OBJECT-TYPE SYNTAX ITSCounter32 UNITS "recordings" MAX-ACCESS read-only STATUS current DESCRIPTION " The number of recordings that have been completed since the last reboot, regardless of adminRecMechV2Owner. 1.3.6.1.4.1.1206.4.2.126.6.9.2.2" ::= { adminRecMechV2 2 } -- 4.3.3 Clear All adminRecMechV2ClearAll OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows in the recMechV2OwnerTable, recMechV2ClassTable, recMechV2FactoryTable, recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.126.6.9.2.3" ::= { adminRecMechV2 3 } -- 4.3.4 Clear All Classes adminRecMechV2ClearAllClasses OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows in the recMechV2ClassTable, recMechV2FactoryTable, recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.126.6.9.2.4" ::= { adminRecMechV2 4 } -- 4.3.5 Clear All Factories adminRecMechV2ClearAllFactories OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows in the recMechV2FactoryTable, recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.126.6.9.2.5" ::= { adminRecMechV2 5 } -- 4.3.6 Clear All Recordings adminRecMechV2ClearAllRecordings OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows in the recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.126.6.9.2.6" ::= { adminRecMechV2 6 } -- 4.4 OWNER TABLE recMechV2OwnerTable OBJECT-TYPE SYNTAX SEQUENCE OF RecMechV2OwnerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This table is used to allow owners to manage the recording mechanism and the recording tables that they own. managed 1.3.6.1.4.1.1206.4.2.6.9.2.1" ::= { recMechV2 1 } recMechV2OwnerEntry OBJECT-TYPE SYNTAX RecMechV2OwnerEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This object defines a row in the RecMechV2OwnerTable. 1.3.6.1.4.1.1206.4.2.6.9.2.1.1" AUGMENTS { fdOwnerEntry } ::= { recMechV2OwnerTable 1 } RecMechV2OwnerEntry ::= SEQUENCE { recMechV2OwnerNumRecordings ITSUnsigned16, recMechV2OwnerRecordingCtr ITSCounter32, recMechV2OwnerClearAll ITSClear, recMechV2OwnerClearAllClasses ITSClear, recMechV2OwnerClearAllFactories ITSClear, recMechV2OwnerClearAllRecordings ITSClear } -- 4.4.1 Number of Recordings for Owner recMechV2OwnerNumRecordings OBJECT-TYPE SYNTAX ITSUnsigned16 UNITS "recordings" MAX-ACCESS read-only STATUS current DESCRIPTION " The number of in-progress and completed recordings currently stored, regardless of adminRecMechV2Owner. 1.3.6.1.4.1.1206.4.2.6.9.2.1.1.1" ::= { recMechV2OwnerEntry 1 } -- 4.4.2 Recording Counter for Owner recMechV2OwnerRecordingCtr OBJECT-TYPE SYNTAX ITSCounter32 UNITS "recordings" MAX-ACCESS read-only STATUS current DESCRIPTION " A counter that increments upon the completion of each recording associated with the adminRecMechV2Owner. 1.3.6.1.4.1.1206.4.2.6.9.2.1.1.2" ::= { recMechV2OwnerEntry 2 } -- 4.4.3 Clear All for Owner recMechV2OwnerClearAll OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows associated with the adminRecMechV2Owner in the recMechV2ClassTable, recMechV2FactoryTable, recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.6.9.2.1.1.3" ::= { recMechV2OwnerEntry 3 } -- 4.4.4 Clear All Classes for Owner recMechV2OwnerClearAllClasses OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows associated with the adminRecMechV2Owner in the recMechV2ClassTable, recMechV2FactoryTable, recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.6.9.2.1.1.4" ::= { recMechV2OwnerEntry 4 } -- 4.4.5 Clear All Factories for Owner recMechV2OwnerClearAllFactories OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows associated with the adminRecMechV2Owner in the recMechV2FactoryTable, recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.6.9.2.1.1.5" ::= { recMechV2OwnerEntry 5 } -- 4.4.6 Clear All Recordings for Owner recMechV2OwnerClearAllRecordings OBJECT-TYPE SYNTAX ITSClear MAX-ACCESS read-write STATUS current DESCRIPTION " A control object that destroys all rows associated with the adminRecMechV2Owner in the recMechV2RecordingTable, and recMechV2SampleTable. 1.3.6.1.4.1.1206.4.2.6.9.2.1.1.6" ::= { recMechV2OwnerEntry 6 } -- 4.5 CLASS TABLE recMechV2ClassTable OBJECT-TYPE SYNTAX SEQUENCE OF RecMechV2ClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table is used to manage the recording mechanism and the recording tables. managed 1.3.6.1.4.1.1206.4.2.6.9.2.2" ::= { recMechV2 2 } recMechV2ClassEntry OBJECT-TYPE SYNTAX RecMechV2ClassEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object defines a row in the Recording Mechanism Manger Table. Rows defined within this table allow recordings from multiple triggers to be grouped together into a single class for easier management. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1" INDEX { fdOwnerID, recMechV2ClassID } ::= { recMechV2ClassTable 1 } RecMechV2ClassEntry ::= SEQUENCE { recMechV2ClassID ITSPositive8, recMechV2ClassDescription SnmpAdminString, recMechV2ClassSizeLimit Unsigned32, recMechV2ClassClearDate ITSDateStamp, recMechV2ClassClearTime ITSDailyTimeStamp, recMechV2ClassNumRecordings ITSUnsigned8, recMechV2ClassRecordingCtr ITSCounter16, recMechV2ClassStorageType StorageType, recMechV2ClassRowStatus RowStatus } -- 4.5.1 Class Name recMechV2ClassID OBJECT-TYPE SYNTAX ITSPositive8 MAX-ACCESS not-accessible STATUS current DESCRIPTION " A unique name for the recording class within the scope of the adminRecMechV2Owner. All recordings assigned to the class will be managed according to the other columns of this row. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.1" ::= { recMechV2ClassEntry 1 } -- 4.5.2 Class Description recMechV2ClassDescription OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION " A description of the recording class. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.2" ::= { recMechV2ClassEntry 2 } -- 4.5.3 Class Size Limit recMechV2ClassSizeLimit OBJECT-TYPE SYNTAX Unsigned32 UNITS "octets" MAX-ACCESS read-create STATUS current DESCRIPTION " This object specifies the maximum amount of memory to be used within the device to store recordings for the associated recording class. When the size limit is reached (e.g., due to a new recording or through the modification of this object) the oldest recording(s) within the class (based on the values of recMechV2RecordingTriggerDate and recMechV2RecordingTriggerTime) are bumped out of storage until the storage used for this recording class is less than or equal to the size defined by this object. An attempt to set this object to a value that would cause the sum of all recMechV2ClassSizeLimit objects for the associated adminRecMechV2Owner to exceed the adminRecMechSizeLimit for the adminRecMechV2Owner shall cause Step 10 of the set operation to fail, thereby resulting in an 'inconsistentVlaue' error. A recording that exceeds recMechV2ClassSizeLimit octets shall not be stored within the recording class. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.3" ::= { recMechV2ClassEntry 3 } -- 4.5.4 Class Clear Date recMechV2ClassClearDate OBJECT-TYPE SYNTAX ITSDateStamp MAX-ACCESS read-create STATUS current DESCRIPTION " This object, along with recMechV2ClassClearTime, is used to clear multiple recordings from the recMechV2RecordingTable and recMechV2SampleTable. All completed recordings (and associated samples) for this recording class that are associated with a recMechV2RecordingTriggerDate and recMechV2RecordingTriggerTime equal to or older than the recMechV2ClassClearDate and recMechV2ClassClearTime shall be cleared from the recMechV2RecordingTable and recMechV2SampleTable. If the recMechV2ClassClearDate and recMechV2ClassClearTime refer to a future point in time, no recordings shall be initiated for the associated recording class. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.4" ::= { recMechV2ClassEntry 4 } -- 4.5.5 Class Clear Time recMechV2ClassClearTime OBJECT-TYPE SYNTAX ITSDailyTimeStamp MAX-ACCESS read-create STATUS current DESCRIPTION " This object, along with recMechV2ClassClearDate, is used to clear multiple recordings from the recMechV2RecordingTable and recMechV2SampleTable. All completed recordings (and associated samples) for this recording class that are associated with a recMechV2RecordingTriggerDate and recMechV2RecordingTriggerTime equal to or older than the recMechV2ClassClearDate and recMechV2ClassClearTime shall be cleared from the recMechV2RecordingTable and recMechV2SampleTable. If the recMechV2ClassClearDate and recMechV2ClassClearTime refer to a future point in time, no recordings shall be initiated for the associated recording class. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.5" ::= { recMechV2ClassEntry 5 } -- 4.5.6 Class Number of Recordings recMechV2ClassNumRecordings OBJECT-TYPE SYNTAX ITSUnsigned8 UNITS "recording" MAX-ACCESS read-only STATUS current DESCRIPTION " The number of recordings for this recording class that are currently stored in the recMechV2RecordingTable. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.6" ::= { recMechV2ClassEntry 6 } -- 4.5.7 Class Recording Counter recMechV2ClassRecordingCtr OBJECT-TYPE SYNTAX ITSCounter16 UNITS "recording" MAX-ACCESS read-only STATUS current DESCRIPTION " This object is a counter that gets incremented every time a recording occurs for this class. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.7" ::= { recMechV2ClassEntry 7 } -- 4.5.8 Class Storage Type recMechV2ClassStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION " This object defines the storage type to use for this row of the recMechV2ClassTable. Rows having the value 'permanent' shall allow writable access to recMechV2ClassSizeLimit, recMechV2ClassClearDate, and recMechV2ClassClearTime. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.8" ::= { recMechV2ClassEntry 8 } -- 4.5.9 Class Row Status recMechV2ClassRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION " This object indicates the status of this row within the recMechV2ClassTable. Objects within this row can be modified regardless of the state of this object. Within the second phase of the set operation to set this object to 'destroy', all rows within the recMechV2FactoryTable, recMechV2RecordingTable, and recMechV2SampleTable that use this recMechV2ClassName as an index shall also be destroyed. 1.3.6.1.4.1.1206.4.2.6.9.2.2.1.9" ::= { recMechV2ClassEntry 9 } -- 4.6 RECORDING FACTORY recMechV2FactoryTable OBJECT-TYPE SYNTAX SEQUENCE OF RecMechV2FactoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This table is used to configure the information to be contained within each recording.
managed 1.3.6.1.4.1.1206.4.2.6.9.2.3" ::= { recMechV2 3 } recMechV2FactoryEntry OBJECT-TYPE SYNTAX RecMechV2FactoryEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This object defines a row in the Recording Mechanism Factory Table. Rows defined within this table define the information the device shall record when a recording is initiated. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1" INDEX { fdOwnerID, recMechV2ClassID, recMechV2FactoryID } ::= { recMechV2FactoryTable 1 } RecMechV2FactoryEntry ::= SEQUENCE { recMechV2FactoryID ITSPositive8, recMechV2FactorySecurityModel SnmpSecurityModel, recMechV2FactorySecurityLevel SnmpSecurityLevel, recMechV2FactorySecurityName SnmpAdminString, recMechV2FactorySampleContext SnmpAdminString, recMechV2FactorySampleOID VariablePointer, recMechV2FactoryPreSamples ITSPercent, recMechV2FactorySamplePeriod ITSUnsigned16, recMechV2FactoryMonitorContext SnmpAdminString, recMechV2FactoryMonitorOID VariablePointer, recMechV2FactorySampleLimit ITSUnsigned16, recMechV2FactoryStorageType StorageType, recMechV2FactoryRowStatus RowStatus } -- 4.6.1 Recording Factory Name recMechV2FactoryID OBJECT-TYPE SYNTAX ITSPositive8 MAX-ACCESS not-accessible STATUS current DESCRIPTION " This object provides a unique name for the recording factory within the context of the adminRecMechV2Owner. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.1" ::= { recMechV2FactoryEntry 1 } -- 4.6.2 Recording Factory Security Model recMechV2FactorySecurityModel OBJECT-TYPE SYNTAX SnmpSecurityModel MAX-ACCESS not-accessible STATUS current DESCRIPTION " The security model used to activate this row of the recMechV2FactoryTable and that is used to access the recMechV2FactoryObjectID and recMechV2FactorySampleOID. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.2" ::= { recMechV2FactoryEntry 2 } -- 4.6.3 Recording Factory Security Level recMechV2FactorySecurityLevel OBJECT-TYPE SYNTAX SnmpSecurityLevel MAX-ACCESS not-accessible STATUS current DESCRIPTION " The security level used to activate this row of the recMechV2FactoryTable and that is used to access the recMechV2FactoryObjectID and recMechV2FactorySampleOID. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.3" ::= { recMechV2FactoryEntry 3 } -- 4.6.4 Recording Factory Security Name recMechV2FactorySecurityName OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS not-accessible STATUS current DESCRIPTION " The security name used to activate this row of the recMechV2FactoryTable and that is used to access the recMechV2FactoryObjectID and recMechV2FactorySampleOID. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.4" ::= { recMechV2FactoryEntry 4 } -- 4.6.5 Context for Object to be Sampled recMechV2FactorySampleContext OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-create STATUS current DESCRIPTION " The management context of the object instance to be sampled for the recording. For example, the command responder might provide access to multiple MIB instances; this object disambiguates which MIB instance is to be used. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.5" ::= { recMechV2FactoryEntry 5 } -- 4.6.6 Object to be Sampled in Recording recMechV2FactorySampleOID OBJECT-TYPE SYNTAX VariablePointer MAX-ACCESS read-create STATUS current DESCRIPTION " The object identifier of the object instance to be sampled for the recording. The object instance shall be accessed using the security parameters as specified in recMechV2FactorySecurityModel, recMechV2FactorySecurityLevel, recMechV2FactorySecurityName, and recMechV2FactorySampleContext. (See RFC 3415 for details about how the view-based access control model uses these parameters.) An attempt to set this object to a value that is not within the read mib view for the supplied security parameters shall result in a failure of Step 10 of the set operation, thereby resulting in an 'inconsistent value' error. NOTE: The object instance does not have to exist at the time that this object is set for the set to be successful. If the object identifier does not point to a valid object instance within the read mib view for the indicated security parameters at the time that the data is being sampled, the sample shall record a zero- length string. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.6" ::= { recMechV2FactoryEntry 6 } -- 4.6.7 Pre-Trigger Samples recMechV2FactoryPreSamples OBJECT-TYPE SYNTAX ITSPercent MAX-ACCESS read-create STATUS current DESCRIPTION " This object indicates the percentage of samples in a recording that are intended to be captured prior to the recording being triggered. When this value is greater than zero (0), the device will need to collect and buffer samples prior to the recording being triggered so that it can store the requisite information when a recording is triggered. A value of zero (0) means that the recording shall start with the first sample captured after the recording is triggered. A value of 100 means that the recording will end with the last sample captured prior to or simultaneous with the recording being triggered, where simultaneous is defined as occurring within recMechV2FactorySamplePeriod / 2. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.7" ::= { recMechV2FactoryEntry 7 } -- 4.6.8 Sample Period recMechV2FactorySamplePeriod OBJECT-TYPE SYNTAX ITSUnsigned16 UNITS "0.1 milliseconds" MAX-ACCESS read-create STATUS current DESCRIPTION " This object indicates the frequency at which samples shall be taken. Allowable sample periods are restricted to a value of zero (0) or recMechMinSamplePeriod + (recMechV2SamplePeriodResolution * n) where n is an integer, 0 <= n, and n <= (recMechMaxSamplePeriod: recMechMinSamplePeriod) / recMechV2SamplePeriodResolution If the value of this object is zero (0), samples shall be collected whenever the value of the object specified by recMechV2FactoryMonitorOID changes (i.e., based on an on-change event rather than based on time). If the value of this object is greater than zero, this object indicates the time that shall elapse between each sample collected for the recording produced by this factory and the value of recMechV2FactoryMonitorOID shall be ignored. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.8" ::= { recMechV2FactoryEntry 8 } -- 4.6.9 Context for Object to be Monitored recMechV2FactoryMonitorContext OBJECT-TYPE SYNTAX SnmpAdminString (SIZE (0..32)) MAX-ACCESS read-create STATUS current DESCRIPTION " The management context to use when accessing recMechV2FactoryMonitorOID. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.9" ::= { recMechV2FactoryEntry 9 } -- 4.6.10 Object to be Monitored for Change Events recMechV2FactoryMonitorOID OBJECT-TYPE SYNTAX VariablePointer MAX-ACCESS read-create STATUS current DESCRIPTION " The object identifier of the object instance to be monitored for on-change events when recMechV2FactorySamplePeriod is zero (0). If recMechV2FactorySamplePeriod is non-zero, the value of this object shall be ignored. The object instance shall be accessed using the security parameters as specified in recMechV2FactorySecurityModel, recMechV2FactorySecurityLevel, recMechV2FactorySecurityName, and recMechV2FactoryMonitorContext. An attempt to set this object to a value, other than zeroDotZero, that is not within the read mib view for the supplied security parameters shall result in a failure of Step 10 of the set operation, thereby resulting in an 'inconsistent value' error. NOTE: The object instance does not have to exist at the time that this object is set for the set to be successful. If this object does not point to a valid object instance within the read mib view for the indicated security parameters at the time that the data is being monitored, the on-change event shall not fire. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.10" ::= { recMechV2FactoryEntry 10 } -- 4.6.11 Number of Samples to Collect recMechV2FactorySampleLimit OBJECT-TYPE SYNTAX ITSUnsigned16 UNITS "samples" MAX-ACCESS read-create STATUS current DESCRIPTION " The intended number of samples to be included for recordings produced by this factory. A recording that collects its full number of samples prior to and after the recording trigger shall have a recording of this number of samples. If this object is zero (0), then no recordings are created based on this configuration. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.11" ::= { recMechV2FactoryEntry 11 } -- 4.6.12 Recording Factory Storage Type recMechV2FactoryStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION " This object defines the storage type to use for this row within the recMechV2FactoryTable. Permanent rows do not have to be editable. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.12" ::= { recMechV2FactoryEntry 12 } -- 4.6.13 Recording Factory Row Status recMechV2FactoryRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION " This object indicates the status of this row within the recMechV2FactoryTable. Objects within this row cannot be modified while this object is 'active'. Within the second phase of the set operation to set this object to 'destroy', all rows within the recMechV2RecordingTable, and recMechV2SampleTable with an index that includes both recMechV2ClassName and recMechV2FactoryName shall also be destroyed. 1.3.6.1.4.1.1206.4.2.6.9.2.3.1.13" ::= { recMechV2FactoryEntry 13 } -- 4.7 RECORDING TABLE recMechV2RecordingTable OBJECT-TYPE SYNTAX SEQUENCE OF RecMechV2RecordingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This table is used to provide information about each recording completed or in progress.
managed 1.3.6.1.4.1.1206.4.2.6.9.2.4" ::= { recMechV2 4 } recMechV2RecordingEntry OBJECT-TYPE SYNTAX RecMechV2RecordingEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " This object defines a row in the recMechV2RecordingTable. Rows defined within this table capture information that applies to all samples collected within the recording. 1.3.6.1.4.1.1206.4.2.6.9.2.4.1" INDEX {fdOwnerID, recMechV2ClassID, recMechV2RecordingID} ::= { recMechV2RecordingTable 1 } RecMechV2RecordingEntry ::= SEQUENCE { recMechV2RecordingID ITSPositive8, recMechV2RecordingTrigger RowPointer, recMechV2RecordingTriggerDate ITSDateStamp, recMechV2RecordingTriggerTime ITSDailyTimeStamp, recMechV2RecordingStatus INTEGER, recMechV2RecordingTriggerSample ITSUnsigned16, recMechV2RecordingNumSamples ITSUnsigned16, recMechV2RecordingDelete TruthValue } -- 4.7.1 Recording Index recMechV2RecordingID OBJECT-TYPE SYNTAX ITSPositive8 MAX-ACCESS not-accessible STATUS current DESCRIPTION " The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and increasing sequentially by 1 with each new recording within the class. After the assigned value reaches 255, the process shall repeat, skipping the value 0. Recordings shall be assigned the index value in order of the trigger events occurring ensuring that the trigger date/time values are chronological (except for the rollover). 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.1" ::= { recMechV2RecordingEntry 1 } -- 4.7.2 Recording Trigger recMechV2RecordingTrigger OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION " This object indicates the trigger or event that caused the recording to be initiated. For example, if the recording was triggered by a conditional trigger, this object would indicate the OID of fdCondTriggerDescription for the row within the fdCondTriggerTable that caused the recording. 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.2" ::= { recMechV2RecordingEntry 2 } -- 4.7.3 Recording Trigger Date recMechV2RecordingTriggerDate OBJECT-TYPE SYNTAX ITSDateStamp MAX-ACCESS read-only STATUS current DESCRIPTION " This object contains the date on which the recording was triggered. 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.3" ::= { recMechV2RecordingEntry 3 } -- 4.7.4 Recording Trigger Time recMechV2RecordingTriggerTime OBJECT-TYPE SYNTAX ITSDailyTimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION " This object indicates the time at which the recording was triggered. 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.4" ::= { recMechV2RecordingEntry 4 } -- 4.7.5 Recording Status recMechV2RecordingStatus OBJECT-TYPE SYNTAX INTEGER { available (1), pretrigger (2), triggered (3), complete (4)} MAX-ACCESS read-only STATUS current DESCRIPTION " The value of this object reflects the state of the recording located in this row. Value Description available This row is available for a new recording to be initiated for this recording class. When a recording is cleared, the value is set to available. Note: This state is only applicable to implementations that have rows that can exist without any samples. pretrigger The recording is collecting pre-trigger samples. Note: When the trigger point is zero (0) percent or the trigger condition is already satisfied when the recMechV2FactoryEntry is configured, this state does not occur. triggered The recording has been triggered and is currently collecting post event records. Triggered recordings shall survive a power outage. Upon power up, any recording in the 'triggered' state shall automatically transition to the 'complete' state. Note: When the trigger point is 100 percent, this state does not occur. complete The recording is complete (e.g., all post-event samples have been collected). Completed recordings shall survive a power outage. 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.5" ::= { recMechV2RecordingEntry 5 } -- 4.7.6 Recording Trigger Sample recMechV2RecordingTriggerSample OBJECT-TYPE SYNTAX ITSUnsigned16 UNITS "samples" MAX-ACCESS read-only STATUS current DESCRIPTION " This object indicates the number (recMechV2SampleNumber) of the first post-event sample in the recording. 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.6" ::= { recMechV2RecordingEntry 6 } -- 4.7.7 Number of Samples in Recording recMechV2RecordingNumSamples OBJECT-TYPE SYNTAX ITSUnsigned16 UNITS "samples" MAX-ACCESS read-only STATUS current DESCRIPTION " The current number of samples contained in this recording. A completed recording does not necessarily have exactly recMechV2FactoryNumSamples samples recorded (e.g., due to changes in configuration, errors in collecting samples, etc.). 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.7" ::= { recMechV2RecordingEntry 7 } -- 4.7.8 Delete Recording recMechV2RecordingDelete OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION " A control that allows the deletion of the recording. The object shall always report false when read. Setting this object to true shall delete this row in the table and shall also delete all rows in the recMechV2SampleTable with the same fdOwnerID, recMechV2ClassID, and recMechV2RecordingID. 1.3.6.1.4.1.1206.4.2.6.9.2.4.1.8" ::= { recMechV2RecordingEntry 8 } -- 4.8 SAMPLE TABLE recMechV2SampleTable OBJECT-TYPE SYNTAX SEQUENCE OF RecMechV2SampleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " A table containing the samples for each recording.
managed 1.3.6.1.4.1.1206.4.2.6.9.2.5" ::= { recMechV2 5 } recMechV2SampleEntry OBJECT-TYPE SYNTAX RecMechV2SampleEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " An entry in the recording mechanism sample table. 1.3.6.1.4.1.1206.4.2.6.9.2.5.1" INDEX { fdOwnerID, recMechV2ClassID, recMechV2RecordingID, recMechV2SampleID} ::= { recMechV2SampleTable 1 } RecMechV2SampleEntry::= SEQUENCE { recMechV2SampleID ITSPositive16, recMechV2SampleTime ITSDailyTimeStamp, recMechV2SampleValue ITSOerString } -- 4.8.1 Sample Number recMechV2SampleID OBJECT-TYPE SYNTAX ITSPositive16 MAX-ACCESS not-accessible STATUS current DESCRIPTION " The number used to uniquely identify this sample within this recording. Sample numbers shall be sequentially assigned starting at 1 and increasing by 1 until the configured number of post-event samples have been captured or the recording is otherwise completed. 1.3.6.1.4.1.1206.4.2.6.9.2.5.1.1" ::= { recMechV2SampleEntry 1 } -- 4.8.2 Sample Time recMechV2SampleTime OBJECT-TYPE SYNTAX ITSDailyTimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION " The time that the sample was captured. The entry shall be collected within one recMechV2SamplePeriodResolution unit of time from the intended time and timestamped with the time of collection. 1.3.6.1.4.1.1206.4.2.6.9.2.5.1.2" ::= { recMechV2SampleEntry 2 } -- 4.8.3 Sample Value recMechV2SampleValue OBJECT-TYPE SYNTAX ITSOerString MAX-ACCESS read-only STATUS current DESCRIPTION " The OER-encoded value of the object instance referenced by recMechV2FactorySampleOID at the time when the sample was collected. The value shall not contain any padding characters either before or after the values. Decoding the value of this object requires knowledge of the syntax of the object referenced by recMechV2FactorySampleOID. For example, the value portion of the variableBinding encoding of this object could be 0x04 02 01 41, where: 04: octet string type for ITSOerString 02: length of 2 octets 01 41: sampled value of object referenced by recMechV2FactorySampleOID The exact meaning of 01 41 is based on the syntax of recMechV2FactorySampleOID; for example, the following table gives possible valid decodings depending on the syntax: Syntax Decoding Logic ITSInteger16 321 fixed-length two-octet integer encoding Counter64 65 one-octet length and one-octet value SnmpAdminString 'A' one-octet length and one-octet value 1.3.6.1.4.1.1206.4.2.6.9.2.5.1.3" ::= { recMechV2SampleEntry 3 } -- 4.9 CAPABILITY OBJECTS -- 4.9.1 Minimum Sample Period recMechV2MinSamplePeriod OBJECT-TYPE SYNTAX ITSPositive16 UNITS "0.1 milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " The minimum sample period for recordings supported by the device. 1.3.6.1.4.1.1206.4.2.6.9.2.6" ::= { recMechV2 6} -- 4.9.2 Maximum Sample Period recMechV2MaxSamplePeriod OBJECT-TYPE SYNTAX ITSPositive16 UNITS "0.1 milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " The maximum sample period for recordings supported by the device. 1.3.6.1.4.1.1206.4.2.6.9.2.7" ::= { recMechV2 7} -- 4.9.3 Sample Period Resolution recMechV2SamplePeriodResolution OBJECT-TYPE SYNTAX Unsigned32 (1..50) UNITS "0.1 milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION " The sample period resolution for recordings supported by the device. Allowable sample periods are restricted to (recMinSamplePeriod + recSamplePeriodResolution * n), where: n is an integer, 0 <= n, and n <= (recMaxSamplePeriod - recMinSamplePeriod) / recSamplePeriodResolution 1.3.6.1.4.1.1206.4.2.6.9.2.8" ::= { recMechV2 8} -- 4.10 COMPLIANCE GROUPS -- 4.10.1 Recording Mechanism Group recMechV2GroupR1 OBJECT-GROUP OBJECTS { adminRecMechV2ClearAll, adminRecMechV2ClearAllFactories, adminRecMechV2ClearAllRecordings, adminRecMechV2NumRecordings, adminRecMechV2RecordingCtr, recMechV2MinSamplePeriod, recMechV2MaxSamplePeriod, recMechV2SamplePeriodResolution, recMechV2OwnerClearAll, recMechV2OwnerClearAllFactories, recMechV2OwnerClearAllRecordings, recMechV2OwnerNumRecordings, recMechV2OwnerRecordingCtr, recMechV2ClassDescription, recMechV2ClassSizeLimit, recMechV2ClassClearDate, recMechV2ClassClearTime, recMechV2ClassStorageType, recMechV2ClassRowStatus, recMechV2ClassNumRecordings, recMechV2ClassRecordingCtr, recMechV2FactorySampleContext, recMechV2FactorySampleOID, recMechV2FactoryPreSamples, recMechV2FactorySamplePeriod, recMechV2FactoryMonitorContext, recMechV2FactoryMonitorOID, recMechV2FactorySampleLimit, recMechV2FactoryStorageType, recMechV2FactoryRowStatus, recMechV2RecordingDelete, recMechV2RecordingTrigger, recMechV2RecordingTriggerDate, recMechV2RecordingTriggerTime, recMechV2RecordingStatus, recMechV2RecordingTriggerSample, recMechV2RecordingNumSamples, recMechV2SampleTime, recMechV2SampleValue } STATUS current DESCRIPTION "The objects necessary for the recording mechanism version 2. NOTE: The recording mechanism is dependent upon the fdOwnerTable, as defined in ISO 20684-7. It is designed to be called by the ISO 20684-3 Action Table but could be called by other means as well. 1.3.6.1.4.1.1206.4.2.6.9.2.127.2.1" ::= {recMechV2Groups 1} END -- NTCIP1201-RechMechV2 -- Section 5 -- 5.1 NTCIP HEADER NTCIP1201-GlobalV1 DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32, Unsigned32, zeroDotZero FROM SNMPv2-SMI -- RFC 2578 AutonomousType, VariablePointer FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP FROM SNMPv2-CONF global FROM NTCIP1201-Global profiles FROM NTCIP8004-Transportation; globalV1 MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of various globally applicable objects that were previously defined in NTCIP 1201 v03. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.2.6.8 Copyright (C) 2010, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "200803240000Z" DESCRIPTION "NTCIP 1201 v03 - Added DST table objects. Created standalone MIBs for the main portion of the MIB and the 2 different versions of AuxIO objects." REVISION "200409270000Z" DESCRIPTION "NTCIP 1201 v02: Removed global report, logicalNameTranslation and communityName nodes as they are now included in NTCIP 1103v0124. Removed state transition diagram form 2.3.1. Changed 'FROM NTCIP8004-A' to 'FROM NTCIP8004-A-2004' and restructured associated imports. Changed status of moduleNumber, timeBaseScheduleNumber, dayPlanNumber, dayPlanEventNumber, eventClassNumber, eventConfigID and their associated Entry to mandatory from optional to eliminate incompatible status errors. " REVISION "199810010000Z" DESCRIPTION "Amendment 1 to NTCIP 1201 v01 (a.k.a. Amendment 1 to NEMA TS 3.4 and NTCIP 1201:1998): Editorial corrections. Revised DST object." REVISION "199610010000Z" DESCRIPTION "Original version approved as NEMA TS 3.4 (a.k.a., NTCIP 1201 v01)." ::= { global 8 } -- 5.2 OBJECT IDENTITIES -- 5.2.1 Global Configuration Node globalConfiguration OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to group all objects for support of configuration functions that are common to most device types. 1.3.6.1.4.1.1206.4.2.6.1" ::= { global 1 } globalConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define conformance information for the global MIB. 1.3.6.1.4.1.1206.4.2.6.8.127" ::= { globalV1 127 } globalCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define compliance statements for the global MIB. 1.3.6.1.4.1.1206.4.2.6.8.127.1" ::= { globalConformance 1 } globalGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define object groups for the global MIB. 1.3.6.1.4.1.1206.4.2.6.8.127.2" ::= { globalConformance 2 } -- 5.3 OBJECTS -- 5.3.1 Global Set ID Parameter globalSetIDParameter OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for all user-changeable parameters of the particular device-type currently implemented in the device. Often this ID is calculated using a CRC algorithm. This value shall be calculated when a change of any parameter object has occurred. The value reported by this object shall not change unless there has been a change in the static data since the last request. If the actual objects, which are to be included to create this object value, are not defined in the actual device-level standard such as 1202 or 1203, then the general guidance is to include all configuration objects that are stored in a type of memory that survives power outages. A management station can use this object to detect any change in the parameter objects by monitoring this value after it has established a baseline. FIELD-DEVICE-MAIN-MIB.fdConfigurationID (ISO 20684-2) 1.3.6.1.4.1.1206.4.2.6.1.1" ::= { globalConfiguration 1} -- 5.3.2 Maximum Modules Parameter globalMaxModules OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "modules" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows that are listed in the globalModuleTable. The module table has been replaced with features from other standards so this object is no longer needed. 1.3.6.1.4.1.1206.4.2.6.1.2" ::= { globalConfiguration 2} -- 5.3.3 Module Table moduleTable OBJECT-TYPE SYNTAX SEQUENCE OF ModuleEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table containing information regarding manufacturer of software and hardware and the associated module models and version numbers as well as an indicator if the module is hardware or software related. The number of rows in this table shall equal the value of the globalMaxModules object. The module table has been replaced with features from other standards. static 1.3.6.1.4.1.1206.4.2.6.1.3" ::= { globalConfiguration 3 } moduleEntry OBJECT-TYPE SYNTAX ModuleEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " This object defines an entry in the module table. The module table has been replaced with features from other standards. 1.3.6.1.4.1.1206.4.2.6.1.3.1" INDEX { moduleNumber } ::= { moduleTable 1 } ModuleEntry ::= SEQUENCE { moduleNumber INTEGER, moduleDeviceNode AutonomousType, moduleMake OCTET STRING, moduleModel OCTET STRING, moduleVersion OCTET STRING, moduleType INTEGER } -- 5.3.3.1 Module Number Parameter moduleNumber OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object contains the row number (1..255) within this table for the associated module. The module table has been replaced with features from other standards so a row number is no longer needed. 1.3.6.1.4.1.1206.4.2.6.1.3.1.1" ::= { moduleEntry 1 } -- 5.3.3.2 Module Device Node Parameter moduleDeviceNode OBJECT-TYPE SYNTAX AutonomousType MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the device node number of the device-type, e.g., an ASC signal controller would have an OID of 1.3.6.1.4.1.1206.4.2.1. SNMPv2-MIB.sysORID (from RFC 3418) The intent of this object was to provide an indication of the type of data within the device. This is achieved at a much finer level of detail with the replacement object, which is a required object per SNMPv3 standards. 1.3.6.1.4.1.1206.4.2.6.1.3.1.2" ::= { moduleEntry 2 } -- 5.3.3.3 Module Make Parameter moduleMake OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object specifies the manufacturer of the associated module. A null-string shall be transmitted if this object has no entry. ENTITY-MIB.entPhysicalMfgName (RFC 6933) The entPhysicalTable allows (but does not require) an implementation to show relationships among components thereby providing more meaningful information for devices that need to provide this level of detail. It is also defined as a multi-lingual string that will allow managers to automatically display the text in the appropriate format. 1.3.6.1.4.1.1206.4.2.6.1.3.1.3" ::= { moduleEntry 3 } -- 5.3.3.4 Module Model Parameter moduleModel OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object specifies the model number (hardware) or firmware reference (software) of the associated module. A null-string shall be transmitted if this object has no entry. ENTITY-MIB.entPhysicalModelName (RFC 6933) The entPhysicalTable allows (but does not require) an implementation to show relationships among components thereby providing more meaningful information for devices that need to provide this level of detail. It is also defined as a multi-lingual string that will allow managers to automatically display the text in the appropriate format. 1.3.6.1.4.1.1206.4.2.6.1.3.1.4" ::= { moduleEntry 4 } -- 5.3.3.5 Module Version Parameter moduleVersion OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object specifies the version of the associated module. If the moduleType has a value of software, the value of this object shall include the date on which the software was released as a string in the form of YYYYMMDD, it shall be followed by a space, a hyphen, another space, the lower-case letter 'v', followed by a version or configuration number. Preceding zeros shall be required for the date. For example, version 7.03.02 of the software released on July 5, 2002 would be presented as 20020705: v7.03.02 A null-string shall be transmitted if this object has no entry. ENTITY-MIB.entPhysicalHardwareRev & ENTITY-MIB.entPhysicalSoftwareRev (RFC 6933) The entPhysicalTable allows (but does not require) an implementation to show relationships among components thereby providing more meaningful information for devices that need to provide this level of detail. It is also defined as a multi-lingual string that will allow managers to automatically display the text in the appropriate format. 1.3.6.1.4.1.1206.4.2.6.1.3.1.5" ::= { moduleEntry 5 } -- 5.3.3.6 Module Type Parameter moduleType OBJECT-TYPE SYNTAX INTEGER { other (1), hardware (2), software (3) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object specifies whether the associated module is a hardware or software module. The ENTITY-MIB.entPhysicalTable (RFC 6933) allows the definition of physical entities that contain hardware and/or software and allows associations among them. 1.3.6.1.4.1.1206.4.2.6.1.3.1.6" ::= { moduleEntry 6 } -- 5.3.4 Base Standards Parameter controllerBaseStandards OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..256)) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " For use in this object, an ASCII string that shall identify all of the standard document numbers that define or reference MIBs upon which the device is based. Where applicable, profiles shall be referenced rather than the base standards. The version string shall be constructed as follows: The acronym of the standards development organization (or other body) that developed and approved the standard; a space; the standards document number; a colon; and the documents version number as designated by the standards development organization (or other body). Separate entries in the list of standards shall be separated by a carriage return (0x0d) and line feed (0x0a). In the case of NTCIP documents prior to formal approval, the version number shall be the version number in the form of lower case 'v' followed by the major version followed by a period followed by the minor revision. In the case of approved NTCIP standards, the publication year shall precede the version number. In the case of amended NTCIP standards, the version number shall be replaced by the four digit year of publication of the published standard followed by the upper case letter 'A', followed by the amendment number. For example, a message sign may have the following value for this object: NTCIP 1201:v02.19 NTCIP 1203:1997A1 NTCIP 2101:2001 v01.19 NTCIP 2103:v01.13 NTCIP 2201:v01.14 NTCIP 2301:2001 v01.08 SNMPv2-MIB.sysORID (from RFC 3418) sysORID provides more refined information using OIDs to identify compliance statements that can be processed by computers without having to parse strings. 1.3.6.1.4.1.1206.4.2.6.1.4" ::= { globalConfiguration 4 } -- 5.4 GLOBAL DATABASE MANAGEMENT NODE globalDBManagement OBJECT-IDENTITY STATUS deprecated DESCRIPTION "This node is an identifier used to group those objects used to manage a transaction. A transaction is a SET of one or more database parameters that have inter- relationships with other database parameters, as such a SET for any one of these objects must be validated against a set of consistency checks and may potentially require the setting of a large number of objects simultaneously. Thus, the mode described by these objects allow for such a large database download. Any device standard that allows this feature shall define which objects are database parameters versus status or control objects. 1.3.6.1.4.1.1206.4.2.6.2" ::= { global 2 } -- -- 5.4.1 Database Creation Transaction dbCreateTransaction OBJECT-TYPE SYNTAX INTEGER { normal (1), transaction (2), verify (3), done (6) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object provides transaction control for device configuration. The transaction mode changes the behavior of the agent to force buffering of parameter objects until all related parameter objects have been modified. In the normal mode, SET operations to any parameter object shall either be stored in a device's database immediately with no regard to whether other changes will be made or be rejected (as defined in the device-specific Information Profile). In the transaction mode, SET operations to any parameter object shall be buffered until a verify state performs a consistency check. When the consistency check completes, the device automatically transitions to the done state where a normal or transaction command may be issued. A parameter object is a user-provided piece of setup information (or it may be defined in an information profile) that is necessary for the proper operation of a device. It is static in nature in that the agent would never change it without direction from the management station. For example, an object that defines a default mode of operation would be a parameter object. An object that indicates the current state of the device would not be a parameter object. The states and commands are defined as: NORMAL: SET operations behave as normal SETs and shall have an immediate effect on the value of any parameter objects used by the device if none of the objects contained in the operation require the use of the transaction mode (as defined in the device-specific Information Profile). A SET operation containing any transaction object (i.e., a parameter object that requires the use of transaction mode) shall result in a genErr. This is the default state of this object. The only command that may be written to dbCreateTransaction while in this state is TRANSACTION. Any other values written to this object in this state shall result in an error response of 'badValue'. TRANSACTION: A SET operation of one or more parameter objects that use the same community name as used in the request for the TRANSACTION state are buffered by the agent device for later consistency checks and a normal response is returned. A SET operation of one or more parameter objects using different community names shall result in a genErr with the index set to zero. A SET operation without a community name field (e.g., an STMP operation) shall be buffered by the agent device for later consistency checks and a normal response is returned. Standard SYNTAX checking shall take place at the time of the SET operation. A transaction may consist of multiple SET operations over multiple frames. A SET operation for one or more non-parameter objects shall be processed as normal even if it uses another community name, except for this (i.e., the dbCreateTransaction) object. A SET operation containing both parameter and non-parameter objects shall be processed in full according to these two rules. Thus, if it contains the same community name as used in the request for the TRANSACTION state, the non-parameter objects shall be stored immediately while the parameter objects shall be buffered. If it uses a different community name, the entire request will be rejected and a genErr with an index of zero shall be returned. GET operations on any object shall return the values of the data stored in the controller and shall ignore any values contained in the buffer. Any valid community name may read this (dbCreateTransaction) object when in this state, but only the community name used to command the object to the transaction mode and the administrator community name can set this object. A set from any other community name shall result in a genErr with an index of zero. The only commands that can be written to dbCreateTransaction while in this state are VERIFY and NORMAL. A VERIFY command will change the state to VERIFY. If a NORMAL command is received, all buffered data is discarded and the state is returned to NORMAL. Any other values written to this object when in this state shall result in an error response of 'badValue'. VERIFY: Specific parameter objects are checked for consistency. When consistency checks are complete the device will automatically advance to the DONE state. The state of dbCreateTransaction cannot be changed when in the VERIFY state. Any values written to this object in this state shall result in an error response of 'badValue'. The consistency check analyzes certain critical objects 'in context' and treats them as an interrelated whole rather than separate non-related data items. The consistency check rules are not defined in NTCIP 1201 v03, since these are device and implementation specific. Where applicable, the consistency check rules are defined in application specific object definition standards. A specific implementation may add additional checks beyond those defined in NTCIP standards. A SET operation containing any parameter objects while in the VERIFY state shall result in a genErr with the index set to zero. DONE: This state is entered automatically once consistency checks have completed in the VERIFY mode. The value of dbVerifyStatus and dbVerifyError indicate whether the consistency check found any errors. A SET operation containing any parameter objects while in the DONE state shall result in a genErr with the index set to zero. Any valid community name may read this (dbCreateTransaction) object when in this state, but only the community name used to command the object to the transaction mode and the administrator community name can set this object. A set from any other community name shall result in a genErr with an index of zero. The only commands that can be written to dbCreateTransaction while in this state are NORMAL and TRANSACTION. Any other values written to this object in this state shall result in an error response of 'badValue'. If a NORMAL command is issued and dbVerifyStatus indicates doneWithNoError, the buffered data is transferred to the device memory and the state is returned to NORMAL. If a NORMAL command is issued and dbVerifyStatus indicates something other than doneWithNoError then the buffered data is discarded and the state is returned to NORMAL. If a TRANSACTION command is issued, regardless of dbVerifyStatus, no action takes place (the buffered data is not changed) and the TRANSACTION state is re-entered. COMMANDED STATE (9) transaction verify normal done CURRENT STATE normal transaction (1) normal (2) normal (2) normal (2) transaction transaction (2) verify (3) normal (4) transaction (2) verify (7) verify (2) verify(2) verify (2) verify (2) done (8) transaction (5) done(2) normal (6) done (2) Operational procedures and error responses: (1) Once a copy of all parameter objects is placed in a buffer, the state is changed to transaction and error response indicates noError. If the operation fails, the state remains the same and error response indicates genErr. (2) No action takes place, the state remains the same, but response indicates badValue. (3) The state is changed to verify, a consistency check is started, and response indicates noError. Once the consistency check is completed, the state automatically changes to done. (4) The buffered copy of all parameter objects is discarded, the state is changed to normal, and response indicates noError. (5) The buffered copy of all parameter objects is not changed or reloaded, the state is changed to transaction, and response indicates noError. (6) If dbVerifyStatus indicates doneWithNoError, then the copy of all parameter objects is transferred to memory, the state is changed to normal and response indicates noError. If dbVerifyStatus indicates doneWithError then the buffered data is discarded, the state is changed to NORMAL, and response indicates noError. (7) The state automatically changes to done when the consistency check completes. (8) dbVerifyStatus and dbVerifyError are only valid in this state. (9) All SET operations on this (dbCreateTransaction) parameter shall be made using a protocol that uses a community name, or equivalent field (e.g., SNMP). NTCIP1201v04-DB-MGMT.dbCreateTransactionV2 The original version of this object referenced SNMPv1 error codes, community names, and an administrator name; the V2 object updates these details to be SNMPv3 specific. 1.3.6.1.4.1.1206.4.2.6.2.1" DEFVAL {normal} ::= { globalDBManagement 1 } -- 5.4.2 Database Error Type Parameter dbErrorType OBJECT-TYPE SYNTAX INTEGER { tooBig (1), noSuchName (2), badValue (3), readOnly (4), genError (5), updateError (6), noError (7)} MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object returns the current error status of the transaction. The value of this object is only valid when the dbCreateTransaction object is in the Done or Error state. This object was deprecated in NTCIP 12012 v02 1.3.6.1.4.1.1206.4.2.6.2.2" ::= { globalDBManagement 2 } -- 5.4.3 Database Error ID Parameter dbErrorID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object contains the object identifier of the first object in the transaction buffer that caused an error while dbCreateTransaction object was in the Verifying or Updating state. The value of this object is only valid when the dbCreateTransaction object is in the Error state. It is undefined when the dbCreateTransaction object is in other states. This object was deprecated in NTCIP 12012 v02 1.3.6.1.4.1.1206.4.2.6.2.3" ::= { globalDBManagement 3 } -- 5.4.4 Database Transaction ID Parameter dbTransactionID OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the transaction ID value that is to be contained in all SET operation writes while the dbCreateTransaction object is not in the Normal state. During transaction operations every SET command shall begin with a write to this object with the current value of this object. If a SET operation is performed without writing to this object, or with a value that does not match the current value, then an error response of 'genError' shall be returned. This mechanism is used to determine that the same management station that started the transaction is performing the SET operations that are being buffered or modifying the state of dbCreateTransaction. This object was deprecated in NTCIP 12012 v02 1.3.6.1.4.1.1206.4.2.6.2.4" ::= { globalDBManagement 4 } -- 5.4.5 Database Make ID Parameter dbMakeID OBJECT-TYPE SYNTAX Integer32(0..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object is used to create unique transaction ID's for management stations to use when starting transactions using the dbCreateTransaction object. This object will be incremented by one every time it is read, so that different values will be returned for each read. Management stations wishing to start a transaction should first read the dbCreateTransaction object to verify that it is in the Normal state. If so then the management shall GET dbMakeID to obtain a transaction ID to use, then SET dbCreateTransaction to startCmd and dbTransactionID to the value just received. If the response to the SET operation is 'noError' then the management station has started a transaction. If the response to the SET operation is 'genError' then the management station should read the dbCreateTransaction and dbTransactionID objects to ensure that the error was not due to a communications retry. If the dbCreateTransaction is in the Transaction state, and the dbTransactionID is the same value returned by the read of this object, then the management station is the owner of the transaction. If the dbTransactionID does not match the value originally returned by this object, then the management station is not the owner of the transaction and must wait until the dbCreateTransaction object returns to the Normal state before attempting to start the transaction. This object was deprecated in NTCIP 12012 v02 1.3.6.1.4.1.1206.4.2.6.2.5" ::= { globalDBManagement 5 } -- 5.4.6 Database Verify Status Parameter dbVerifyStatus OBJECT-TYPE SYNTAX INTEGER { notDone (1), doneWithError (2), doneWithNoError (3) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object indicates the current status of verify (consistency checking) processing. The value of this object is only meaningful when the dbCreateTransaction object is in the Verify or Done state. NTCIP1201v04-DB-MGMT.dbVerifyStatusV2 The V2 object adds support for error codes related to Implementing the database after consistency checks have passed. 1.3.6.1.4.1.1206.4.2.6.2.6" ::= { globalDBManagement 6 } -- 5.4.7 Database Verify Error Parameter dbVerifyError OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..255)) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object contains a textual description of or a reference to an error that was found by the verify (consistency checking) processing. The value of this object is only meaningful when the dbCreateTransaction object is in the Done state and the dbVerifyStatus object is in the doneWithError state. NTCIP1201v04-DB-MGMT.dbVerifyErrorV2 The V2 object revises the syntax so that it can be automatically recognized as a multi-lingual text string (i.e., SnmpAdminString). 1.3.6.1.4.1.1206.4.2.6.2.7" ::= { globalDBManagement 7 } -- 5.5 GLOBAL TIME MANAGEMENT NODE globalTimeManagement OBJECT-IDENTITY STATUS current DESCRIPTION "This node is an identifier used to organize all objects for support of time-related functions that are common to most device types. 1.3.6.1.4.1.1206.4.2.6.3" ::= { global 3 } -- 5.5.1 Global Time Parameter globalTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The number of seconds since the epoch of 00:00:00 (midnight) January 1, 1970 UTC (a.k.a. Zulu or GMT). CLOCK-MIB.fdClockUtcDate & CLOCK-MIB.fdClockUtcTime (ISO 20684-7) The original specification defined this parameter using a Counter; however, by convention, Counter objects are not supposed to be writable in SNMPv1 and SNMPv3 prohibits writable Counter objects. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than a Counter32; proxy agents will need to address this encoding change within their implementation. In addition, the object has a potential rollover problem in 2038 and there are NTCIP needs to support millisecond-level time information. The superseding objects address all of these issues. 1.3.6.1.4.1.1206.4.2.6.3.1" DEFVAL { 0 } ::= { globalTimeManagement 1} -- 5.5.2 Global Daylight Saving Parameter globalDaylightSaving OBJECT-TYPE SYNTAX INTEGER { other (1), disableDST (2), enableUSDST (3), enableEuropeDST (4), enableAustraliaDST (5), enableTasmaniaDST (6), enableEgyptDST (7), enableNamibiaDST (8), enableIraqDST (9), enableMangoliaDST (10), enableIranDST (11), enableFijiDST (12), enableNewZealandDST (13), enableTongaDST (14), enableCubaDST (15), enableBrazilDST (16), enableChileDST (17), enableFalklandsDST (18), enableParaguayDST (19), enableDaylightSavingNode (20) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies whether the daylight saving time (DST) is enabled, disabled or some other form of DST is active. other - DST adjustments by a mechanism not defined within this standard. disableDST - DST clock adjustments shall NOT occur. enableUSDST - DST shall begin the first Sunday in April and shall end the last Sunday of October. All changes of time occur at 2:00 AM. (This is the pre-2007 DST settings for the USA.) enableEuropeDST - DST shall start the last Sunday of March at 2:00 AM and ends the last Sunday of October at 3:00 AM. enableAustraliaDST - DST shall start the last Sunday in October at 2:00 AM and ends the last Sunday in March at 2:00 AM. enableTasmaniaDST - DST shall start the first Sunday in October at 2 a.m. and ends the last Sunday in March at 3 a.m. enableEgyptDST: DST shall start the last Friday in April and end the last Thursday in September. enableNamibiaDST: DST shall start the first Sunday in September and end the first Sunday in April. enableIraqDST: DST shall start on April 1 and end on October 1. enableMongoliaDST: DST shall start the last Sunday in March and end the last Sunday in September. enableIranDST: DST shall start the first day of Farvardin and end the first day of Mehr enableFijiDST: DST shall start the first Sunday in November and end the last Sunday in February. enableNewZealandDST: DST shall start the first Sunday in October and end the first Sunday on or after March 5th. enableTongaDST: DST shall start the first Saturday in October and end the first Saturday on or after April 15th. enableCubaDST: DST shall start April 1st and end last Sunday in October. enableBrazilDST: DST shall start the first Sunday in October and end the last Sunday in February. enableChileDST: DST shall start the first Sunday on or after October 9th and end the first Sunday on or after March 9th. enableFalklandsDST: DST shall start the first Sunday on or after September 8th and end the first Sunday on or after April 8th. enableParaguayDST: DST shall start the first Sunday in October and end the last Saturday in February. enableDaylightSavingNode: DST operation is controlled by objects located under the daylightSavingNode. DST table This object was deprecated in NTCIP 1201 v03. This object is maintained for backward compatibility and it is envisioned that only the following values are supported with all other values are deprecated: - other (1), - disableDST (2), - enableDaylightSavingNode (20) NOTE: Users should ensure that the values of globalDaylightSaving and the entries in the new DST Table are coordinated. The globalDaylightSaving object is intended to be used to enable and disable DST and should not be set to the value '20', enableDaylightSavingNode until after the dstTable entries have been fully configured. Further, the globalDaylightSaving object supersedes the settings in the DST Table. 1.3.6.1.4.1.1206.4.2.6.3.2" REFERENCE "NEMA TS 2 Clause 3.8.2; http://fatty.law.cornell.edu/uscode/15/260a.html; http://webexhibits.org/daylightsaving/g.html " DEFVAL { enableDaylightSavingNode } ::= { globalTimeManagement 2 } -- 5.6 TIMEBASE EVENT SCHEDULER NODE timebase OBJECT-IDENTITY STATUS current DESCRIPTION "This node is an identifier used to organize the main objects for event scheduling. Device type-specific objects (tables) pointed to are defined within the appropriate MIB. 1.3.6.1.4.1.1206.4.2.6.3.3" ::= { globalTimeManagement 3 } -- 5.6.1 Maximum Number of Time Base Schedule Entries Parameter maxTimeBaseScheduleEntries OBJECT-TYPE SYNTAX Integer32(1..65535) UNITS " TimeBaseScheduleEntry" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The value of this object specifies the maximum number of different entries supported by the device as shown by the number of rows in the timeBaseScheduleTable. The timeBaseScheduleTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.2.6.3.3.1" ::= { timebase 1 } -- 5.6.2 Time Base Schedule Table timeBaseScheduleTable OBJECT-TYPE SYNTAX SEQUENCE OF TimeBaseScheduleEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table containing the time base schedule parameters for the device. The number of rows in this table shall be equal to the maxTimeBaseScheduleEntries object. The table references the appropriate day plan for the device. The plan is determined by comparing the current month (MONTH), day of week (DOW) and date of month (DOM) to the appropriate fields. The settings for MONTH, DOW and DOM are connected with a logical AND. To determine which timebased event to select, determine the event which has the most specific date specified. Select the more specific event based on their MONTH settings; if the same, select the most specific DOM; if that is still the same, select the most specific DOW; if still the same, the first occurrence within the time base event table shall be selected. 'More specific' means the least number of bits set within an object. All entries in Time Base Schedule Table are expressed in local time and date. A row in the table may be deactivated by setting the Month, Day, Date, or DayPlan parameters to zero (0) static DAY-PLAN-MIB.fdDayPlanScheduleTable (ISO 20684-3) The original timeBaseScheuleDate object was defined as INTEGER (0..4294967295); however, by convention, SNMPv1 does not allow unsigned 32-bit integers and SNMPv3 prohibits them. The revise table addresses this issue and is also treated using trigger logic so that it can be used to activate a day plan (as originally envisioned) and/or to call other actions (e.g., creating a log entry). 1.3.6.1.4.1.1206.4.2.6.3.3.2" ::= { timebase 2 } timeBaseScheduleEntry OBJECT-TYPE SYNTAX TimeBaseScheduleEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " Event Parameters for the time based schedule programming of the device. DAY-PLAN-MIB.fdDayPlanScheduleEntry (ISO 20684-3) The replacement object extends the row to support a description and supports full SNMPv3 row management. 1.3.6.1.4.1.1206.4.2.6.3.3.2.1" INDEX { timeBaseScheduleNumber } ::= { timeBaseScheduleTable 1 } TimeBaseScheduleEntry ::= SEQUENCE { timeBaseScheduleNumber Integer32, timeBaseScheduleMonth Integer32, timeBaseScheduleDay Integer32, timeBaseScheduleDate Integer32, timeBaseScheduleDayPlan Integer32 } -- 5.6.2.1 Time Base Schedule Number Parameter timeBaseScheduleNumber OBJECT-TYPE SYNTAX Integer32(1..65535 ) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The time base schedule number for objects in this row. The value of this object shall not exceed the value of the maxTimeBaseScheduleEntries object. The activation of a scheduled entry shall occur whenever allowed by all other objects within this table. DAY-PLAN-MIB.fdDayPlanScheduleNumber (ISO 20684-3) The replacement object extends the range to an Unsigned32 1.3.6.1.4.1.1206.4.2.6.3.3.2.1.1" ::= { timeBaseScheduleEntry 1 } -- 5.6.2.2 Time Base Schedule Month of Year Parameter timeBaseScheduleMonth OBJECT-TYPE SYNTAX Integer32(0..65535) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The Month(s) Of the Year that the schedule entry shall be allowed. Each bit represents a specific month. If the bit is set to one (1), then the scheduled entry shall be allowed during the associated month. If the bit is set to zero (0), then the scheduled entry shall not be allowed during the associated month. The bits are defined as: Bit Month of Year 0 Reserved 1 January 2 February 3 March 4 April 5 May 6 June 7 July 8 August 9 September 10 October 11 November 12 December 13 - 15 Reserved Thus, a value of six (6) would indicate that the entry would only be allowed during the months of January and February. A value of zero (0) shall indicate that this row has been disabled. DAY-PLAN-MIB.fdDayPlanScheduleMonth (ISO 20684-3) The replacement object is defined using the BITS structure. 1.3.6.1.4.1.1206.4.2.6.3.3.2.1.2" ::= { timeBaseScheduleEntry 2 } -- 5.6.2.3 Time Base Schedule Day of Week Parameter timeBaseScheduleDay OBJECT-TYPE SYNTAX Integer32(0..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The Day(s) Of Week that the schedule entry shall be allowed. Each bit represents a specific day of the week. If the bit is set to one (1), then the scheduled entry shall be allowed during the associated DOW. If the bit is set to zero (0), then the scheduled entry shall not be allowed during the associated DOW. The bits are defined as: Bit Day of Week 0 Reserved ('Holiday', not defined by this standard) 1 Sunday 2 Monday 3 Tuesday 4 Wednesday 5 Thursday 6 Friday 7 Saturday Thus, a value of six (6) would indicate that the entry would only be allowed on Sundays and Mondays. A value of zero (0) shall indicate that this row has been disabled. DAY-PLAN-MIB.fdDayPlanScheduleDayOfWeek (ISO 20684-3) The replacement object is defined using the BITS structure 1.3.6.1.4.1.1206.4.2.6.3.3.2.1.3" ::= { timeBaseScheduleEntry 3 } -- 5.6.2.4 Time Base Schedule Date Parameter timeBaseScheduleDate OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The Day(s) Of a Month that the schedule entry shall be allowed. Each bit represents a specific date of the month. If the bit is set to one (1), then the scheduled entry shall be allowed during the associated date. If the bit is set to zero (0), then the scheduled entry shall not be allowed during the associated date. The bits are defined as: Bit Day Number 0 Reserved 1 Day 1 2 Day 2 || 31 Day 31 Thus, a value of six (6) would indicate that the entry would only be allowed on the first and second of the allowed months. A value of zero (0) shall indicate that this row has been disabled. DAY-PLAN- MIB.fdDayPlanScheduleDayOfMonth (ISO 20684-3) The original specification defined this parameter using INTEGER (0..4294967295); however, by convention, INTEGERs are limited to the range (- 2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. The replacement object in the DAY-PLAN-MIB implements this concept using the BITS structure. 1.3.6.1.4.1.1206.4.2.6.3.3.2.1.4" ::= { timeBaseScheduleEntry 4 } -- 5.6.2.5 Time Base Schedule Day Plan Parameter timeBaseScheduleDayPlan OBJECT-TYPE SYNTAX Integer32(0..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies what Plan number shall be associated with this timeBaseScheduleDayPlan object. The value of this object cannot exceed the value of the maxDayPlans object. A value of zero (0) shall indicate that this row has been disabled. DAY-PLAN-MIB.fdDayPlanScheduleDayPlan (ISO 20684-3) The replacement object extends the range to Unsigned32 1.3.6.1.4.1.1206.4.2.6.3.3.2.1.5" ::= { timeBaseScheduleEntry 5 } -- 5.6.3 Maximum Number of Day Plans-Parameter maxDayPlans OBJECT-TYPE SYNTAX Integer32(1..255) UNITS "DayPlan" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The value of this object specifies the maximum, fixed number of different timebased Day Plans supported by the device. The value of this object represents the number of day plans (primary key into the table) available in the timeBaseDayPlanTable. The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.2.6.3.3.3" ::= { timebase 3 } -- 5.6.4 Maximum Number of Day Plan Events-Parameter maxDayPlanEvents OBJECT-TYPE SYNTAX Integer32(1..255) UNITS "DayPlanEvent" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The value of this object specifies the fixed number of different timebased Day Plan Events within each Day Plan supported by the device. The value of this object represents the number of rows (secondary key into the table) available within each of the day plans that are available in the timeBaseDayPlanTable. All day plans shall have the same number of day plan events available for use. The timeBaseDayPlanTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.2.6.3.3.4" ::= { timebase 4 } -- 5.6.5 Day Plan Table timeBaseDayPlanTable OBJECT-TYPE SYNTAX SEQUENCE OF TimeBaseDayPlanEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing day plan numbers, the times when to implement them and the associated actions. The number of rows in this table shall be equal to the product of the maxDayPlans object and the maxDayPlanEvents object. The dayPlanNumbers within this table shall begin with day plan number 1 and increment by one to the maxDayPlans. The dayPlanEventNumbers within this table shall begin with day plan event number 1 and increment by one to the maxDayPlanEvents. This table is always used in association with device-type specific objects specifying device-type specific actions such as activating a message on a VMS sign or initiating a pattern for a signal controller. A device MIB that defines an action table should define the relative priority of the action table as compared to the priority of system and other commands. The device-type specific action is only initiated when (1) the specific DayPlan has been activated, (2) the scheduler has sufficient priority to override the current operation of the device, and (3) at the indicated time. After a power recovery, or after a change to any object that affects controlerLocalTime, the operational mode called for by the scheduler shall be per the last event that would have been called for by the currently defined schedule; the logic searches for all events that may have occurred for at least the previous 24 hours. static DAY-PLAN-MIB.fdDayPlanTable & DAY-PLAN-MIB.fdDayPlanTriggerTable (ISO 20684-3) The replacement tables are designed to trigger an action, which can include activating a day plan (as originally envisioned by this object) and/or to call other actions (e.g., creating a log entry). 1.3.6.1.4.1.1206.4.2.6.3.3.5" ::= { timebase 5 } timeBaseDayPlanEntry OBJECT-TYPE SYNTAX TimeBaseDayPlanEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "Day plan parameters for the time based schedule programming of a device. DAY-PLAN-MIB.fdDayPlanEntry & DAY-PLAN-MIB.fdDayPlanTriggerEntry The replacement objects extend the row to support a description of the day plan and supports full SNMPv3 row management. 1.3.6.1.4.1.1206.4.2.6.3.3.5.1" INDEX { dayPlanNumber, dayPlanEventNumber} ::= { timeBaseDayPlanTable 1 } TimeBaseDayPlanEntry ::= SEQUENCE { dayPlanNumber INTEGER, dayPlanEventNumber INTEGER, dayPlanHour INTEGER, dayPlanMinute INTEGER, dayPlanActionNumberOID VariablePointer } -- 5.6.5.1 Day Plan Number dayPlanNumber OBJECT-TYPE SYNTAX Integer32(1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object specifies the day plan number for objects in this row. The value shall not exceed the value of the maxDayPlans object. Day plan numbers are used in the TimeBase Event Table to specify day plan numbers to be implemented on specific days of the year or as part of the week plans. DAY-PLAN-MIB.fdDayPlanNumber (ISO 20684-3) The replacement object extends the range to an Unsigned32 1.3.6.1.4.1.1206.4.2.6.3.3.5.1.1" ::= { timeBaseDayPlanEntry 1 } -- 5.6.5.2 Day Plan Event Number dayPlanEventNumber OBJECT-TYPE SYNTAX Integer32(1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object identifies day plan event number(s) to be scheduled on a specific day plan number. Several different events can be scheduled to take place during a day, and each of these events is one entry or row within a specified day plan number. The total number of events for one day plan shall not exceed the value of the maxDayPlanEvents object. If multiple non-conflicting events are scheduled to occur at the same time, they shall be logically executed in order of their dayPlanEventNumber with the lowest number occurring first. An implementation shall omit lower number actions that are in conflict with higher number actions at the same time. DAY-PLAN-MIB.fdDayPlanTriggerTime (ISO 20684-3) The replacement object (and second index into the replacement table) is the millisecond-based time object. 1.3.6.1.4.1.1206.4.2.6.3.3.5.1.2" ::= { timeBaseDayPlanEntry 2 } -- 5.6.5.3 Day Plan Hour Parameter dayPlanHour OBJECT-TYPE SYNTAX Integer32(0..23) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The Hour of day, as measured by the controllerLocalTime object, that the associated event shall become active. DAY-PLAN-MIB.fdDayPlanTriggerTime (ISO 20684-3) The replacement object includes the complete daily timestamp and is used as an index to the replacement table. 1.3.6.1.4.1.1206.4.2.6.3.3.5.1.3" DEFVAL {0} ::= { timeBaseDayPlanEntry 3 } -- 5.6.5.4 Day Plan Minute Parameter dayPlanMinute OBJECT-TYPE SYNTAX Integer32(0..59) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The Minute of the hour (defined in the dayPlanHour), as measured by the controllerLocalTime object, that the associated event shall become active. DAY-PLAN-MIB.fdDayPlanTriggerTime (ISO 20684-3) The replacement object includes the complete daily timestamp and is used as an index to the replacement table. 1.3.6.1.4.1.1206.4.2.6.3.3.5.1.4" DEFVAL {0} ::= { timeBaseDayPlanEntry 4 } -- 5.6.5.5 Day Plan Action Number OID Parameter dayPlanActionNumberOID OBJECT-TYPE SYNTAX VariablePointer MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object provides a reference to the device-type specific action that shall be executed. The object shall reference the action by its associated object identifier, including its instance (i.e., the full OID of the scalar or columnar object). Only objects whose description field explicitly states that they may be called by the action table may be referenced. If a management system attempts to set this value to any other object identifier, the device shall respond with a genErr. Any object allowing the action table to reference it shall define precisely what action takes place when it is activated, and whether the action is transitionary or continuous until deactivated. The object shall also define what, if any, restrictions may be placed on other operations the device may be able to perform. If the action to be performed is defined by a row of a table, one of the index columns should be identified as the explicit object that is referenced. DAY-PLAN-MIB.fdDayPlanTriggerOwner & DAY-PLAN-MIB.fdDayPlanTriggerName (ISO 20684-3) The replacement objects provide the two indicies necessary to identify a unique row into the fdActionTable. 1.3.6.1.4.1.1206.4.2.6.3.3.5.1.5" DEFVAL { zeroDotZero } ::= { timeBaseDayPlanEntry 5 } -- 5.6.6 Day Plan Status Parameter dayPlanStatus OBJECT-TYPE SYNTAX Integer32(0..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object indicates the current value of the active dayPlanNumber-object. A value of zero (0) indicates that there is no dayPlanNumber that is currently active. DAY-PLAN-MIB.fdDayPlanSchedulerCurrentDayPlan (ISO 20684-3) 1.3.6.1.4.1.1206.4.2.6.3.3.6" ::= { timebase 6 } -- 5.6.7 Schedule Status Parameter timeBaseScheduleTableStatus OBJECT-TYPE SYNTAX Integer32(0..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object indicates the number of the TimeBaseSchedule which is currently selected by the scheduling logic; the device may or may not be using the selected schedule. The value of zero (0) indicates that there is no timeBaseScheduleNumber that is currently selected. DAY-PLAN-MIB.fdDayPlanSchedulerSelectedRule (ISO 20684-3) 1.3.6.1.4.1.1206.4.2.6.3.3.7" ::={timebase 7} -- 5.6.8 Global Local Time Differential Parameter globalLocalTimeDifferential OBJECT-TYPE SYNTAX Integer32(-43200..43200) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "Indicates the number of seconds offset between local time and GMT. Positive values indicate local times in the Eastern Hemisphere up to the International Date Line and negative values indicate local times in the Western Hemisphere back to the International Date Line. If one of the daylight saving times is activated, this value will change automatically at the referenced time. For example, Central Standard Time (CST) is -21600 and Central Daylight Time (CDT) is -18000. controllerStandardTimeZone This object was deprecated in NTCIP 1202 v02 to prevent confusion when setting time near a DST event. 1.3.6.1.4.1.1206.4.2.6.3.4" ::= { globalTimeManagement 4 } -- 5.6.9 Standard Time Zone Parameter controllerStandardTimeZone OBJECT-TYPE SYNTAX Integer32(-43200..43200) UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " Indicates the number of seconds offset between local Standard Time and GMT. Positive values indicate local times in the Eastern Hemisphere up to the International Date Line and negative values indicate local times in the Western Hemisphere back to the International Date Line. This value does not change in response to a DST event. CLOCK-MIB.fdClockLocalStandardTimeZone (ISO 20684-7) The replacement object extends the range to (-46800..46800) to support all defined time zones (i.e., +/- 13 hours). 1.3.6.1.4.1.1206.4.2.6.3.5" DEFVAL {0} ::= { globalTimeManagement 5 } -- 5.6.10 Local Time Parameter controllerLocalTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The current local time expressed in seconds since 00:00:00 (midnight) January 1, 1970 of the same time offset. This value changes by 3600 seconds in response to a DST event. CLOCK-MIB.fdClockLocalDate & CLOCK-MIB.fdClockLocalTime (ISO 20684-7) The original specification defined this parameter using a Counter; however, by convention, Counter objects are supposed to follow the defined semantics for a counter in SNMPv1 and SNMPv3 requires this compliance. This object fails to meet this standard because it is not always increasing. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than a Counter32; proxy agents will need to address this encoding change within their implementation. 1.3.6.1.4.1.1206.4.2.6.3.6" ::= { globalTimeManagement 6 } -- 5.7 DAYLIGHT SAVING TIME (DST) NODE daylightSavingNode OBJECT-IDENTITY STATUS deprecated DESCRIPTION "This node is an identifier used to organize all objects for support of defining DST. This function is common to most device types. The The objects under this node only affect device operation when globalDaylightSaving = enableDaylightSavingNode (20). See Annex A.2.2 for examples. 1.3.6.1.4.1.1206.4.2.6.3.7" ::= { globalTimeManagement 7 } -- 5.7.1 Maximum Daylight Saving Time (DST) Table Entries Parameter maxDaylightSavingEntries OBJECT-TYPE SYNTAX Integer32(1..100) UNITS "entries" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The maximum number of entries (begin and end date pairs) that the DST Table can contain within the device. As of July 2007, devices used within the United States only require 1 entry when using the generic begin and end date method. It is expected that, for devices using the absolute date method, the device would need to support at least 1 entry per year programmed. For multi-step DST transitions, a minimum of 2 rows are required (see Annex A.2.1 Figure 6). More than one row may be required if absolute date method (see Section 2.4.8.2.2) is used for more than one year, or if more than one time change is implemented in a given year. CLOCK-MIB.fdClockDstMaxEntries (ISO 20684-7) The replacement object has a range of Unsigned32 1.3.6.1.4.1.1206.4.2.6.3.7.1" ::= { daylightSavingNode 1 } -- 5.7.2 Daylight Saving Time (DST) Table Parameter dstTable OBJECT-TYPE SYNTAX SEQUENCE OF DstEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table containing DST Begin and End dates. The table is useful for agencies with multiple daylight saving time incremental steps per year. The number of rows in this table is equal to the maxDaylightSavingEntries object. static CLOCK-MIB.fdClockDstTable (ISO 20684-7) The original table contained two SecondsToTransition objects that have an invalid syntax for SNMPv3. 1.3.6.1.4.1.1206.4.2.6.3.7.2" ::= { daylightSavingNode 2 } dstEntry OBJECT-TYPE SYNTAX DstEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " The DST Begin and End dates parameters. CLOCK-MIB.fdClockDstEntry (ISO 20684-7) The replacement object extends the row to support a status object for each row (showing whether the plan is activated) as well as a RowStatus object to disable defined rows. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1" INDEX { dstEntryNumber } ::= { dstTable 1 } DstEntry ::= SEQUENCE { dstEntryNumber INTEGER, dstBeginMonth INTEGER, dstBeginOccurrences INTEGER, dstBeginDayOfWeek INTEGER, dstBeginDayOfMonth INTEGER, dstBeginSecondsToTransition INTEGER, dstEndMonth INTEGER, dstEndOccurrences INTEGER, dstEndDayOfWeek INTEGER, dstEndDayOfMonth INTEGER, dstEndSecondsToTransition INTEGER, dstSecondsToAdjust INTEGER } -- 5.7.2.1 Daylight Saving Time (DST) Entry Number Parameter dstEntryNumber OBJECT-TYPE SYNTAX Integer32(1..100) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The entry number for the DST objects in this row. This value shall not exceed the maxDaylightSavingEntries object value. CLOCK-MIB.fdClockDstIndex (ISO 20684-7) The replacement object has a range of ITSPositive8 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.1" ::= { dstEntry 1 } -- 5.7.2.2 Daylight Saving Time (DST) Beginning Month Parameter dstBeginMonth OBJECT-TYPE SYNTAX INTEGER { january (1), february (2), march (3), april (4), may (5), june (6), july (7), august (8), september (9), october (10), november (11), december (12), absolute (13), disabled (14)} MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The month during which daylight saving time (DST) begins. An entry of 'absolute' means that dstBeginSecondsToTransition defines an absolute time to begin DST relative to midnight January 1, 1970. In this case, any value indicated in the dstEndMonth, dstBeginOccurences, dstBeginDayOfWeek, dstBeginDayOfMonth, dstEndOccurances, dstEndDayOfWeek, and dstEndDayOfMonth objects are irrelevant, and the dstEndSecondsToTransition object defines an absolute time to end DST relative to midnight January 1, 1970. If the daylightSavingNode is enabled (i.e. globalDaylightSaving = enableDaylightSavingNode), and the value of this object is disabled(14), then the values in the remaining objects in this row of the dstTable are irrelevant and therefore ignored by the device. CLOCK-MIB.fdClockDstBeginMonth (ISO 20684-7) The replacement object does not support absolute mode and disabling a row is achieved through the RowStatus object. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.2" DEFVAL { march } ::= { dstEntry 2 } -- 5.7.2.3 Daylight Saving Time (DST) Beginning Occurrence Parameter dstBeginOccurrences OBJECT-TYPE SYNTAX INTEGER { first (1), second (2), third (3), fourth (4), last (5), secondLast (6), thirdLast (7), fourthLast (8), specificDayOfMonth (9) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "For values of 1-4, the number of occurrences of the specific day of week that shall occur on or after dstBeginDayOfMonth until the daylight saving transition shall take place. For values of 5-8, the number of occurrences of the specific day of week that shall occur on or before dstBeginDayOfMonth until the daylight saving transition shall take place. For value = 9, dstBeginDayOfMonth defines the specific day of the month that the DST transition occurs regardless of value in dstBeginDayOfWeek object. NOTE: To specify the last occurrence of a specified day of the month, simply specify the last occurrence of the specified day of the week on or before the last day of the month (e.g., 31). CLOCK-MIB.fdClockDstBeginOccurrences (ISO 20684-7) The replacement object has an identical range. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.3" DEFVAL { second } ::= { dstEntry 3 } -- 5.7.2.4 Daylight Saving Time (DST) Beginning Day of Week Parameter dstBeginDayOfWeek OBJECT-TYPE SYNTAX INTEGER { sunday (1), monday (2), tuesday (3), wednesday (4), thursday (5), friday (6), saturday (7) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The Day of the week on which daylight saving time (DST)begins. This object shall only apply if dstBeginOccurrences = 1-8. CLOCK-MIB.fdClockDstBeginDayOfWeek (ISO 20684-7) The replacement object shifts Sunday to the end of the enumeration (7) and all other days up one to conform to international conventions in other standards. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.4" DEFVAL { sunday } ::= { dstEntry 4 } -- 5.7.2.5 Daylight Saving Time (DST) Beginning Day of Month Parameter dstBeginDayOfMonth OBJECT-TYPE SYNTAX Integer32 (1..31) UNITS "days" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " If dstBeginOccurrences = 1-8: The day of the month from which to begin counting occurrences of a specific day of the week (forward for values 1-4, and backwards for values 5-8). If dstBeginOccurrences = 9: The specific day of the month on which the transition occurs. day of month CLOCK-MIB.fdClockDstBeginDayOfMonth (ISO 20684-7) The replacement object has an identical range. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.5" DEFVAL { 1 } ::= { dstEntry 5 } -- 5.7.2.6 Daylight Saving Time (DST) Beginning Seconds to Transition Parameter dstBeginSecondsToTransition OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " If dstBeginMonth = absolute, then this object defines when DST begins based on the seconds from midnight January 1, 1970 (UTC/GMT). If dstBeginMonth = 1-12 (January to December), then this object defines the time when DST begins in seconds past midnight relative to local time (see the controllerLocalTime object). NOTE: a set of parameters that causes a day transition that crosses the midnight boundary may result in unexpected behavior. CLOCK-MIB.fdClockDstBeginTime (ISO 20684-7) The original specification defined this parameter using INTEGER (0..4294967295); however, by convention, INTEGERs are limited to the range (-2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. The replacement object is a daily timestamp to the millisecond and does not support an absolute time. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.6" DEFVAL { 7200 } ::= { dstEntry 6 } -- 5.7.2.7 Daylight Saving Time (DST) Ending Month Parameter dstEndMonth OBJECT-TYPE SYNTAX INTEGER { january (1), february (2), march (3), april (4), may (5), june (6), july (7), august (8), september (9), october (10), november (11), december (12) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The month during which daylight saving time (DST) ends. If the value of dstBeginMonth object = 'absolute' or 'disabled', then the agent shall ignore the value of this object. Otherwise, the value of this object is valid. CLOCK-MIB.fdClockDstEndMonth (ISO 20684-7) The replacement object has an identical syntax. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.7" DEFVAL { november } ::= { dstEntry 7 } -- 5.7.2.8 Daylight Saving Time (DST) Ending Occurrences Parameter dstEndOccurrences OBJECT-TYPE SYNTAX INTEGER { first (1), second (2), third (3), fourth (4), last (5), secondLast (6), thirdLast (7), fourthLast (8), specificDayOfMonth (9) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "For values of 1-4, the number of occurrences of the specific day of week that shall occur on or after dstEndDayOfMonth until the daylight saving transition shall take place. For values of 5-8, the number of occurrences of the specific day of week that shall occur on or before dstEndDayOfMonth until the daylight saving transition shall take place. For value = 9, dstEndDayOfMonth defines the specific day of the month that the DST transition occurs regardless of value in dstEndDayOfWeek object. NOTE: To specify the last occurrence of a specified day of the month, simply specify the last occurrence of the specified day of the week on or before the last day of the month (e.g. 31). CLOCK-MIB.fdClockDstEndOccurrences (ISO 20684-7) The replacement object has an identical range. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.8" DEFVAL { first } ::= { dstEntry 8 } -- 5.7.2.9 Daylight Saving Time (DST) Ending Day of Week Parameter dstEndDayOfWeek OBJECT-TYPE SYNTAX INTEGER { sunday (1), monday (2), tuesday (3), wednesday (4), thursday (5), friday (6), saturday (7) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The Day of the week on which daylight saving time (DST) ends. This object shall only apply if dstEndOccurrences = 1-8. CLOCK-MIB.fdClockDstEndDayOfWeek (ISO 20684-7) The replacement object shifts Sunday to the end of the enumeration (7) and all other days up one to conform to international conventions in other standards. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.9" DEFVAL { sunday } ::= { dstEntry 9 } -- 5.7.2.10 Daylight Saving Time (DST) Ending Day of Month Parameter dstEndDayOfMonth OBJECT-TYPE SYNTAX Integer32(1..31) UNITS "days" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " If dstEndOccurrences = 1-8: The day of the month from which to begin counting occurrences of a specific day of the week (forward for values 1-4, and backwards for values 5-8). If dstEndOccurrences = 9: The specific day of the month on which the transition occurs. CLOCK-MIB.fdClockDstEndDayOfMonth (ISO 20684-7) The replacement object has an identical range. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.10" DEFVAL { 1 } ::= { dstEntry 10 } -- 5.7.2.11 Daylight Saving Time (DST) Ending Seconds to Transition Parameter dstEndSecondsToTransition OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " If dstBeginMonth = absolute, then this object defines when DST ends based on the seconds from midnight January 1, 1970 (UTC/GMT). If dstBeginMonth = 1-12 (January to December), then this object defines the time when DST ends in seconds past midnight relative to local time (see the controllerLocalTime object). NOTE: a set of parameters that causes a day transition that crosses the midnight boundary may result in unexpected behavior. CLOCK-MIB.fdClockDstEndTime (ISO 20684-7) The original specification defined this parameter using INTEGER (0..4294967295); however, by convention, INTEGERs are limited to the range (-2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. The replacement object is a daily timestamp to the millisecond and does not support an absolute time. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.11" DEFVAL { 7200 } ::= { dstEntry 11 } -- 5.7.2.12 Daylight Saving Time (DST) Seconds to Adjust Parameter dstSecondsToAdjust OBJECT-TYPE SYNTAX Integer32 (0..21600) UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This is the absolute offset in seconds that will be added to the local time reference point to determine the local time when DST is in effect as specified by this row entry. Values of this object in adjacent rows, even if they overlap, are not cumulative. That is, the row with the latest dstBegin time, which has not terminated due to passing the dstEnd time, shall determine the setting of the local TOD clock; the dstSecondsToAdjust for the latest dstBegin governs the Local TOD clock settings. The maximum offset to adjust is 21600 seconds, an equivalent of 6 hours. CLOCK-MIB.fdClockDstOffset (ISO 20684-7) This object allows what may be considered an exception, in that it is possible and allowed to configure an adjustment backward past midnight. The replacement object uses an ITSInteger16 range. 1.3.6.1.4.1.1206.4.2.6.3.7.2.1.12" DEFVAL { 3600 } ::= { dstEntry 12 } -- 5.8 PMPP OBJECT NODE profilesPMPP OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to group all objects for support of the PMPP function that are common to all device types. The objects under this node are placed under the Protocols\Profiles\PMPP subtree within the NEMA node, but they have been listed here due to the lack of a separate document that lists these objects. PMPP is a historic protocol designed for multi-drop serial communication networks with typical data capacities of 9600 bits per second or less. The overhead of X.509 security certificates and the availability of alternate communication technologies has resulted in the decision to no longer maintain this protocol and the deprecation of all of its management objects. 1.3.6.1.4.1.1206.4.1.2.3" ::= { profiles 3 } -- 5.8.1 Maximum HDLC Group Address Parameter maxGroupAddresses OBJECT-TYPE SYNTAX Integer32(1..255) UNITS "addresses" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The maximum number of group addresses this device supports. This object indicates the maximum number of rows in the hdlcGroupAddressTable. The PMPP protocol has been deprecated and there is no replacement object. 1.3.6.1.4.1.1206.4.1.2.3.1" ::= {profilesPMPP 1 } -- 5.8.2 HDLC Group Address Table hdlcGroupAddressTable OBJECT-TYPE SYNTAX SEQUENCE OF HdlcGroupAddressEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table containing group addresses at which a device may receive frames. static The PMPP protocol has been deprecated and there is no replacement object. 1.3.6.1.4.1.1206.4.1.2.3.2" ::= { profilesPMPP 2 } hdlcGroupAddressEntry OBJECT-TYPE SYNTAX HdlcGroupAddressEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " An entry in the group address table that contains a device's data link layer group address at which it will accept frames. The PMPP protocol has been deprecated and there is no replacement object. 1.3.6.1.4.1.1206.4.1.2.3.2.1" INDEX { hdlcGroupAddressIndex } ::= { hdlcGroupAddressTable 1 } HdlcGroupAddressEntry ::= SEQUENCE { hdlcGroupAddressIndex INTEGER, hdlcGroupAddress INTEGER, -- deprecated previously hdlcGroupAddressNumber INTEGER } -- 5.8.2.1 HDLC Group Address Index Parameter hdlcGroupAddressIndex OBJECT-TYPE SYNTAX Integer32(1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The index number for the group address in this row. The PMPP protocol has been deprecated and there is no replacement object. 1.3.6.1.4.1.1206.4.1.2.3.2.1.1" ::= { hdlcGroupAddressEntry 1} -- 5.8.2.2 HDLC Group Address Parameter hdlcGroupAddress OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION " A group address for the data link layer. For PMPP, the syntax is an 8 or 16 bit entry with the second low order bit set to a one indicating that this is a group address. This object was deprecated in NTCIP 1201 v03. The PMPP protocol has been deprecated and there is no replacement object. 1.3.6.1.4.1.1206.4.1.2.3.2.1.2" REFERENCE "NEMA TS 3.3 Clause 3.3.3.1" ::= { hdlcGroupAddressEntry 2} -- 5.8.2.3 HDLC Group Address Number Parameter hdlcGroupAddressNumber OBJECT-TYPE SYNTAX Integer32(0..62) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " A group address number prior to any encoding for the data link layer. The address of 63 is reserved for the all stations address. The value of zero (0) shall disable this row of the table. NOTE that in PMPP all group addresses are encoded in one byte. The PMPP protocol has been deprecated and there is no replacement object. 1.3.6.1.4.1.1206.4.1.2.3.2.1.3" REFERENCE "NTCIP 2101" DEFVAL { 0 } ::= { hdlcGroupAddressEntry 3} -- 5.9 COMPLIANCE GROUPS -- 5.9.1 Global Configuration Identifier Group globalConfigIDGroup OBJECT-GROUP OBJECTS { globalSetIDParameter } STATUS deprecated DESCRIPTION " The objects necessary for monitoring the configuration of the device. 1.3.6.1.4.1.1206.4.2.6.8.127.2.1" ::= {globalGroups 1} -- 5.9.2 Global Module Group globalModuleGroup OBJECT-GROUP OBJECTS { globalMaxModules, moduleNumber, moduleDeviceNode, moduleMake, moduleModel, moduleVersion, moduleType } STATUS deprecated DESCRIPTION " The objects necessary for determining the modules contained in the device. 1.3.6.1.4.1.1206.4.2.6.8.127.2.2" ::= {globalGroups 2} -- 5.9.3 Global Base Standards Group globalBaseStandardsGroup OBJECT-GROUP OBJECTS { controllerBaseStandards } STATUS deprecated DESCRIPTION " The objects necessary for determining the standards supported by the device. 1.3.6.1.4.1.1206.4.2.6.8.127.2.3" ::= {globalGroups 3} -- 5.9.4 Global Database Management Group globalDbMgmtV1GroupR1 OBJECT-GROUP OBJECTS { dbCreateTransaction, dbErrorType, dbErrorID, dbTransactionID, dbMakeID } STATUS deprecated DESCRIPTION " The objects necessary for managing the original database management logic for the device. 1.3.6.1.4.1.1206.4.2.6.8.127.2.4" ::= {globalGroups 4} -- 5.9.5 Global Database Management Group Revision 2 globalDbMgmtV1GroupR2 OBJECT-GROUP OBJECTS { dbCreateTransaction, dbVerifyStatus, dbVerifyError } STATUS deprecated DESCRIPTION " The objects necessary for managing the database transaction feature of the device as revised in Amendment 1. 1.3.6.1.4.1.1206.4.2.6.8.127.2.5" ::= {globalGroups 5} -- 5.9.6 Global Time Management UTC Group globalTimeMgmtUtcGroup OBJECT-GROUP OBJECTS { globalTime } STATUS deprecated DESCRIPTION " The objects necessary for managing UTC time. 1.3.6.1.4.1.1206.4.2.6.8.127.2.6" ::= {globalGroups 6} -- 5.9.7 Global Daylight Saving Time Group globalTimeMgmtDstGroupR1 OBJECT-GROUP OBJECTS { globalDaylightSaving, globalLocalTimeDifferential } STATUS deprecated DESCRIPTION " The objects necessary for managing the original DST logic. 1.3.6.1.4.1.1206.4.2.6.8.127.2.7" ::= {globalGroups 7} -- 5.9.8 Global Daylight Saving Time Group Revision 2 globalTimeMgmtDstGroupR2 OBJECT-GROUP OBJECTS { maxDaylightSavingEntries, dstEntryNumber, dstBeginMonth, dstBeginOccurrences, dstBeginDayOfWeek, dstBeginDayOfMonth, dstBeginSecondsToTransition, dstEndMonth, dstEndOccurrences, dstEndDayOfWeek, dstEndDayOfMonth, dstEndSecondsToTransition, dstSecondsToAdjust } STATUS deprecated DESCRIPTION " The objects necessary for managing the DST logic according to a configurable table. 1.3.6.1.4.1.1206.4.2.6.8.127.2.8" ::= {globalGroups 8} -- 5.9.9 Global Local Time Group globalTimeMgmtLocalGroup OBJECT-GROUP OBJECTS { controllerStandardTimeZone, controllerLocalTime } STATUS deprecated DESCRIPTION " The minimum objects necessary for managing local time. 1.3.6.1.4.1.1206.4.2.6.8.127.2.9" ::= {globalGroups 9} -- 5.9.10 Global Time Base Event Group globalTimeBaseEventGroup OBJECT-GROUP OBJECTS { maxTimeBaseScheduleEntries, timeBaseScheduleNumber, timeBaseScheduleMonth, timeBaseScheduleDay, timeBaseScheduleDate, timeBaseScheduleDayPlan, maxDayPlans, maxDayPlanEvents, dayPlanNumber, dayPlanEventNumber, dayPlanHour, dayPlanMinute, dayPlanActionNumberOID, dayPlanStatus } STATUS deprecated DESCRIPTION " The objects necessary for managing the original timebase schedule feature. 1.3.6.1.4.1.1206.4.2.6.8.127.2.10" ::= {globalGroups 10} -- 5.9.11 Global Time Base Event Group Extension globalTimeBaseEventGroupExt OBJECT-GROUP OBJECTS { timeBaseScheduleTableStatus } STATUS deprecated DESCRIPTION " Additional objects used to manage the status of the timebase schedule feature. 1.3.6.1.4.1.1206.4.2.6.8.127.2.11" ::= {globalGroups 11} -- 5.9.12 Global PMPP Group Revision 1 globalPmppGroupR1 OBJECT-GROUP OBJECTS { maxGroupAddresses, hdlcGroupAddressIndex, hdlcGroupAddress } STATUS deprecated DESCRIPTION " The objects necessary for managing the PMPP group addresses. 1.3.6.1.4.1.1206.4.2.6.8.127.2.12" ::= {globalGroups 12} -- 5.9.13 Global PMPP Group Revision 2 globalPmppGroupR2 OBJECT-GROUP OBJECTS { maxGroupAddresses, hdlcGroupAddressIndex, hdlcGroupAddressNumber } STATUS deprecated DESCRIPTION " The objects necessary for managing the PMPP group addresses correcting for an ambiguity. 1.3.6.1.4.1.1206.4.2.6.8.127.2.13" ::= {globalGroups 13} END -- NTCIP1201-GlobalV1 -- Section 6 -- 6.1 AUXILIARY I/O V2 HEADER NTCIP1201-AuxIOv2 DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32, Unsigned32 FROM SNMPv2-SMI -- RFC 2578 DisplayString FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP FROM SNMPv2-CONF global FROM NTCIP1201-Global; auxIOv2 MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the AuxIOv2 objects that were previously defined in NTCIP 1201 v03. Auxiliary I/O was originally defined in NTCIP 1203 v01 under the experimental node. NTCIP 1201 v02 moved the objects to the location defined by this MIB but retained the same object names. Experience demonstrated challenges in compiling MIB files with duplicate object names and as a result NTCIP 1201 v03 changed the names of objects while retaining the NTCIP 1201 v02 object identifiers. NTCIP 1201 v04 deprecated these objects in favor of the general purpose I/O design defined in ISO 20684-2. For those agents that may support these objects and those originally defined under the experimental node (see Section 2.10), the object definitions are treated as aliases such that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in this group is equivalent to a read of the corresponding object in the auxIO group. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.2.6.7 Copyright (C) 2010, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "200610020000Z" DESCRIPTION "NTCIP 1201 v03 - Created this as a standalone MIB. Changed all statuses to 'mandatory' to eliminate checking errors. Revised object names. " ::= { global 7} -- 6.2 OBJECT IDENTITIES -- 6.2.1 AuxIOv2 Conformance Node auxIOv2Conformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define conformance information for the auxIOv2 MIB. 1.3.6.1.4.1.1206.4.2.6.7.127" ::= { auxIOv2 127 } auxIOv2Compliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define compliance statements for the auxIOv2 MIB. 1.3.6.1.4.1.1206.4.2.6.7.127.1" ::= { auxIOv2Conformance 1 } auxIOv2Groups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define object groups for the auxIOv2 MIB. 1.3.6.1.4.1.1206.4.2.6.7.127.2" ::= { auxIOv2Conformance 2 } -- 6.3 OBJECTS -- 6.3.1 Maximum Number of Digital Auxiliary I/Os Parameter maxAuxIOv2TableNumDigitalPorts OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "digital ports" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The number of rows contained in the 'auxIOv2Table' with the auxIOv2PortType set to 'digital'. FIELD-DEVICE-GPIO-MIB.fdGPIOTypeCount (ISO 20684-2) The GPIO count objects are managed by port type. 1.3.6.1.4.1.1206.4.2.6.7.1" ::= { auxIOv2 1} -- 6.3.2 Maximum Number of Analog Auxiliary I/Os Parameter maxAuxIOv2TableNumAnalogPorts OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "analog ports" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows contained in the 'auxIOv2Table' with the auxIOv2PortType set to 'analog'. FIELD-DEVICE-GPIO-MIB.fdGPIOTypeCount (ISO 20684-2) The GPIO count objects are managed by port type. 1.3.6.1.4.1.1206.4.2.6.7.2" ::= {auxIOv2 2} -- 6.3.3 Auxiliary I/O Table Parameter auxIOv2Table OBJECT-TYPE SYNTAX SEQUENCE OF AuxIOv2Entry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table providing the means to access any non- mission-critical or non-safety-related auxiliary I/O of the controller, including reading inputs and setting outputs. The number of rows in this table equals the sum of the values of the 'maxAuxIOv2TableNumDigitalPorts' and 'maxAuxIOv2TableNumAnalogPorts' objects. This table shall not be used to control or monitor any safety related equipment. The electrical levels used by the ports are not standardized by auxIOv2Table objects; such information should be contained in the hardware manual. static FIELD-DEVICE-GPIO-MIB.fdGPIOTable & FIELD-DEVICE-GPIO- MIB.fdGPIOPortTable (ISO 20684-2) The GPIO objects provide a summary table for each port type. 1.3.6.1.4.1.1206.4.2.6.7.3" ::= { auxIOv2 3} auxIOv2Entry OBJECT-TYPE SYNTAX AuxIOv2Entry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "Parameters of the auxiliary I/O table. FIELD-DEVICE-GPIO-MIB.fdGPIOEntry & FIELD-DEVICE-GPIO- MIB.fdGPIOPortEntry (ISO 20684-2) The GPIO tables add columns for a count for each port type, a summary status of each type of port, an indication of the units reported by the port, an indication of the minimum and maximum values that can be reliably reported by the port, minimum and maximum threshold values that indicate when an alarm should be raised, and a status object that indicates any availability or alarm conditions. 1.3.6.1.4.1.1206.4.2.6.7.3.1" INDEX {auxIOv2PortType, auxIOv2PortNumber} ::={auxIOv2Table 1} AuxIOv2Entry ::= SEQUENCE { auxIOv2PortType INTEGER, auxIOv2PortNumber INTEGER, auxIOv2PortDescription DisplayString, auxIOv2PortResolution INTEGER, auxIOv2PortValue INTEGER, auxIOv2PortDirection INTEGER, auxIOv2PortLastCommandedState INTEGER } -- 6.3.3.1 Auxiliary Port Type Parameter auxIOv2PortType OBJECT-TYPE SYNTAX INTEGER{ other (1), analog (2), digital (3) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION "Indicates the type of auxiliary I/O, which can be analog or digital. FIELD-DEVICE-GPIO-MIB.fdGPIOType (ISO 20684-2) The GPIO tables classify ports using a three-letter code. ISO 20684-2 defines 23 port types and additional port types can be defined by registering with ISO. Example port types currently defined include humidity, light intensity, temperature, battery current, battery voltage, battery charge, generator fuel level, generator engine speed, fan status, etc. From NTCIP 1201 v01 to NTCIP v02 of these objects, it was determined that ports are either digital, analog, or other. 1.3.6.1.4.1.1206.4.2.6.7.3.1.1" ::= {auxIOv2Entry 1} -- 6.3.3.2 Auxiliary Port Number Parameter auxIOv2PortNumber OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port. FIELD-DEVICE-GPIO-MIB.fdGPIOPortNumber (ISO 20684-2) 1.3.6.1.4.1.1206.4.2.6.7.3.1.2" ::= {auxIOv2Entry 2} -- 6.3.3.3 Auxiliary Description Parameter auxIOv2PortDescription OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "Informational text field describing the device at the associated auxiliary I/O. FIELD-DEVICE-GPIO-MIB.fdGPIOPortDescription (ISO 20684-2) The GPIO object is an SnmpAdminString, which supports multi-lingual text. In NTCIP 1203 v01, the SYNTAX SIZE was listed as (0..50). In NTCIP 1201 v02 and NTCIP 1201 v03, this was changed to (0..255). 1.3.6.1.4.1.1206.4.2.6.7.3.1.3" ::= {auxIOv2Entry 3} -- 6.3.3.4 Auxiliary Resolution Parameter auxIOv2PortResolution OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "bits" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). Thus, this feature allows the digital monitoring (via NTCIP) of an analog port on the agent. In NTCIP 1203 v01, ACCESS was listed as read-write; however, in NTCIP 1201 v03, ACCESS changed to read-only . This changed because resolution is fixed by the hardware implementation and cannot be changed by the management station. The SYNTAX also changed from NTCIP 1201 v02 to NTCIP 1201 v03; it is now as it was originally under the experimental node defined in NTCIP 1203v01. This changed to address backward compatibility and the 'aliasing' between the version 1 objects (see Section 2.10) and the Version 02 objects. FIELD-DEVICE-GPIO-MIB.fdGPIOPortMinValue & FIELD-DEVICE-GPIO-MIB.fdGPIOPortMaxValue (ISO 20684-2) The GPIO table indicates the range over which values can be considered reliable. 1.3.6.1.4.1.1206.4.2.6.7.3.1.4" ::= {auxIOv2Entry 4} -- 6.3.3.5 Auxiliary Value Parameter auxIOv2PortValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION "For input or bidirectional ports, this contains the current value of the input. For output ports, this is the last commanded value of the port. A genError shall be generated, if this object is set and the port is an input. The actual value exchanged shall not exceed [2^(auxIOv2PortResolution): 1]; any SET operation to a value in excess of this number shall result in a genErr, and any GET response in excess of this value shall be considered erroneous. FIELD-DEVICE-GPIO-MIB.fdGPIOPortValue (ISO 20684-2) The original specification defined this parameter using INTEGER (0..4294967295); however, by convention, INTEGERs are limited to the range (-2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. The replacement object in the GPIO table supports a signed 32-bit integer, thereby allowing sensors to report negative values. 1.3.6.1.4.1.1206.4.2.6.7.3.1.5" ::= {auxIOv2Entry 5} -- 6.3.3.6 Auxiliary Port Direction Parameter auxIOv2PortDirection OBJECT-TYPE SYNTAX INTEGER { output (1), input (2), bidirectional (3)} MAX-ACCESS read-only STATUS deprecated DESCRIPTION "Indicates whether state of this port can be set (output), read (input) or both (bidirectional). FIELD-DEVICE-GPIO-MIB.fdGPIOPortDirection (ISO 20684-2) 1.3.6.1.4.1.1206.4.2.6.7.3.1.6" ::= {auxIOv2Entry 6} -- 6.3.3.7 Auxiliary Port Last Commanded State Parameter auxIOv2PortLastCommandedState OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS deprecated DESCRIPTION "For bi-directional ports, this object indicates the last state to which the auxIOv2PortValue object was set. For output ports, this value shall always be equal to the auxIOv2PortValue object. For input ports, this value shall always be zero (0). FIELD-DEVICE-GPIO-MIB.fdGPIORequestedValue (ISO 20684-2) The original specification defined this parameter Using INTEGER (0..4294967295); however, by convention, INTEGERs Are limited to the range (-2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this Object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. The replacement object in the GPIO table supports a signed 32- bit integer, thereby allowing negative output values. 1.3.6.1.4.1.1206.4.2.6.7.3.1.7" ::= {auxIOv2Entry 7} -- 6.4 COMPLIANCE GROUPS -- 6.4.1 Auxiliary I/O Version 2 Group auxIOv2GroupR1 OBJECT-GROUP OBJECTS { maxAuxIOv2TableNumDigitalPorts, maxAuxIOv2TableNumAnalogPorts, auxIOv2PortType, auxIOv2PortNumber, auxIOv2PortDescription, auxIOv2PortResolution, auxIOv2PortValue, auxIOv2PortDirection, auxIOv2PortLastCommandedState } STATUS deprecated DESCRIPTION " The objects necessary for managing the auxiliary IO ports according to the revised scheme under the global node. 1.3.6.1.4.1.1206.4.2.6.7.127.2.1" ::= {auxIOv2Groups 1} END --NTCIP1201-AuxIOv2 -- Section 7 -- 7.1 AUXILIARY I/O HEADER NTCIP1201-AuxIO DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32, Unsigned32 FROM SNMPv2-SMI -- RFC 2578 DisplayString FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP FROM SNMPv2-CONF expGlobal FROM NTCIP8004-NEMA; auxiliaryIO MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the AuxIO objects that were previously defined in NTCIP 1201 v03. This MIB contains the auxiliary input/output (I/O) objects originally defined in NTCIP 1203 v01 (a.k.a. NTCIP 1203:1997) under the experimental node. When the objects were moved to NTCIP 1201 v02, a slightly revised structure was developed under the global node and the original experimental objects were deprecated. This MIB is provided for backwards compatibility to support access to the experimental objects via an SNMPv3 proxy agent. In the context of implementation that supports these objects, there is no difference between what appeared in NTCIP 1203:1997 and what appears here. The auxiliary I/O management objects listed herein define a mechanism for the support of unspecified I/O for an NTCIP device. The agency or device specifications should define the intended operation of these ports. NOTE: These objects are still logically located under the nemaExperimental node and use their originally defined textual names and OIDs. For the purposes of backward compatibility, the object STATUS has been changed to deprecated. For those agents that may support these objects and the new objects under the global node (see Section 2.9), the object definitions shall be treated as aliases in that a write to an object in one group acts as write to the corresponding object in the other group. As aliases, a read of an object in one group also acts as read of the corresponding object in the other group. Early NTCIP deployments included the Aux I/O objects defined in NTCIP 1203 v01 located under an experimental node. These objects were moved to a permanent node with the release of NTCIP 1201 v02 and given new names. This can create confusion and backward compatibility issues. As noted in the object definition, both sets of objects refer to the same functions within the device; hence, both sets of objects cause the same device action or provide the same device status. Agency specifications which do NOT require support for the Aux I/O objects under the experimental node should exclude the support for these experimental objects (which have been deprecated) to ensure backward compatibility. Support of the Aux I/O objects under the permanent node identified in NTCIP 1201 v03 may be optional or mandatory depending on the agency- or project specification. Use the PRL to exclude support of NTCIP 1201 v01-defined aux I/O objects. The relationship between mandatory and optional support of NTCIP 1201 v01 (experimental) and NTCIP 1201 v02 objects is unique to the Aux I/O objects. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.2.2.1 Copyright (C) 2010, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 (all objects were previously deprecated)." REVISION "200610020000Z" DESCRIPTION "NTCIP 1201 v03 - Created this as a standalone MIB. Deprecated all objects. " ::= { expGlobal 1} -- 7.2 OBJECT IDENTITIES -- 7.2.1 AuxIO Configuration Node auxIOConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define conformance information for the auxIO MIB. 1.3.6.1.4.1.1206.4.2.2.1.127" ::= { auxiliaryIO 127 } auxIOCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define compliance statements for the auxIO MIB. 1.3.6.1.4.1.1206.4.2.2.1.127.1" ::= { auxIOConformance 1 } auxIOGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define object groups for the auxIO MIB. 1.3.6.1.4.1.1206.4.2.2.1.127.2" ::= { auxIOConformance 2 } -- 7.3 OBJECTS -- 7.3.1 Maximum Number of Digital Auxiliary I/Os Parameter maxAuxIODigital OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "digital ports" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The number of rows contained in the 'auxIOTable' with the auxIOPortType set to 'digital'. maxAuxIOv2TableNumDigitalPorts 1.3.6.1.4.1.1206.2.2.1.1 " ::= {auxiliaryIO 1} -- 7.3.2 Maximum Number of Analog Auxiliary I/Os Parameter maxAuxIOAnalog OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "analog ports" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows contained in the 'auxIOTable' with the auxIOPortType set to 'analog'. maxAuxIOv2TableNumAnalogPorts 1.3.6.1.4.1.1206.2.2.1.2 " ::= {auxiliaryIO 2} -- 7.3.3 Auxiliary I/O Table Parameter auxIOTable OBJECT-TYPE SYNTAX SEQUENCE OF AuxIOEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table providing the means to access the auxiliary I/O of the Controller, including reading inputs and setting outputs. A maximum of 255 auxiliary I/Os may be defined for all, digital, analog or other types of ports. static auxIOv2Table 1.3.6.1.4.1.1206.2.2.1.3 " ::= { auxiliaryIO 3} auxIOEntry OBJECT-TYPE SYNTAX AuxIOEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " Parameters of the auxiliary I/O table. auxIOv2Entry 1.3.6.1.4.1.1206.2.2.1.3.1 " INDEX {auxIOPortType, auxIOPortNumber} ::={auxIOTable 1} AuxIOEntry ::= SEQUENCE { auxIOPortType INTEGER, auxIOPortNumber INTEGER, auxIODescription DisplayString, auxIOResolution INTEGER, auxIOValue INTEGER, auxIOPortDirection INTEGER } -- 7.3.3.1 Auxiliary Port Type Parameter auxIOPortType OBJECT-TYPE SYNTAX INTEGER{ other (1), analog (2), digital (3) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Indicates the type of auxiliary I/O, which may be analog, digital or other. auxIOv2PortType 1.3.6.1.4.1.1206.2.2.1.3.1.1 " ::= {auxIOEntry 1} -- 7.3.3.2 Auxiliary Port Number Parameter auxIOPortNumber OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Indicates the port number for the associated port type. Port numbers are used sequentially from one to max for each port type. There can be a port 1 for analog port and port 1 for digital port. auxIOv2PortNumber 1.3.6.1.4.1.1206.2.2.1.3.1.2" ::= {auxIOEntry 2} -- 7.3.3.3 Auxiliary Description Parameter auxIODescription OBJECT-TYPE SYNTAX DisplayString (SIZE (0..50)) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " Informational text field describing the device at the associated auxiliary I/O In NTCIP 1203 v01, the SYNTAX SIZE was listed as (0..50). In all versions of NTCIP 1201 v02, auxIO2Description (this object's alias) was changed to (0..255). This does not present a backward compatibility issue if a NTCIP 1201 v02 management station limits the size of the DisplayString to 50 characters. auxIOv2PortDescription 1.3.6.1.4.1.1206.2.2.1.3.1.3 " ::= {auxIOEntry 3} -- 7.3.3.4 Auxiliary Resolution Parameter auxIOResolution OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "bits" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Defines number of bits used for the IO-port (e.g. width of digital, resolution of analog). In NTCIP 1203 v01, the ACCESS was listed as read- write. Resolution is fixed by the hardware implementation and cannot be changed by the management station. auxIOv2PortResolution 1.3.6.1.4.1.1206.2.2.1.3.1.4 " ::= {auxIOEntry 4} -- 7.3.3.5 Auxiliary Value Parameter auxIOValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION " For input or bidirectional ports, this contains the current value of the input. For output ports, this is the last commanded value of the port. A genError shall be generated, if this object is set and the port is an input. auxIOv2PortValue The original specification defined this parameter using INTEGER (0..4294967295); however, by convention, INTEGERs are limited to the range (-2147483648..2147483647) in SNMPv1 and SNMPv3 enforces this limitation. Therefore, when presenting this object in SNMPv3, it is encoded as an Unsigned32 rather than an INTEGER (0..4294967295); proxy agents will need to address this encoding change within their implementation. 1.3.6.1.4.1.1206.2.2.1.3.1.5 " ::= {auxIOEntry 5} -- 7.3.3.6 Auxiliary Port Direction Parameter auxIOPortDirection OBJECT-TYPE SYNTAX INTEGER { output (1), input (2), bidirectional (3)} MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Indicates whether state of this port can be set (output), read (input) or both (bidirectional). The ACCESS has been changed from what originally appeared in NTCIP 1203 v01 because it was an error. auxIOv2PortDirection 1.3.6.1.4.1.1206.2.2.1.3.1.6 " ::= {auxIOEntry 6} -- 7.4 COMPLIANCE GROUPS -- 7.4.1 Auxiliary I/O Group auxIOGroupR1 OBJECT-GROUP OBJECTS { maxAuxIODigital, maxAuxIOAnalog, auxIOPortType, auxIOPortNumber, auxIODescription, auxIOResolution, auxIOValue, auxIOPortDirection } STATUS deprecated DESCRIPTION " The objects necessary for managing the auxiliary IO ports according to the revised scheme under the global node. 1.3.6.1.4.1.1206.2.2.1.127.2.1" ::= {auxIOGroups 1} END -- NTCIP1201-AuxIO -- Section 8 -- 8.1 HEADER NTCIP1201-SNMPConfig DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Integer32 FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF application FROM NTCIP8004-Transportation; snmpConfig MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of snmpMaxPacketSize, which was previously defined in NTCIP 1103. This object is no longer needed with SNMPv3. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.1.7.1 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Changed name to snmpMaxPacketSize. Separated SNMP object into its own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version with object named snmp-maxPacketSize." ::= {application 1} -- 8.2 OBJECT IDENTITIES -- 8.2.1 SNMP Conformance Node snmpConfigConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define conformance information for the snmpConfig MIB. 1.3.6.1.4.1.1206.4.1.1.7.1.127" ::= { snmpConfig 127 } snmpConfigCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define compliance statements for the snmpConnfig MIB. 1.3.6.1.4.1.1206.4.1.1.7.1.127.1" ::= { snmpConfigConformance 1 } snmpConfigGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define object groups for the snmpConfig MIB. 1.3.6.1.4.1.1206.4.1.1.7.1.127.2" ::= { snmpConfigConformance 2 } -- 8.3 OBJECTS -- 8.3.1 Max Packet Size snmpMaxPacketSize OBJECT-TYPE SYNTAX Integer32 (484..65535) UNITS "octets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Indicates the maximum packet size, in octets, that the SNMP agent supports for reception or transmission. SNMP-FRAMEWORK-MIB.snmpEngineMaxMessageSize (RFC 3411) This object is no longer needed within SNMPv3 because the maximum packet size is contained in the HeaderData of each SNMPv3 data packet, as defined in RFC 3412. Nonetheless, RFC 3411 does define an object that can be retrieved to report the value that is applicable across all connections. 1.3.6.1.4.1.1206.4.1.1.7.1.1" ::= {snmpConfig 1} -- 8.4 COMPLIANCE GROUPS -- 8.4.1 SNMP Configuration Group snmpConfigGroupR1 OBJECT-GROUP OBJECTS { snmpMaxPacketSize } STATUS deprecated DESCRIPTION " The objects necessary for managing the SNMP configuration. 1.3.6.1.4.1.1206.4.1.1.7.1.127.2.1" ::= {snmpConfigGroups 1} END --NTCIP1201-SNMPConfig -- Section 9 -- 9.1 HEADER NTCIP1201-SFMP DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Counter32 FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF application FROM NTCIP8004-Transportation; sfmp MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-SFMP MIB, which is defined in NTCIP 1103. It defines objects related to managing and monitoring the communication statistics for the Simple Fixed Message Protocol. (SFMP). *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.1.7.2 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Updated text to conform to current conventions; separated SFMP objects into their own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version of objects." ::= {application 2} -- 9.2 OBJECT IDENTITIES -- 9.2.1 SFMP Statistics sfmpStatistics OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node contains communication statistics for the Simple Fixed Message Protocol (SFMP). 1.3.6.1.4.1.1206.4.1.1.7.2.1" ::= { sfmp 1 } -- 9.2.2 SFMP Conformance Node sfmpConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define conformance clauses for SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.127" ::= { sfmp 127 } sfmpCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define compliance statements for the SFMP MIB. 1.3.6.1.4.1.1206.4.1.1.7.2.127.1" ::= { sfmpConformance 1 } sfmpGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define object groups for the SFMP MIB. 1.3.6.1.4.1.1206.4.1.1.7.2.127.2" ::= { sfmpConformance 2 } -- 9.3 OBJECTS -- 9.3.1 Number of Incoming SFMP Packets sfmpInPkts OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of Messages delivered to the SFMP entity for processing. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.1" ::= { sfmpStatistics 1 } -- 9.3.2 Number of Outgoing SFMP Packets sfmpOutPkts OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDU's which were generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.2" ::= { sfmpStatistics 2 } -- 9.3.3 Number of Incoming SFMP Packets with Bad Version Numbers sfmpInBadVersions OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Messages which were delivered to the SFMP protocol entity and were for an unsupported SFMP version. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.3" ::= { sfmpStatistics 3 } -- 9.3.4 Number of Incoming SFMP Packets with Bad Community Names sfmpInBadCommunityNames OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Messages delivered to the SFMP protocol entity which used a SFMP community name not known to said entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.4" ::= { sfmpStatistics 4 } -- 9.3.5 Number of Incoming SFMP Packets with Bad Use of a Community Name sfmpInBadCommunityUses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Messages delivered to the SFMP protocol entity which represented an SFMP operation which was not allowed by the SFMP community named in the Message. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.5" ::= { sfmpStatistics 5 } -- 9.3.6 Number of Incoming SFMP Packets with Parsing Errors sfmpInParseErrs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of OER errors encountered by the SFMP protocol entity when decoding received SFMP Messages. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.6" ::= { sfmpStatistics 6 } -- 9.3.7 Reserved -- node 7 is reserved for bad types to parallel SNMP, but it does not -- apply to SFMP -- 9.3.8 Number of Incoming SFMP Packets indicating a Too Big Error sfmpInTooBigs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were delivered to the SFMP protocol entity with a Message Type of Error and Error Number of tooBig. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.8" ::= { sfmpStatistics 8 } -- 9.3.9 Number of Incoming SFMP Packets indicating a No Such Name Error sfmpInNoSuchNames OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were delivered to the SFMP protocol entity with a Message Type of Error and Error Number of noSuchName. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.9" ::= { sfmpStatistics 9 } -- 9.3.10 Number of Incoming SFMP Packets indicating a Bad Value Error sfmpInBadValues OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were delivered to the SFMP protocol entity with a Message Type of Error and Error Number of badValue. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.10" ::= { sfmpStatistics 10 } -- 9.3.11 Number of Incoming SFMP Packets indicating a Read-Only Error sfmpInReadOnlys OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were delivered to the SFMP protocol entity with a Message Type of Error and Error Number of readOnly. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.11" ::= { sfmpStatistics 11 } -- 9.3.12 Number of Incoming SFMP Packets indicating a General Error sfmpInGenErrs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were delivered to the SFMP protocol entity with a Message Type of Error and Error Number of genError. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.12" ::= { sfmpStatistics 12 } -- 9.3.13 Reserved -- node 13 is reserved for total request vars to -- parallel SNMP, but it does not apply to SFMP -- 9.3.14 Reserved -- node 14 is reserved for total set vars to parallel -- SNMP, but it does not apply to SFMP -- 9.3.15 Number of Incoming SFMP Get Requests sfmpInGetRequests OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Get-Request PDUs which have been accepted and processed by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.15" ::= { sfmpStatistics 15 } -- 9.3.16 Reserved -- node 16 is reserved for in get nexts to parallel -- SNMP, but it does not apply to SFMP -- 9.3.17 Number of Incoming SFMP Set Requests sfmpInSetRequests OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Set-Request PDUs which have been accepted and processed by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.17" ::= { sfmpStatistics 17 } -- 9.3.18 Number of Incoming SFMP Get Responses sfmpInGetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Get-Response PDUs which have been accepted and processed by the SFMP protocol entity. 1.3.6.1.4.1.1206.4.1.1.7.2.1.18" ::= { sfmpStatistics 18 } -- 9.3.19 Reserved -- node 19 is reserved for traps to parallel SNMP, but it -- does not apply to SFMP at present -- 9.3.20 Number of Outgoing SFMP Packets indicating a Too Big Error sfmpOutTooBigs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were generated by the SFMP protocol entity with a Message Type of Error and Error Number of tooBig. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.20" ::= { sfmpStatistics 20 } -- 9.3.21 Number of Outgoing SFMP Packets indicating a No Such Name Error sfmpOutNoSuchNames OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were generated by the SFMP protocol entity with a Message Type of Error and Error Number of noSuchname. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.21" ::= { sfmpStatistics 21 } -- 9.3.22 Number of Outgoing SFMP Packets indicating a Bad Value Error sfmpOutBadValues OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were generated by the SFMP protocol entity with a Message Type of Error and Error Number of badValue. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.22" ::= { sfmpStatistics 22 } -- 9.3.23 Number of Outgoing SFMP Packets indicating a Read-Only Error sfmpOutReadOnly OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were generated by the SFMP protocol entity with a Message Type of Error and Error Number of readOnly. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.23" ::= { sfmpStatistics 23 } -- 9.3.24 Number of Outgoing SFMP Packets indicating a General Error sfmpOutGenError OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs which were generated by the SFMP protocol entity with a Message Type of Error and Error Number of genErr. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.24" ::= { sfmpStatistics 24 } -- 9.3.25 Number of Outgoing SFMP Get Requests sfmpOutGetRequests OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDU's with a Message Type of Get-Request, which have been generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.25" ::= { sfmpStatistics 25 } -- 9.3.26 Reserved -- node 26 is reserved for out get nexts to parallel SNMP, -- but it does not apply to SFMP -- 9.3.27 Number of Outgoing SFMP Set Requests sfmpOutSetRequests OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDU's with a Message Type of Set-Request, which have been generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.27" ::= { sfmpStatistics 27 } -- 9.3.28 Number of Outgoing SFMP Get Responses sfmpOutGetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDU's with a Message Type of Get-Response, which have been generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.28" ::= { sfmpStatistics 28 } -- 9.3.29 Number of Outgoing SFMP Trap Messages sfmpOutTrapMessages OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDUs with a message type of Trap that have been generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.29" ::= { sfmpStatistics 29 } -- 9.3.30 Reserved -- node 30 is reserved for enable authentication traps to parallel -- SNMP, but it does not apply to SFMP -- 9.3.31 Number of Incoming SFMP Set Requests: No Replies sfmpInSetRequestsNoReply OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Set-Request No Reply PDUs which have been accepted and processed by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.31" ::= { sfmpStatistics 31 } -- 9.3.32 Number of Incoming SFMP Set Responses sfmpInSetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Set-Response PDUs which have been accepted and processed by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.32" ::= { sfmpStatistics 32 } -- 9.3.33 Number of Incoming SFMP Error Responses sfmpInErrorResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP Error-Response PDUs which have been accepted and processed by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.33" ::= { sfmpStatistics 33 } -- 9.3.34 Number of Outgoing SFMP Set Requests: No Replies sfmpOutSetRequestsNoReply OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDU's with a Message Type of Set-Request-No-Reply, which have been generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.34" ::= { sfmpStatistics 34 } -- 9.3.35 Number of Outgoing SFMP Set Responses sfmpOutSetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDU's with a Message Type of Set-Response, which have been generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.35" ::= { sfmpStatistics 35 } -- 9.3.36 Number of Outgoing SFMP Error Responses sfmpOutErrorResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of SFMP PDU's with a Message Type of Error-Response, which have been generated by the SFMP protocol entity. This object has been deprecated along with SFMP. 1.3.6.1.4.1.1206.4.1.1.7.2.1.36" ::= { sfmpStatistics 36 } -- 9.4 COMPLIANCE GROUPS -- 9.4.1 SFMP Group sfmpGroupR1 OBJECT-GROUP OBJECTS { sfmpInPkts, sfmpOutPkts, sfmpInBadVersions, sfmpInBadCommunityNames, sfmpInBadCommunityUses, sfmpInParseErrs, sfmpInTooBigs, sfmpInNoSuchNames, sfmpInBadValues, sfmpInReadOnlys, sfmpInGenErrs, sfmpInGetRequests, sfmpInSetRequests, sfmpInGetResponses, sfmpOutTooBigs, sfmpOutNoSuchNames, sfmpOutBadValues, sfmpOutReadOnly, sfmpOutGenError, sfmpOutGetRequests, sfmpOutSetRequests, sfmpOutGetResponses, sfmpOutTrapMessages, sfmpInSetRequestsNoReply, sfmpInSetResponses, sfmpInErrorResponses, sfmpOutSetRequestsNoReply, sfmpOutSetResponses, sfmpOutErrorResponses } STATUS deprecated DESCRIPTION " The objects necessary for monitoring SFMP statistics. 1.3.6.1.4.1.1206.4.1.1.7.2.127.2.1" ::= {sfmpGroups 1} END -- NTCIP1201-SFMP -- Section 10 -- 10.1 HEADER NTCIP1201-DynObjMgmt DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Integer32, zeroDotZero FROM SNMPv2-SMI -- RFC 2578 TEXTUAL-CONVENTION FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 protocols, NtcipOwnerString FROM NTCIP8004-Transportation; dynObjMgmt MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-STMP MIB, which was previously defined in NTCIP 1103. This node contains management information related to dynamic objects. This node was deprecated in 2021 as a part of the NTCIP 8004v03 update because dynamic objects are a specific feature of the Simple Transportation Management Protocol (STMP), which was itself deprecated because it was deemed to provide insufficient security for modern networks. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.3 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 -." REVISION "199609270000Z" DESCRIPTION "NTCIP 1101 v01: Original version of these objects." ::= {protocols 3} -- 10.2 TEXTUAL CONVENTIONS ConfigEntryStatus ::= TEXTUAL-CONVENTION STATUS deprecated DESCRIPTION "See Clause 5.2.4.1 of NTCIP 1103 v03 for the complete definition of this type." SYNTAX INTEGER { valid (1), underCreation (2), invalid (3) } EntryStatus ::= TEXTUAL-CONVENTION STATUS deprecated DESCRIPTION "See Annex E of NTCIP 1103 v03 for a complete definition of this Type." SYNTAX INTEGER { valid (1), createRequest (2), underCreation (3), invalid (4) } -- 10.3 OBJECT IDENTITIES -- 10.3.1 Data Node dynObjData OBJECT-IDENTITY STATUS current DESCRIPTION " A node containing SNMP object definitions of the dynamic objects. 1.3.6.1.4.1.1206.4.1.3.2" ::= { dynObjMgmt 2 } -- 10.3.2 Dynamic Object Management Conformance Node dynObjMgmtConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define conformance clauses for dynamic object management. 1.3.6.1.4.1.1206.4.1.3.127" ::= { dynObjMgmt 127 } dynObjMgmtCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define compliance statements for ynamic object management. 1.3.6.1.4.1.1206.4.1.3.127.1" ::= { dynObjMgmtConformance 1 } dynObjMgmtGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define object groups for dynamic object management. 1.3.6.1.4.1.1206.4.1.3.127.2" ::= { dynObjMgmtConformance 2 } -- 10.4 DYNAMIC OBJECT DEFINITION -- 10.4.1 Maximum Dynamic Object Table Entries dynObjDefTableMaxEntries OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "entries" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object specifies the maximum number of rows that may be implemented in the Dynamic Object Definition table. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.4" ::= { dynObjMgmt 4 } -- 10.4.2 Dynamic Object Definition Table dynObjDef OBJECT-TYPE SYNTAX SEQUENCE OF DynObjEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A list of objects to be included in dynamic objects static This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.1" ::= { dynObjMgmt 1 } dynObjEntry OBJECT-TYPE SYNTAX DynObjEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A list of OBJECT IDENTIFIERs that make up a dynamic object This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.1.1" INDEX { dynObjNumber, dynObjIndex } ::= { dynObjDef 1 } DynObjEntry ::= SEQUENCE { dynObjNumber Integer32, dynObjIndex Integer32, dynObjVariable OBJECT IDENTIFIER, dynObjOwner NtcipOwnerString, -- previously deprecated dynObjStatus EntryStatus } -- previously deprecated -- 10.4.2.1 Dynamic Object Number dynObjNumber OBJECT-TYPE SYNTAX Integer32 ( 1..13) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The dynamic object number that this entry is to be associated with. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.1.1.1" ::= { dynObjEntry 1 } -- 10.4.2.2 Dynamic Object Index dynObjIndex OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " An index that uniquely identifies an entry in the dynamic object table. Each entry defines an object that is to be associated with a dynamic object number. The dynObjIndex determines the order in which objects are transmitted for the associated dynamic object. The lower dynObjIndex numbers are transmitted before larger numbers for entries within the same dynamic object. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.1.1.2" ::= { dynObjEntry 2 } -- 10.4.2.3 Dynamic Object Variable dynObjVariable OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The complete object identifier of the particular variable to be included in the specified dynamic object number. When defining dynamic objects, the maximum size of all the objects included in a dynamic object shall not exceed the maximum packet size of the communications network. When set to reference a columnar object, an agent may wish to only validate the prefix portion of the object identifier. The suffix or index portion of an object identifier need not be instantiated or exist at the time a dynObjVariable is defined. This object shall not reference any of the objects identified in NTCIP 1103 Clause 8.2. This object may not be modified unless the associated dynObjConfigStatus object is equal to underCreation. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.1.1.3" DEFVAL { zeroDotZero } ::= { dynObjEntry 3 } -- 10.4.2.4 Dynamic Object Owner dynObjOwner OBJECT-TYPE SYNTAX NtcipOwnerString MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object has been replaced with dynObjConfigOwner. The entity that configured this entry and is therefore using the resources assigned to it. This object may not be modified if the associated dynObjStatus object is equal to valid(1). This object was deprecated in NTCIP 1103 v02. 1.3.6.1.4.1.1206.4.1.3.1.1.4" ::= { dynObjEntry 4 } -- 10.4.2.5 Dynamic Object Status dynObjStatus OBJECT-TYPE SYNTAX EntryStatus MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object has been replaced with dynObjConfigStatus. The status of this dynamic object definition entry. See description of EntryStatus above for restrictions on accesses. This object was deprecated in NTCIP 1103 v02. 1.3.6.1.4.1.1206.4.1.3.1.1.5" ::= { dynObjEntry 5 } -- 10.5 DYNAMIC OBJECT DATA dynObj1 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 1. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.1" ::= { dynObjData 1 } dynObj2 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 2. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.2" ::= { dynObjData 2 } dynObj3 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 3. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.3" ::= { dynObjData 3 } dynObj4 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 4. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.4" ::= { dynObjData 4 } dynObj5 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 5. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.5" ::= { dynObjData 5 } dynObj6 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 6. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.6" ::= { dynObjData 6 } dynObj7 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 7. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.7" ::= { dynObjData 7 } dynObj8 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 8. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.8" ::= { dynObjData 8 } dynObj9 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 9. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.9" ::= { dynObjData 9 } dynObj10 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 10. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.10" ::= { dynObjData 10 } dynObj11 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 11. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.11" ::= { dynObjData 11 } dynObj12 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 12. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.12" ::= { dynObjData 12 } dynObj13 OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The value of this object is determined by the dynObjDef entries with dynObjNumber equal to 13. Packed Encoding Rules are utilized to encode the objects for transmission. This object is intended for use with the Simple Transportation Management Protocol, and provides little advantage if used with SNMP. If no objects are defined for this dynamic object number, then an error of noSuchName shall be returned by the agent This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.2.13" ::= { dynObjData 13 } -- 10.5.1 Dynamic Object Configuration dynObjConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF DynObjConfigEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table consisting of an owner and status for each of the 13 dynamic object definitions. static This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.3" ::= { dynObjMgmt 3} dynObjConfigEntry OBJECT-TYPE SYNTAX DynObjConfigEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table consisting of an owner and status for each of the 13 dynamic object definitions. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.3.1" INDEX {dynObjNumber} ::= {dynObjConfigTable 1} DynObjConfigEntry ::= SEQUENCE { dynObjConfigOwner NtcipOwnerString, dynObjConfigStatus ConfigEntryStatus } -- 10.5.1.1 Dynamic Object Configuration Owner dynObjConfigOwner OBJECT-TYPE SYNTAX NtcipOwnerString MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The entity that configured the associated dynamic object. This object may not be modified unless the associated dynObjConfigStatus object is equal to underCreation. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.3.1.1" DEFVAL {""} ::= {dynObjConfigEntry 1} -- 10.5.1.2 Dynamic Object Configuration Status dynObjConfigStatus OBJECT-TYPE SYNTAX ConfigEntryStatus MAX-ACCESS read-write STATUS deprecated DESCRIPTION " Indicates the state of the associated dynamic object. Depending on the validity checks that are performed on the dynamic object definition, a set request may or may not be honored. See Clause 5.2.4.1 for a complete description. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.3.3.1.2" ::= {dynObjConfigEntry 2} -- 10.6 COMPLIANCE GROUPS -- 10.6.1 Dynamic Object Definition Group dynObjMgmtGroupR1 OBJECT-GROUP OBJECTS { dynObjNumber, dynObjIndex, dynObjVariable, dynObjOwner, dynObjStatus } STATUS deprecated DESCRIPTION " The objects necessary for defining dynamic objects according to the original standard. 1.3.6.1.4.1.1206.4.1.3.127.2.1" ::= {dynObjMgmtGroups 1} -- 10.6.2 Dynamic Object Definition Group 2 dynObjMgmtGroupR2 OBJECT-GROUP OBJECTS { dynObjNumber, dynObjIndex, dynObjVariable, dynObjConfigOwner, dynObjConfigStatus } STATUS deprecated DESCRIPTION " The objects necessary for defining dynamic object based on the revised standard that incorporated field experience. 1.3.6.1.4.1.1206.4.1.3.127.2.2" ::= {dynObjMgmtGroups 2} -- 10.6.3 Dynamic Object Definition Group 2 Extension dynObjMgmtGroupR2Ext OBJECT-GROUP OBJECTS { dynObjDefTableMaxEntries } STATUS deprecated DESCRIPTION " The object for determining the feature support within the dynamic object table. 1.3.6.1.4.1.1206.4.1.3.127.2.3" ::= {dynObjMgmtGroups 3} -- 10.6.4 Dynamic Object Data Group dynObjDataGroupR1 OBJECT-GROUP OBJECTS { dynObj1, dynObj2, dynObj3, dynObj4, dynObj5, dynObj6, dynObj7, dynObj8, dynObj9, dynObj10, dynObj11, dynObj12, dynObj13 } STATUS deprecated DESCRIPTION " The objects necessary for monitoring dynamic objects as SNMP objects. 1.3.6.1.4.1.1206.4.1.3.127.2.4" ::= {dynObjMgmtGroups 4} END -- NTCIP1201-DynObjMgmt -- Section 11 -- 11.1 HEADER NTCIP1201-STMP DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Counter32, zeroDotZero FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF application FROM NTCIP8004-Transportation; stmp MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-STMP-Stats MIB, which was defined in NTCIP 1103. This MIB defines objects related to communication statistics for the Simple Transportation Management Protocol (STMP). This MIB was deprecated in NTCIP 1201 v04 because the Simple Transportation Management Protocol (STMP) was deprecated because it was deemed to provide insufficient security for modern networks. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.1.7.3 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Changed name to snmpMaxPacketSize. Separated SNMP object into its own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version with object named snmp-maxPacketSize." ::= {application 3} -- 11.2 OBJECT IDENTITIES -- 11.2.1 STMP Statistics Node stmpStatistics OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node contains communication statistics for the Simple Transportation Management Protocol (STMP). 1.3.6.1.4.1.1206.4.1.1.7.3.1" ::= { stmp 1 } -- 11.2.2 STMP Statistics Conformance Node stmpStatsConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define conformance clauses for STMP . 1.3.6.1.4.1.1206.4.1.1.7.3.127" ::= { stmpStatistics 127 } stmpStatsCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define compliance statements for STMP. 1.3.6.1.4.1.1206.4.1.1.7.3.127.1" ::= { stmpStatsConformance 1 } stmpStatsGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to define groups for STMP. 1.3.6.1.4.1.1206.4.1.1.7.3.127.2" ::= { stmpStatsConformance 2 } -- 11.3 OBJECTS -- 11.3.1 Number of Incoming STMP Packets stmpInPkts OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of Messages delivered to the STMP entity for processing. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.1" ::= { stmpStatistics 1 } -- 11.3.2 Number of Outgoing STMP Packets stmpOutPkts OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's which were generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.2" ::= { stmpStatistics 2 } -- 11.3.3 Reserved -- node 3 is reserved for bad version to parallel SNMP, -- but it does not apply to STMP -- 11.3.4 Reserved -- node 4 is reserved for bad community name to parallel -- SNMP, but it does not apply to STMP -- 11.3.5 Reserved -- node 5 is reserved for bad community use to parallel -- SNMP, but it does not apply to STMP -- 11.3.6 Number of Incoming STMP Packets with Parsing Errors stmpInParseErrs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of OER errors encountered by the STMP protocol entity when decoding received STMP Messages. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.6" ::= { stmpStatistics 6 } -- 11.3.7 Reserved -- node 7 is reserved for bad types to parallel SNMP, but -- it does not apply to STMP -- 11.3.8 Number of Incoming STMP Packets indicating a Too Big Error stmpInTooBigs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were delivered to the STMP protocol entity with a Message Type of Error and Error Number of tooBig. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.8" ::= { stmpStatistics 8 } -- 11.3.9 Number of Incoming STMP Packets indicating a No Such Name Error stmpInNoSuchNames OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were delivered to the STMP protocol entity with a Message Type of Error and Error Number of noSuchName. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.9" ::= { stmpStatistics 9 } -- 11.3.10 Number of Incoming STMP Packets indicating a Bad Value Error stmpInBadValues OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were delivered to the STMP protocol entity with a Message Type of Error and Error Number of badValue. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.10" ::= { stmpStatistics 10 } -- 11.3.11 Number of Incoming STMP Packets indicating a Read-Only Error stmpInReadOnlys OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were delivered to the STMP protocol entity with a Message Type of Error and Error Number of readOnly. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.11" ::= { stmpStatistics 11 } -- 11.3.12 Number of Incoming STMP Packets indicating a General Error stmpInGenErrs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were delivered to the STMP protocol entity with a Message Type of Error and Error Number of genError. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.12" ::= { stmpStatistics 12 } -- 11.3.13 Reserved -- node 13 is reserved for total request vars to parallel -- SNMP, but it does not apply to STMP -- 11.3.14 Reserved -- node 14 is reserved for total set vars to parallel SNMP, -- but it does not apply to STMP -- 11.3.15 Number of Incoming STMP Get Requests stmpInGetRequests OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP Get-Request PDUs which have been accepted and processed by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.15" ::= { stmpStatistics 15 } -- 11.3.16 Number of Incoming STMP Get Next Requests stmpInGetNexts OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP Get-Next PDUs which have been accepted and processed by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.16" ::= { stmpStatistics 16 } -- 11.3.17 Number of Incoming STMP Set Requests stmpInSetRequests OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP Set-Request PDUs which have been accepted and processed by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.17" ::= { stmpStatistics 17 } -- 11.3.18 Number of Incoming STMP Get Responses stmpInGetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP Get-Response PDUs which have been accepted and processed by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.18" ::= { stmpStatistics 18 } -- 11.3.19 Reserved -- node 19 is reserved for in trap responses to parallel -- SNMP, but it does not apply to STMP -- 11.3.20 Number of Outgoing STMP Packets indicating a Too Big Error stmpOutTooBigs OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were generated by the STMP protocol entity with a Message Type of Error and Error Number of tooBig. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.20" ::= { stmpStatistics 20 } -- 11.3.21 Number of Outgoing STMP Packets indicating a No Such Name Error stmpOutNoSuchNames OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were generated by the STMP protocol entity with a Message Type of Error and Error Number of noSuchName. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.21" ::= { stmpStatistics 21 } -- 11.3.22 Number of Outgoing STMP Packets indicating a Bad Value Error stmpOutBadValues OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were generated by the STMP protocol entity with a Message Type of Error and Error Number of badValue. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.22" ::= { stmpStatistics 22 } -- 11.3.23 Number of Outgoing STMP Packets indicating a Read-Only Error stmpOutReadOnly OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were generated by the STMP protocol entity with a Message Type of Error and Error Number of readOnly. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.23" ::= { stmpStatistics 23 } -- 11.3.24 Number of Outgoing STMP Packets indicating a General Error stmpOutGenError OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDUs which were generated by the STMP protocol entity with a Message Type of Error and Error Number of genErr. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.24" ::= { stmpStatistics 24 } -- 11.3.25 Number of Outgoing STMP Get Requests stmpOutGetRequests OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's with a Message Type of Get-Request, which have been generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.25" ::= { stmpStatistics 25 } -- 11.3.26 Number of Outgoing STMP Get Next Requests stmpOutGetNexts OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's with a Message Type of Get-Next, which have been generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.26" ::= { stmpStatistics 26 } -- 11.3.27 Number of Outgoing STMP Set Requests stmpOutSetRequests OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's with a Message Type of Set-Request, which have been generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.27" ::= { stmpStatistics 27 } -- 11.3.28 Number of Outgoing STMP Get Responses stmpOutGetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's with a Message Type of Get-Response, which have been generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.28" ::= { stmpStatistics 28 } -- 11.3.29 Reserved -- node 29 is reserved for in trap responses to parallel -- SNMP, but it does not apply to STMP -- 11.3.30 Reserved -- node 30 is reserved for enable authentication traps to parallel -- SNMP, but it does not apply to STMP -- 11.3.31 Number of Incoming STMP Set Request: No Replies stmpInSetRequestsNoReply OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP Set-Request No Reply PDUs which have been accepted and processed by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.31" ::= { stmpStatistics 31 } -- 11.3.32 Number of Incoming STMP Set Responses stmpInSetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP Set-Response PDUs which have been accepted and processed by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.32" ::= { stmpStatistics 32 } -- 11.3.33 Number of Incoming STMP Error Responses stmpInErrorResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP Error-Response PDUs which have been accepted and processed by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.33" ::= { stmpStatistics 33 } -- 11.3.34 Number of Outgoing STMP Set Request: No Replies stmpOutSetRequestsNoReply OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's with a Message Type of Set-Request-No-Reply, which have been generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.34" ::= { stmpStatistics 34 } -- 11.3.35 Number of Outgoing STMP Set Responses stmpOutSetResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's with a Message Type of Set-Response, which have been generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.35" ::= { stmpStatistics 35 } -- 11.3.36 Number of Outgoing STMP Error Responses stmpOutErrorResponses OBJECT-TYPE SYNTAX Counter32 UNITS "packets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The total number of STMP PDU's with a Message Type of Error-Response, which have been generated by the STMP protocol entity. This object has been deprecated along with STMP. This object was originally defined with a syntax of Counter. This MIB updates the syntax to Counter32 to conform to SMIv2 conventions. There is no difference between the Counter and Counter32 syntaxes. Users should note, however, that neither a Counter nor a Counter32 is Required to initialize at or reset to zero (0). 1.3.6.1.4.1.1206.4.1.1.7.3.1.36" ::= { stmpStatistics 36 } -- 11.4 COMPLIANCE GROUPS -- 11.4.1 Dynamic Object Definition Group stmpStatisticsGroupR1 OBJECT-GROUP OBJECTS { stmpInPkts, stmpOutPkts, stmpInParseErrs, stmpInTooBigs, stmpInNoSuchNames, stmpInBadValues, stmpInReadOnlys, stmpInGenErrs, stmpInGetRequests, stmpInGetNexts, stmpInSetRequests, stmpInGetResponses, stmpOutTooBigs, stmpOutNoSuchNames, stmpOutBadValues, stmpOutReadOnly, stmpOutGenError, stmpOutGetRequests, stmpOutGetNexts, stmpOutSetRequests, stmpOutGetResponses, stmpInSetRequestsNoReply, stmpInSetResponses, stmpInErrorResponses, stmpOutSetRequestsNoReply, stmpOutSetResponses, stmpOutErrorResponses } STATUS deprecated DESCRIPTION " The objects necessary for monitoring STMP statistics. 1.3.6.1.4.1.1206.4.1.1.7.3.127.2.1" ::= {stmpStatsGroups 1} END -- NTCIP1201-STMPStatistics -- Section 12 -- 12.1 HEADER NTCIP1201-ProfilesSTMP DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Integer32 FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF profiles FROM NTCIP8004-Transportation; profilesSTMP MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-STMP-Config MIB, which was defined in NTCIP 1103. This MIB defines objects related to the configuration of the Simple Transportation Management Protocol (STMP). This MIB was deprecated in NTCIP 1201 v04 because the Simple Transportation Management Protocol (STMP) was deprecated because it was deemed to provide insufficient security for modern networks. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.2.2 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Changed name to snmpMaxPacketSize. Separated SNMP object into its own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version with object named snmp-maxPacketSize." ::= { profiles 2 } -- 12.2 OBJECT IDENTITIES -- 12.2.1 Profile STMP Conformance Node profilesSTMPConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the STMP profile. 1.3.6.1.4.1.1206.4.1.2.2.127" ::= { profilesSTMP 127 } profilesSTMPCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the STMP profile. 1.3.6.1.4.1.1206.4.1.2.2.127.1" ::= { profilesSTMPConformance 1 } profilesSTMPGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the STMP profile. 1.3.6.1.4.1.1206.4.1.2.2.127.2" ::= { profilesSTMPConformance 2 } -- 12.3 OBJECTS -- 12.3.1 Dynamic Object Persistence dynamicObjectPersistence OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "minutes" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The maximum power outage time in minutes that may occur before all STMP dynamic object definitions in a device shall be invalidated. If this object is set to zero then the existing dynamic object definitions shall be invalidated on device power up. If this object is set to its maximum value (65535), then the existing dynamic object definitions shall nominally persist for an infinite period (in practice this is limited by the non-volatile memory capabilities of the device). This object shall not be invalidated due to power outages of any duration. A device that supports STMP dynamic objects shall support this object. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.2.2.1" DEFVAL {65535} ::= { profilesSTMP 1 } -- 12.3.2 Dynamic Object Configuration ID dynamicObjectTableConfigID OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Specifies a relatively unique ID (e.g., this could be a counter, a check-sum, etc.) for the current values stored in the dynObjVariable and dynObjConfigOwner objects for all dynamic objects with a dynObjStatus of valid. This value shall be calculated on the change of any dynObjStatus to or from the valid state. This value reported by this object shall not change unless there has been a change in the data since the last request; however a genErr shall be returned if the unique ID value has not yet been updated. A management station will be able to detect any change in the configuration of dynamic objects by monitoring this value after it has established a baseline. This object has been deprecated along with STMP. 1.3.6.1.4.1.1206.4.1.2.2.2" ::= { profilesSTMP 2 } -- 12.4 COMPLIANCE GROUPS -- 12.4.1 Dynamic Object Definition Group profilesSTMPGroup OBJECT-GROUP OBJECTS { dynamicObjectPersistence, dynamicObjectTableConfigID } STATUS deprecated DESCRIPTION " The objects necessary for managing the STMP profile. 1.3.6.1.4.1.1206.4.1.2.2.127.2.1" ::= {profilesSTMPGroups 1} END -- NTCIP1201-ProfilesSTMP -- Section 13 -- 13.1 HEADER NTCIP1201-LogicalNames DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Integer32, IpAddress FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF application, NtcipRowStatusStatic FROM NTCIP8004-Transportation; logicalNames MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-LogicalNames MIB, which was defined in NTCIP 1103. This MIB defines various objects related to the mapping of logical device names to network addresses. This MIB was deprecated in NTCIP 1201 v04 because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.1.7.4 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Separated into its own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version." ::= { application 4 } -- 13.2 OBJECT IDENTITIES -- 13.2.1 Logical Names Conformance Node logicalNamesConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage logical names. 1.3.6.1.4.1.1206.4.1.1.7.4.127" ::= { logicalNames 127 } logicalNamesCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage logical names. 1.3.6.1.4.1.1206.4.1.1.7.4.127.1" ::= { logicalNamesConformance 1 } logicalNamesGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage logical names. 1.3.6.1.4.1.1206.4.1.1.7.4.127.2" ::= { logicalNamesConformance 2 } -- 13.3 OBJECTS -- 13.3.1 Maximum Logical Name Translations logicalNameTranslationTableMaxEntries OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "entries" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object specifies the maximum number of rows that may be implemented in the logical name translation table. This object was deprecated because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. 1.3.6.1.4.1.1206.4.1.1.7.4.1" ::= { logicalNames 1 } -- 13.3.2 Logical Name Translation Table logicalNameTranslationTable OBJECT-TYPE SYNTAX SEQUENCE OF LogicalNameTranslationEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " This table defines the logical names of the other network entities with which the device may communicate and maps these names to the network addresses of those devices. static This object was deprecated because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. 1.3.6.1.4.1.1206.4.1.1.7.4.2" ::= { logicalNames 2 } logicalNameTranslationEntry OBJECT-TYPE SYNTAX LogicalNameTranslationEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " This is one logical row of the logical name translation table. This object was deprecated because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. 1.3.6.1.4.1.1206.4.1.1.7.4.2.1" INDEX { logicalNameTranslationIndex } ::= { logicalNameTranslationTable 1} LogicalNameTranslationEntry::=SEQUENCE { logicalNameTranslationIndex Integer32, logicalNameTranslationLogicalName OCTET STRING, logicalNameTranslationNetworkAddress IpAddress, logicalNameTranslationStatus NtcipRowStatusStatic } -- 13.3.2.1 Index for the Logical Name Translation logicalNameTranslationIndex OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object provides the index into the logical name table. This object was deprecated because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. 1.3.6.1.4.1.1206.4.1.1.7.4.2.1.1" ::= { logicalNameTranslationEntry 1 } -- 13.3.2.2 Logical Name for the Logical Name Translation logicalNameTranslationLogicalName OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..32)) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object defines the logical name of the network entity for which this row is defined. This object was deprecated because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. 1.3.6.1.4.1.1206.4.1.1.7.4.2.1.2" DEFVAL { "" } ::= { logicalNameTranslationEntry 2 } -- 13.3.2.3 Network Address of the Logical Name Translation logicalNameTranslationNetworkAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object defines the network address of the associated network entity for the given profile. If the transport profile is 'internet, the network address is the IP address of the entity stored as an IpAddress. If the transport profile is 't2, there is no physical network address, but the entity is assigned a dummy IP address in order to abstract the mapping to the ipNetToMediaTable defined in MIB-II. This object was deprecated because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. This object was originally defined with the syntax of NetworkAddress; The NetworkAddress is not defined in SNMPv3 and is actually an alias of IpAddress (i.e., it was defined as CHOICE {internet IpAddress}, which in BER is encoded exactly the same as IpAddress.) The conversion to SMIv2 replaced this syntax with IpAddress. 1.3.6.1.4.1.1206.4.1.1.7.4.2.1.3" -- DEFVAL { 0 } ::= { logicalNameTranslationEntry 3 } -- 13.3.2.4 Logical Name Translation Status logicalNameTranslationStatus OBJECT-TYPE SYNTAX NtcipRowStatusStatic MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object allows for the management of rows within the table. This object was deprecated because the SNMPv3 includes the definition of targets in the SNMP-TARGET-MIB, as defined in RFC 3413. 1.3.6.1.4.1.1206.4.1.1.7.4.2.1.4" DEFVAL { invalid } ::= { logicalNameTranslationEntry 4 } -- 13.4 COMPLIANCE GROUPS -- 13.4.1 Logical Names Group logicalNamesGroupR1 OBJECT-GROUP OBJECTS { logicalNameTranslationTableMaxEntries, logicalNameTranslationIndex, logicalNameTranslationLogicalName, logicalNameTranslationNetworkAddress, logicalNameTranslationStatus } STATUS deprecated DESCRIPTION " The objects necessary for managing logical names. 1.3.6.1.4.1.1206.4.1.1.7.4.127.2.1" ::= {logicalNamesGroups 1} END -- NTCIP1201-LogicalNames -- Section 14 -- 14.1 HEADER NTCIP1201-Report DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Counter32, Opaque, zeroDotZero FROM SNMPv2-SMI -- RFC 2578 VariablePointer FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP FROM SNMPv2-CONF global FROM NTCIP1201-Global; globalReport MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-globalReport MIB, which was defined in NTCIP 1103. This MIB defines objects related to managing event information for the Purpose of logging data within the device. This MIB was deprecated in NTCIP 1201 v04 due to security issues in the structure of the MIB. The objects have been replaced by objects in the ISO 20684 series. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.2.6.4 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Separated into its own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version." ::= { global 4 } -- NOTE The event class table is presented first to ease -- the readability of the standard; however, the node numbers -- assigned to this table reflect the original node numbering used -- in the original 1996 specification to preserve backwards -- compatibility with existing systems. -- 14.2 OBJECT IDENTITIES -- 14.2.1 Logical Names Conformance Node reportConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the event logging feature. 1.3.6.1.4.1.1206.4.2.6.4.127" ::= { globalReport 127 } reportCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the event logging feature. 1.3.6.1.4.1.1206.4.2.6.4.127.1" ::= { reportConformance 1 } reportGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the event logging feature. 1.3.6.1.4.1.1206.4.2.6.4.127.2" ::= { reportConformance 2 } -- 14.3 OBJECTS -- 14.3.1 Event Classes maxEventClasses OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "classes" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The object defines the number of rows in the eventClassTable that this device supports. This is a static table. The eventClassTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.2.6.4.5" ::= { globalReport 5 } -- 14.3.2 Event Class Table eventClassTable OBJECT-TYPE SYNTAX SEQUENCE OF EventClassEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This table is used to configure event logging limits and log table maintenance. static LOG-MIB.fdLogManagerTable (ISO 20684-5) 1.3.6.1.4.1.1206.4.2.6.4.6" ::= { globalReport 6 } eventClassEntry OBJECT-TYPE SYNTAX EventClassEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This defines a row in the Event Class Table LOG-MIB.fdLogManagerEntry (ISO 20684-5) The replacement table adds an index (fdLogManagerOwner) to allow administrators to limit access rights to groups of rows within the table and to allow users to define new rows without worrying if they are overwriting rows managed by other users. The replacement table also adds the following columns: a size limit (in octets) in addition to a limit on the number of entries, a separation of the time into a date and time to parallel the new way to represent time, parameters to configure the type of memory to use to store the log and the log configuration, a counter of the number of events bumped, and a row status. It is missing the number of rows currently in the log. 1.3.6.1.4.1.1206.4.2.6.4.6.1" INDEX { eventClassNumber } ::= { eventClassTable 1 } EventClassEntry ::= SEQUENCE { eventClassNumber Integer32, eventClassLimit Integer32, eventClassClearTime Unsigned32, eventClassDescription OCTET STRING, eventClassNumRowsInLog Integer32, eventClassNumEvents Integer32} -- 14.3.2.1 Event Class Number Parameter eventClassNumber OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This is a class value that is to be configured. LOG-MIB.fdLogManagerName (ISO 20684-5) The replacement object is a secondary index that uses an SnmpAdminString syntax; the primary index is LOG-MIB.fdLogManagerOwner which also uses an SnmpAdminSyntax. 1.3.6.1.4.1.1206.4.2.6.4.6.1.1" ::= { eventClassEntry 1 } -- 14.3.2.2 Event Class Limit Parameter eventClassLimit OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "events" MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies the maximum number of events of the associated class to store in the log. Once the limit is reached, the oldest entry of the matching class will be overwritten by any new entry of the same class. If the value of this object is set to a number smaller than the current number of rows within this class in the eventLogTable, then the oldest entries shall be lost/deleted. The sum of all event class limits shall not exceed the maxEventLogSize object; if a SET operation to this object causes the sum of eventClassLimit objects to exceed maxEventLogSize, then the agent shall respond with a genErr. The event cannot be logged if the eventClass has an eventClassLimit of zero (0). Event LOG-MIB.fdLogManagerSizeLimit & LOG- MIB.fdLogManagerEntryLimit (ISO 20684-5) The replacement objects allow limits to be placed on the number of entries or the total size. The replacement object for the number of entries has a syntax of Unsigned32. 1.3.6.1.4.1.1206.4.2.6.4.6.1.2 " ::= { eventClassEntry 2 } -- 14.3.2.3 Event Class Clear Time Parameter eventClassClearTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object is used to clear multiple event log entries from the eventLogTable. All events of this class that have an eventLogTime equal to or less than this object shall be cleared from the eventLogTable. If this object has a value greater than the current value of globalTime, it shall prevent the logging of any events of this class. LOG-MIB.fdLogManagerClearDate & LOG- MIB.fdLogManagerClearTime (ISO 20684-5) This SMIv2 representation of the original SMIv1 object uses an Unsigned32 syntax rather than the original Counter syntax because the definition of the object does not meet the semantics defined for a Counter object. As a result, this object will have a different value in the 'type' field in the BER encoding when transmitted using SNMPv3 (and using SMIv2) than when transmitted using SNMPv1 (and using the SMIv1 definition). The superseding objects use the extended time format that includes a date object (good to the year 65535) and a time object (with millisecond resolution). 1.3.6.1.4.1.1206.4.2.6.4.6.1.3" DEFVAL {0} ::= { eventClassEntry 3 } -- 14.3.2.4 Event Class Description Parameter eventClassDescription OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies a description of the class in ASCII characters. LOG-MIB.fdLogManagerDescription (ISO 20684-5) The replacement object specifies an SnmpAdminString Syntax, which allows management systems to automatically recognize the entry as text in any language. 1.3.6.1.4.1.1206.4.2.6.4.6.1.4" ::= { eventClassEntry 4 } -- 14.3.2.5 Event Class Number of Rows in Event Log Table Parameter eventClassNumRowsInLog OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "events" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows for this class that currently exist in the eventLogTable. The replacement table does not include a parallel object for this object. 1.3.6.1.4.1.1206.4.2.6.4.6.1.5" ::= { eventClassEntry 5 } -- 14.3.2.6 Class Event Log Counter Parameter eventClassNumEvents OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "events" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object is a counter that gets incremented every time an event occurs for this class; it shall initialize to zero at power up. The value shall roll over each time it exceeds the maximum of 65535. LOG-MIB.fdLogManagerEventsLogged (ISO 20684-5) The replacement object has a syntax of Counter32. 1.3.6.1.4.1.1206.4.2.6.4.6.1.6" ::= { eventClassEntry 6 } -- 14.3.3 Maximum Event Log Configurations Parameter maxEventLogConfigs OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "event types" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows that exist in the static eventLogConfig table for this device. The eventLogConfigTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.2.6.4.1" ::= { globalReport 1} -- 14.3.4 Event Log Configuration Table eventLogConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF EventLogConfigEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing Event Log Configuration information. The number of rows in this table is equal to the maxEventLogConfigs object. This table defines the parameters that the device will monitor to create an event. static LOG-MIB.fdLogFactoryTable (ISO 20684-5) & COND- TRIGGER-MIB.fdCondTriggerTable (ISO 20684-3) 1.3.6.1.4.1.1206.4.2.6.4.2" ::= { globalReport 2 } eventLogConfigEntry OBJECT-TYPE SYNTAX EventLogConfigEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines an entry in the event log configuration table. LOG-MIB.fdLogFactoryEntry (ISO 20684-5) & COND- TRIGGER-MIB.fdCondTriggerEntry (ISO 20684-3) The replacement tables have dual indicies consisting of An owner and a name. The trigger table manages the definition of the trigger with the following changes: - A textual description is added - Samples (compare value) can be either the current value (as with this node, or a delta (i.e., how fast a value is changing) - The concept of Opaque is not supported in SNMPv3, so the replacement table includes a 'ValueOctet' object that is used with the bitwise operator - A wildcard column that allows defining the same condition on multiple comparison OIDs (e.g., all rows of a table) - Columns to define the target and context of the comparison object; in other words, the comparison can be performed by a proxy agent or can reference another device to get the object value to compare against - A frequency object that allows the configuration to control how frequently a comparison is made - A truthDuration object that allows the configuration to require the evaluation to be true for some length of time prior to firing the trigger. - Startup objects that define whether the triggers startup in a fired or unfired state (for hysteresis, there are two startups) - A pointer to the action table that identifies the action(s) to be performed. - An error message object that allows a device to report configuration errors. - Counters for the number of times the trigger has fired, had Evaluation errors, and activation errors. - An indication of the type of storage to use - A RowStatus object. The log factory table manages the definition of the information to be recorded with the following changes: - An object context, which allows a proxy/hrbrid agent to capture information from another context - A StorageType object - A RowStatus object 1.3.6.1.4.1.1206.4.2.6.4.2.1" INDEX { eventConfigID } ::= { eventLogConfigTable 1 } EventLogConfigEntry ::= SEQUENCE { eventConfigID Integer32, eventConfigClass Integer32, eventConfigMode INTEGER, eventConfigCompareValue Integer32, eventConfigCompareValue2 Integer32, eventConfigCompareOID VariablePointer, eventConfigLogOID VariablePointer, eventConfigAction INTEGER, eventConfigStatus INTEGER } -- 14.3.4.1 Event Log Configuration ID Parameter eventConfigID OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object contains the row number which is used to identify the event associated with this row in the eventLogConfigTable. The number of event IDs shall not exceed the value indicated in the maxEventLogConfigs object. LOG-MIB.fdLogManagerOwner, fdLogFactoryName (ISO 20684-5), COND-TRIGGER-MIB.fdActionOwner & fdCondTriggerName (ISO 20684-3) The replacement object specifies an SnmpAdminString Syntax, which allows management systems to automatically recognize the entry as text in any language. 1.3.6.1.4.1.1206.4.2.6.4.2.1.1" ::= { eventLogConfigEntry 1 } -- 14.3.4.2 Event Log Configuration Class Parameter eventConfigClass OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the class value to assign to the event associated with this row in the event configuration table. This value is used in the event log table to organize various events defined in this table into logical groupings. This value shall not exceed the maxEventClasses object value. NOTE-The event cannot be logged if the EventClass has an eventClassLimit of zero (0). LOG-MIB.fdLogEventFactoryLogName (ISO 20684-5) The replacement object specifies an SnmpAdminString 1.3.6.1.4.1.1206.4.2.6.4.2.1.2" DEFVAL {1} ::= { eventLogConfigEntry 2 } -- 14.3.4.3 Event Log Configuration Mode Parameter eventConfigMode OBJECT-TYPE SYNTAX INTEGER { other (1), onChange (2), greaterThanValue (3), smallerThanValue (4), hysteresisBound (5), periodic (6), andedWithValue (7) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies the mode of operation for this event. The modes are defined as follows: Value Description other the event mode of operation is not described in this standard, refer to the device manual. onChange create a log entry when the object value referenced by eventConfigCompareOID changes. The values of eventConfigCompareValue and eventConfigCompareValue2 are ignored in this mode. greaterThanValue create a log entry when the object value referenced by eventConfigCompareOID becomes greater than the value of eventConfigCompareValue for the time (tenth seconds) defined by eventConfigCompareValue2 (zero means immediate logging). smallerThanValue create a log entry when the object value referenced by eventConfigCompareOID becomes less than the value of eventConfigCompareValue for the time (tenth seconds) defined by eventConfigCompareValue2 (zero means immediate logging). hysteresisBound create a log entry when the object value referenced by eventConfigCompareOID becomes less than or greater than the bound values. The lowerbound value is the lower value of eventConfigCompareValue and eventConfigCompareValue2; the upperbound value is the higher value of the two values. When the object value becomes greater than the upper bound value, subsequent logging of upperbound conditions shall not occur until the object value becomes less than the lower bound value. When the object value becomes less than the lower bound value, subsequent logging of lowerbound conditions shall not occur until the object value becomes greater than the upper bound value. Periodic create a log entry every x seconds, where x is defined by the value stored in eventConfigCompareValue. The values stored in eventConfigCompareValue2 and eventConfigCompareOID are ignored in this mode. andedWithValue create a log entry when the object value referenced by eventConfigCompareOID ANDED with the value of eventConfigCompareValue is NOT equal to zero for the time (tenth seconds) defined by eventConfigCompareValue2 (zero means immediate logging). This allows monitoring of a specific bit; the condition becomes true anytime that any one of the selected bits become true. COND-TRIGGER-MIB.fdCondTriggerMode (ISO 20684-3) The replacement object adds the following modes: - equal - not equal - on creation (i.e., creation of a new row in a table) - on deletion - separate modes for octet string and integer bitwise operations 1.3.6.1.4.1.1206.4.2.6.4.2.1.3" DEFVAL {onChange} ::= { eventLogConfigEntry 3 } -- 14.3.4.4 Event Log Configuration Compare Value Parameter eventConfigCompareValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the comparison value to use with eventConfigMode values (greaterThanValue, smallerThanValue, hysteresisBound ). No value within this object is necessary when the eventConfigMode-object has the value onChange (2). COND-TRIGGER-MIB.fdCondTriggerValue & fdCondTriggerValueOctet (ISO 20684-3) The interger-based replacement object conforms to SNMPv3 rules and does not allow the specification of a 64-bit value and requires integers to be defined as either signed or unsigned. eventConfigCompareValue is perhaps ambiguous about this, although SNMPv1 conventions dictate the same functionality. The result is that the current design does not allow for comparing large unsigned integer values. 1.3.6.1.4.1.1206.4.2.6.4.2.1.4" DEFVAL {0} ::= { eventLogConfigEntry 4 } -- 14.3.4.5 Event Log Configuration Compare Value 2 Parameter eventConfigCompareValue2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION "If the eventConfigMode is set to hysteresisBound, this object specifies the second comparison value for the hysteresis. If the eventConfigMode is set to greaterThanValue, smallerThanValue, or andedWithValue, this object specifies the time (in tenths of seconds, +1 tenth / -0 tenths) for which the samples used for comparison shall be true prior to the event condition becoming true. If the eventConfigMode is set to onChange or periodic, the value of this object shall be ignored. The amount of time the condition shall be true is measured in tenths of a second. The accuracy of this timer is limited to +1 tenth of a second and:0 tenths of a second. If the event is true for at least the time shown in this parameter +1 tenth of a second, the condition shall trigger a log entry. It is recognized that some designs only sample the condition periodically, in which case the condition shall be true for at least the time indicated by this object before the event becomes true and the event shall always become true if the condition is true for a duration equal to the value shown in this object plus 1 tenth of a second. COND-TRIGGER-MIB.fdCondTriggerValue2 (ISO 20684-3) 1.3.6.1.4.1.1206.4.2.6.4.2.1.5" DEFVAL {0} ::= { eventLogConfigEntry 5 } -- 14.3.4.6 Event Log Configuration Compare Object Identifier Parameter eventConfigCompareOID OBJECT-TYPE SYNTAX VariablePointer MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the object identifier which references the value against which the comparison is made. If the eventConfigMode is set to periodic, the value of this object shall be ignored. If the eventConfigMode is set to greaterThanValue, smallerThanValue or hysteresisBound, this object shall reference an object whose SYNTAX resolves to a ranged or unranged INTEGER. As with all other objects that are sub-ranged by a given implementation, an agent should return a badValue error if it receives a set command indicating a OID which is not supported by the implementation or which is not zeroDotZero. COND-TRIGGER-MIB.fdCondTriggerObject (ISO 20684-3) 1.3.6.1.4.1.1206.4.2.6.4.2.1.6" DEFVAL { zeroDotZero } ::= { eventLogConfigEntry 6 } -- 14.3.4.7 Event Log Configuration Log Object Identifier Parameter eventConfigLogOID OBJECT-TYPE SYNTAX VariablePointer MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the object identifier which indicates what value to log when a condition or event occurs (e.g., log the phase display when the watchdog alarm status changes). As with all other objects that are sub-ranged by a given implementation, an agent should return a badValue error if it receives a set command indicating a value which is not supported by the implementation. The valid value range of this object shall not include any values, other than zeroDotZero, that do not correspond to objects that may exist within the agent, although it may be further restricted. The valid value range of this object shall not include objects under the following nodes: Security - { nema transportation devices global security } CHAP - { nema transportation protocols layers chap } LOG-MIB.fdLogEventFactoryObjectID (ISO 20684-5) 1.3.6.1.4.1.1206.4.2.6.4.2.1.7" DEFVAL { zeroDotZero } ::= { eventLogConfigEntry 7 } -- 14.3.4.8 Event Log Configuration Action Parameter eventConfigAction OBJECT-TYPE SYNTAX INTEGER { other (1), disabled (2), log (3) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The value of this object indicates what action shall take place when this event occurs. Other - indicates that the action is other than defined in this standard. This value exists in order to support proprietary event logging mechanisms configured by other means not specified in this standard. If this value is used in a SET request, the agent shall respond with a badValueError. Disabled - no event log entry shall be generated or recorded due to this event. In an agent complying with NTCIP 1103 v03 or later, this event shall not be used to trigger NTCIP traps, nor to construct NTCIP trap messages. Log - an event log entry shall be generated when this event occurs. In an agent complying with NTCIP 1103 v03 and later, this may trigger an NTCIP trap (see the eventConfigID index element of trapTable). If eventConfigClass refers to an eventClassTable row having eventClassLimit = 0, the log entry's eventLogValue shall be used to construct any necessary trap messages implied by the associated trapTable rows, but the log entry shall then be discarded and not added to the eventLogTable. If the eventClassLimit is greater than zero, the log entry shall be added to the eventLogTable, subject to the constraints imposed by the associated eventConfigClass. COND-TRIGGER-MIB.fdCondTriggerActionOwner, fdCondTriggerAction, fdCondTriggerActionOwner2, & fdCondTriggerAction2 (ISO 20684-3) The replacement object points to a table that can point to multiple actions. For example, a single trigger can result in both a log entry and a notification. 1.3.6.1.4.1.1206.4.2.6.4.2.1.8" DEFVAL {disabled} ::= { eventLogConfigEntry 8 } -- 14.3.4.9 Event Log Configuration Status Parameter eventConfigStatus OBJECT-TYPE SYNTAX INTEGER { other (1), disabled (2), log (3), error (4) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The value of this object indicates the current status of the configured event. Upon setting any object in this row of the eventLogConfigTable, the agent will determine if the setting is valid and will set this object to one of the following states: other indicates that the action is successfully set to a mode other than that defined in this standard disabled indicates that the action is set to disabled log indicates that the action is successfully set to the log state after passing consistency checks. Error indicates that the requested action could not be implemented due to a consistency check COND-TRIGGER-MIB.fdCondTriggerRowStatus (ISO 20684-3) & LOG-MIB.fdLogEventFacoryRowStatus (ISO 20684-5) 1.3.6.1.4.1.1206.4.2.6.4.2.1.9" ::= { eventLogConfigEntry 9 } -- 14.3.5 Maximum Event Log Size Parameter maxEventLogSize OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "events" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The maximum, fixed number of rows that can be utilized within the eventLogTable. LOG-MIB.fdLogsGlobalEntryLimit and fdLogsGlobalSizeLimit (ISO 20684-3) The replacement objects are for all managers. 1.3.6.1.4.1.1206.4.2.6.4.3" ::= { globalReport 3} -- 14.3.6 Event Log Table eventLogTable OBJECT-TYPE SYNTAX SEQUENCE OF EventLogEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing Event History data collected. A request for an object from a row that has not been instantiated or has been cleared shall return a noSuchName error. dynamic LOG-MIB.fdLogTable (ISO 20684-5) 1.3.6.1.4.1.1206.4.2.6.4.4" ::= { globalReport 4 } eventLogEntry OBJECT-TYPE SYNTAX EventLogEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines an entry in the event log Table. LOG-MIB.fdLogEntry (ISO 20684-5) EventLogTable was modified in NTCIP 1103 v03 to add an entry eventLogTimeMilliseconds Integer, which did not exist in NTCIP 1103 v02. The replacement table precedes the class/manager and number indicies With an owner so that access to information in the table can be controlled with proper configuration of the SNMP agent. The replacement table also records both the date and time of the event and the date and time that the event was placed into the table (i.e., so that if there is latency, a command to clear the table does not inadvertently delete rows that had occurred but had not been entered into the table. 1.3.6.1.4.1.1206.4.2.6.4.4.1" INDEX { eventLogClass, eventLogNumber } ::= { eventLogTable 1 } EventLogEntry ::= SEQUENCE { eventLogClass Integer32, eventLogNumber Integer32, eventLogID Integer32, eventLogTime Unsigned32, eventLogValue Opaque, eventLogTimeMilliseconds Integer32 } -- 14.3.6.1 Event Log Class Parameter eventLogClass OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the class of the associated event as defined in the eventLogConfig Table. LOG-MIB.fdLogManagerOwner & fdLogManagerName (ISO 20684-5) The replacement objects are SnmpAdminStrings 1.3.6.1.4.1.1206.4.2.6.4.4.1.1" ::= { eventLogEntry 1 } -- 14.3.6.2 Event Log Number Parameter eventLogNumber OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The event number within this class for this event. Event numbers shall be assigned starting at 1 and shall increase to the value specified by the associated eventClassLimit for the class associated with the rows. Events shall maintain a chronological ordering in the table with the oldest event of a class occupying the row with eventNumber = 1, and subsequent events filling subsequent rows. This ordering shall be maintained for those rows still remaining when events are cleared. LOG-MIB.fdLogIndex (ISO 20684-5) The replacement object is an Unsigned32 1.3.6.1.4.1.1206.4.2.6.4.4.1.2" ::= { eventLogEntry 2 } -- 14.3.6.3 Event Log ID Parameter eventLogID OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the event configuration ID (from the eventLogConfigTable) that caused this table entry. It indicates the row in the eventLogConfig table responsible for this event entry. LOG-MIB.fdLogFactoryName (ISO 20684-5) The replacement object is an SnmpAdminString 1.3.6.1.4.1.1206.4.2.6.4.4.1.3" ::= { eventLogEntry 3 } -- 14.3.6.4 Event Log Time Parameter eventLogTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The time that the event was detected. If the device supports the globalTime object, the value shall reflect the value of globalTime when the event occurred, otherwise this shall be the time in seconds since the device powered up. The event shall be detected and timestamped within one second from the event becoming true. The event shall be logged in the table within five seconds of the event being detected. These timing resolutions may be modified by a device profile. LOG-MIB.fdLogEventDate, fdLogEventTime, fdLogDate, fdLogTime (ISO 20684-5) This SMIv2 representation of the original SMIv1 object uses an Unsigned32 syntax rather than the original Counter syntax because the definition of the object does not meet the semantics defined for a Counter object. As a result, this object will have a different value in the 'type' field in the BER encoding when transmitted using SNMPv3 (and using SMIv2) than when transmitted using SNMPv1 (and using the SMIv1 definition). The superseding objects adopt the new time format. They also distinguish between event time and log time. 1.3.6.1.4.1.1206.4.2.6.4.4.1.4" ::= { eventLogEntry 4 } -- 14.3.6.5 Event Log Value Parameter eventLogValue OBJECT-TYPE SYNTAX Opaque MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The value of this object is set to the BER encoding of the value referenced by the eventConfigLogOID of the associated eventLogID when the event was logged. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. LOG-MIB.fdLogValue (ISO 20684-5) The replacement object uses an ITSOerString (i.e., the value is in OER and sent over SNMP with a BER wrapper as opposed to the Opaque which created a double BER wrapper). This means that the manager who requests the value must know the syntax that was encoded. 1.3.6.1.4.1.1206.4.2.6.4.4.1.5" ::= { eventLogEntry 5 } -- 14.3.6.6 Event Log Time Milliseconds Parameter eventLogTimeMilliseconds OBJECT-TYPE SYNTAX Integer32 (0..999) UNITS "milliseconds" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of milliseconds after the beginning of the second indicated by the value of eventLogTime at which the event was detected. Devices that do not support sub-second event time resolution shall always set this object to zero. When implementing eventLogTimeMilliseconds, devices require a time source with millisecond-level resolution, such as GPS or TIA (International Atomic Time). This data content is covered by the new time format used by LOG-MIB.fdLogEventTime & fdLogTime (ISO 20684-5) 1.3.6.1.4.1.1206.4.2.6.4.4.1.6" ::= { eventLogEntry 6 } -- 14.3.7 Total Event Log Counter Parameter numEvents OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "events" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object is a counter that gets incremented every time an event occurs and shall initialize to zero at power up. The value shall roll over each time it exceeds the maximum of 65535. LOG-MIB.fdLogsTotalLogged (ISO 20684-5) The replacement object uses a syntax of Counter32, which does not require a zero-base. 1.3.6.1.4.1.1206.4.2.6.4.7" ::= { globalReport 7 } -- 14.3.8 Event Log Time Latency Parameter eventTimeLatency OBJECT-TYPE SYNTAX Integer32 (0..1000) UNITS "milliseconds" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object indicates the maximum amount of time, in milliseconds, that may elapse between an event's occurrence and the time reported for that event entry in the eventLogTable. This is a global, constant value that reports the capability of the device with respect to event-reporting latency. It should account for all sources of latency, including both hardware and firmware delays. If eventTimeLatency has a value of L, this means that any event in the eventLogTable may actually have occurred up to L milliseconds prior to the time reported by the eventLogTime and eventLogTimeMilliseconds values associated with the event. A value of 0 indicates that the device reports accurate event times with millisecond resolution. A value of 1000 indicates that the device cannot accurately report sub-second event times. LOG-MIB.fdLogsRecordingLatency (ISO 20684-5) The replacement object places limits on the time between retrieving the value to log and the logging rather than what is described here. 1.3.6.1.4.1.1206.4.2.6.4.8" ::= { globalReport 8 } -- 14.4 COMPLIANCE GROUPS -- 14.4.1 Report Group reportGroupR1 OBJECT-GROUP OBJECTS { maxEventClasses, eventClassNumber, eventClassLimit, eventClassClearTime, eventClassDescription, eventClassNumRowsInLog, eventClassNumEvents, maxEventLogConfigs, eventConfigID, eventConfigClass, eventConfigMode, eventConfigCompareValue, eventConfigCompareValue2, eventConfigLogOID, eventConfigAction, eventConfigStatus, maxEventLogSize, eventLogClass, eventLogNumber, eventLogID, eventLogTime, eventLogValue } STATUS deprecated DESCRIPTION " The objects necessary for managing the event logging feature. 1.3.6.1.4.1.1206.4.2.6.4.127.2.1" ::= {reportGroups 1} -- 14.4.2 Report Group Extension reportGroupR1Ext OBJECT-GROUP OBJECTS { eventLogTimeMilliseconds, numEvents, eventTimeLatency } STATUS deprecated DESCRIPTION " The extended objects necessary for managing the event logging feature. 1.3.6.1.4.1.1206.4.2.6.4.127.2.2" ::= {reportGroups 2} END -- NTCIP1201-Report -- Section 15 -- 15.1 HEADER NTCIP1201-Security DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, Integer32, Gauge32 FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 global FROM NTCIP1201-Global; security MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-Security MIB, which was defined in NTCIP 1103. This MIB defines objects related to managing the configuration of community names and associated access rights for SNMPv1 packets. This MIB was deprecated in NTCIP 1201 v04 due to security limitations of SNMPv1. The objects contained in this MIB are no longer relevant as Security is now based on (D)TLS certificates combined with SNMP securityNames as defined in the Transport Security Model (RFC 5591) and the TLS Transport Model (RFC 6353). However, this MIB defines how to exchange this data to enable a manager to remotely manage these objects through a proxy agent. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.2.6.5 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Separated into its own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version." ::= {global 5} -- 15.2 OBJECT IDENTITIES -- 15.2.1 Security Conformance Node securityConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the community names for SNMPv1 deployments. 1.3.6.1.4.1.1206.4.2.6.5.127" ::= { security 127 } securityCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the community names for SNMPv1 deployments. 1.3.6.1.4.1.1206.4.2.6.5.127.1" ::= { securityConformance 1 } securityGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the community names for SNMPv1 deployments. 1.3.6.1.4.1.1206.4.2.6.5.127.2" ::= { securityConformance 2 } -- 15.3 OBJECTS -- 15.3.1 Community Name Administrator Parameter communityNameAdmin OBJECT-TYPE SYNTAX OCTET STRING (SIZE(8..16)) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object is the community name that shall be used to specifically gain access to information under the security node. A message with this value in the community name field of an SNMP message has user read-write access to the security node objects and all other objects implemented in the device. The syntax is defined as an OCTET STRING and therefore any character can have a value of 0..255. This object has been deprecated along with the use of SNMPv1. 1.3.6.1.4.1.1206.4.2.6.5.1" DEFVAL { "administrator" } ::= { security 1 } -- 15.3.2 Maximum Community Names Parameter communityNamesMax OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object specifies the maximum number of rows that are implemented in the community name table. This object has been deprecated along with the use of SNMPv1. 1.3.6.1.4.1.1206.4.2.6.5.2" ::= { security 2 } -- 15.3.3 Community Names Table communityNameTable OBJECT-TYPE SYNTAX SEQUENCE OF CommunityNameTableEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " This table defines the community names that can appear in the community name field of the SNMP message and access privileges associated with that community name. static This object has been deprecated along with the use of SNMPv1. 1.3.6.1.4.1.1206.4.2.6.5.3" ::= { security 3 } communityNameTableEntry OBJECT-TYPE SYNTAX CommunityNameTableEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " This is the row index of information in the community name table. This object has been deprecated along with the use of SNMPv1. 1.3.6.1.4.1.1206.4.2.6.5.3.1" INDEX { communityNameIndex } ::= { communityNameTable 1} CommunityNameTableEntry::=SEQUENCE { communityNameIndex Integer32, communityNameUser OCTET STRING, communityNameAccessMask Gauge32 } -- 15.3.3.1 Community Name Index Parameter communityNameIndex OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object defines the row index into the communityNameTable. This value shall not exceed the communityNamesMax object value. This object has been deprecated along with the use of SNMPv1. 1.3.6.1.4.1.1206.4.2.6.5.3.1.1" ::= { communityNameTableEntry 1 } -- 15.3.3.2 User Community Name Parameter communityNameUser OBJECT-TYPE SYNTAX OCTET STRING (SIZE(6..16)) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object defines a community name value that a security administrator can assign user read-write access to information (other than security) in a device. A message with this value in the community name field of an SNMP/SFMP message has user access rights as defined in the communityNameAccessMask. The syntax is defined as an OCTET STRING and therefore any character can have a value of 0..255. This object has been deprecated along with the use of SNMPv1. 1.3.6.1.4.1.1206.4.2.6.5.3.1.2" DEFVAL { "public" } ::= { communityNameTableEntry 2 } -- 15.3.3.3 User Community Name Mask Parameter communityNameAccessMask OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object defines a 32 bit mask that can be used to associate 'write access' with a community name. A value of 0x00 00 00 00 grants the community name user read-only access and overrides any individual object's read-write access clause. A value of 0xFF FF FF FF grants the community name user read-write access and an individual object's read-write access clause applies. Values other than 0x00 00 00 00 and 0xFF FF FF FF are implementation specific and may limit viewing and/or accessing the information in a device. This object has been deprecated along with the use of SNMPv1. 1.3.6.1.4.1.1206.4.2.6.5.3.1.3" DEFVAL { 4294967295 } ::= { communityNameTableEntry 3 } -- 15.4 COMPLIANCE GROUPS -- 15.4.1 Security Group securityGroupR1 OBJECT-GROUP OBJECTS { communityNameAdmin, communityNamesMax, communityNameIndex, communityNameUser, communityNameAccessMask } STATUS deprecated DESCRIPTION " The objects necessary for managing the community names for SNMPv1 deployments. 1.3.6.1.4.1.1206.4.2.6.5.127.2.1" ::= {securityGroups 1} END -- NTCIP1201-Security -- Section 16 -- 16.1 HEADER NTCIP1201-NtcipTraps DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Integer32, Unsigned32, Counter32, IpAddress, zeroDotZero FROM SNMPv2-SMI -- RFC 2578 DisplayString FROM SNMPv2-TC -- RFC 2579 OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC 2580 ITSOerString FROM FIELD-DEVICE-TC-MIB -- ISO 20684-1 Annex A application, protocols, NtcipRowStatusStatic FROM NTCIP8004-Transportation eventConfigID FROM NTCIP1201-Report; ntcipTraps MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-Traps MIB, which was defined in NTCIP 1103. This MIB defines objects related to: (a) configuration of block and watch objects, (b) configuration and monitoring of traps This MIB was deprecated in NTCIP 1201 v04 due to security issues in the structure of the MIB. The objects have been replaced by objects in the ISO 20684 series. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.4 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - No change." REVISION "200903310000Z" DESCRIPTION "NTCIP 1103 v02 - Separated into its own MIB." REVISION "200409270000Z" DESCRIPTION "NTCIP 1103 v01: Original version." ::= {protocols 4} -- 16.2 OBJECT IDENTITIES -- 16.2.1 Watch Blocks watchBlocks OBJECT-IDENTITY STATUS deprecated DESCRIPTION " Watch Blocks are OER encoded configurable read only blocks intended to be utilized for device status monitoring in the eventConfigCompareOID in the eventConfigTable. The intent is to be able to configure events to monitor a collection of NTCIP objects at the same time, and trigger the logging and/or transmission of a trap message. Note that when a watch block is used for the eventConfigCompareOID, the eventConfigMode object is restricted to onChange (2) Any entry with an attempt to use any other mode shall be ignored at run time. Because there is no restriction on the order in which the entries are created, specifying a watch block that has not been configured does not generate an error. Likewise care should be taken to ensure that the configuration of the event table and the watch blocks (as well as the report blocks) are consistent and correct. 1.3.6.1.4.1.1206.4.1.1.7.6" ::= { application 6 } -- 16.2.2 Report Blocks reportBlocks OBJECT-IDENTITY STATUS deprecated DESCRIPTION " Report blocks are OER encoded configurable read only blocks intended to be utilized for device status and other parameters as the eventConfigLogOID in the eventConfigTable. Like the watch blocks, they can only be validated at run-time. Improperly configured report blocks shall be ignored. 1.3.6.1.4.1.1206.4.1.1.7.7" ::= { application 7 } -- 16.2.3 Clear Objects eventClearObjects OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to group all objects for support of clearing the report node (events) and report objects. 1.3.6.1.4.1.1206.4.1.1.7.8" ::= { application 8 } -- 16.2.4 NTCIP Trap Management trapMgmt OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node defines information used to manage the generation and issuance of traps. 1.3.6.1.4.1.1206.4.1.4.1" ::= {ntcipTraps 1} -- 16.2.5 NTCIP Trap Data ntcipTrapData OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node defines information to be reported by the trap management feature. 1.3.6.1.4.1.1206.4.1.4.2" ::= {ntcipTraps 2} -- 16.2.6 NTCIP Trap Notifications ntcipTrapNotifications OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node defines trap information to be reported by the trap management feature. SMIv2 defines notifications, which can be sent as unacknowledged 'traps' or acknowledged 'informs'. The SMIv2 NOTIFICATION-TYPE macro registers traps on the naming tree and per RFC 4181, to provide backward compatibility the OID of a notification should be the SNMPv1 'enterprise' followed by a node '0' followed by the number assigned to the SMIv1 trap. This node provides the prefix to define such notifications. 1.3.6.1.4.1.1206.4.1.4.2.0" ::= {ntcipTrapData 0} -- 16.2.7 Trap Management Conformance Node ntcipTrapConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage traps. 1.3.6.1.4.1.1206.4.1.4.127" ::= { ntcipTraps 127 } ntcipTrapCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage traps. 1.3.6.1.4.1.1206.4.1.4.127.1" ::= { ntcipTrapConformance 1 } ntcipTrapGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage traps. 1.3.6.1.4.1.1206.4.1.4.127.2" ::= { ntcipTrapConformance 2 } -- 16.3 WATCH BLOCKS -- In addition to the objects mentioned below, the replacement feature -- includes objects to indicate: -- a) the encodings supported (BER and/or OER) -- b) whether there are limitations on the support for structures that allow -- new values (i.e., set operations) -- c) whether the supports one-step processing, two-step processing, or both -- 16.3.1 Maximum Watch Objects maxWatchObjects OBJECT-TYPE SYNTAX Integer32 (150..8192) UNITS "watch objects" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows that exist in the watchObjectDefinitionTable for this device. OBJECT-GROUP-MIB.fdObjectGroupsMaxObjects (ISO 20684-7) The watchObjectDefinitionTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows; however, the replacement object allows implementations to impose a limit on the size of block objects and to inform the user of the limit. 1.3.6.1.4.1.1206.4.1.1.7.6.1" ::= { watchBlocks 1 } -- 16.3.2 Maximum Watch Blocks maxWatchBlocks OBJECT-TYPE SYNTAX Integer32 (1..50) UNITS "watch blocks" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows that exist in the watchBlockTable for this device. The watchBlockTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.1.1.7.6.2" ::= { watchBlocks 2 } -- 16.3.3 Watch Object Definition Table watchObjectDefinitionTable OBJECT-TYPE SYNTAX SEQUENCE OF WatchObjectDefinitionEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing Watch Object definition information. The number of rows in this table is equal to the maxWatchObjects object. static OBJECT-GROUP-MIB.fdObjectGroupFieldTable (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.6.3" ::= { watchBlocks 3 } watchObjectDefinitionEntry OBJECT-TYPE SYNTAX WatchObjectDefinitionEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines an entry in the Watch Object Definition table. OBJECT-GROUP-MIB.fdObjectGroupFieldEntry (ISO 20684-7) The replacement table has a three-part index consisting of a group owner (which provides a level of protection from other users from changing the definition without authorization), a group name (which is functionally equivalent to watchBlock), and field index (which is functionally equivalent to watchID). 1.3.6.1.4.1.1206.4.1.1.7.6.3.1" INDEX { watchID } ::= { watchObjectDefinitionTable 1 } WatchObjectDefinitionEntry ::= SEQUENCE { watchID Integer32, watchStatus NtcipRowStatusStatic, watchBlock Integer32, watchOID OBJECT IDENTIFIER } -- 16.3.3.1 Watch Identification Parameter watchID OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the row number which is used to identify the object associated with this row in the watchObjectDefinitionTable. This value shall not exceed the value indicated by the maxWatchObjects object. OBJECT-GROUP-MIB.fdObjectGroupFieldIndex (ISO 20684-7) The replacement object is the third part of a three-part index and is defined as an Unsigned32. 1.3.6.1.4.1.1206.4.1.1.7.6.3.1.1" ::= { watchObjectDefinitionEntry 1 } -- 16.3.3.2 Watch Status Parameter watchStatus OBJECT-TYPE SYNTAX NtcipRowStatusStatic MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The value of this object indicates the current status of the this row in the table. The replacement table does not have a RowStatus object; when changes are necessary, the entire object needs to be cleared and redefined. 1.3.6.1.4.1.1206.4.1.1.7.6.3.1.2" DEFVAL { invalid } ::= { watchObjectDefinitionEntry 2 } -- 16.3.3.3 Watch Block Parameter watchBlock OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the block number to assign to the watch object associated with this row in the watch object definition table. This value shall not exceed the value indicated by the maxWatchBlocks object. OBJECT-GROUP-MIB.fdObjectGroupName (ISO 20684-7) The replacement object is the second part of a three- part index and is defined as an SnmpAdminString (SIZE(0..32)) 1.3.6.1.4.1.1206.4.1.1.7.6.3.1.3" DEFVAL { 1 } ::= { watchObjectDefinitionEntry 3 } -- 16.3.3.4 Watch Object Identifier Parameter watchOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the object identifier of the object to watch. The following objects shall NOT be assigned to any watchOID: All objects under the security node (Annex B) { nema transportation devices global security } All objects under the dynObjMgmt node (Annex A) {nema transportation protocols dynObjMgmt} All objects under the chap node (Annex B of NTCIP 2301) { nema transportation protocols layers chap } Any objects so identified by various device standards Any objects whose SYNTAX does NOT resolve to a ranged or unranged INTEGER. Any other report object or watch object Any objects that the agent/device does not support. An agent should return a badValue error if it receives a SET command for any of the above. OBJECT-GROUP-MIB.fdObjectGroupFieldObject (ISO 20684-7) The replacement object does not define any restrictions currently. 1.3.6.1.4.1.1206.4.1.1.7.6.3.1.4" DEFVAL { zeroDotZero } ::= { watchObjectDefinitionEntry 4 } -- 16.3.4 Watch Block Table watchBlockTable OBJECT-TYPE SYNTAX SEQUENCE OF WatchBlockEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table containing the Watch Blocks defined in the Watch Object Definition table. The number of rows in this table is equal to the value of the maxWatchBlocks object. static OBJECT-GROUP-MIB.fdObjectGroupTable (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.6.4" ::= { watchBlocks 4 } watchBlockEntry OBJECT-TYPE SYNTAX WatchBlockEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This defines a row in the watchBlockTable. OBJECT-GROUP-MIB.fdObjectGroupEntry (ISO 20684-7) The replacement table has a dual index consisting of an owner and a group name. The table has the following changes: - the encoding can be selected (BER or OER) - the ObjectGroup can be configured for retrieval as either a one- step or two-step process. In other words, one-step groups can be retrieved directly; two-step groups have to be refreshed in one command and retrieved in a second command. - there is a refresh command and a refresh date/time associated with the two-step process. There is also an object that provides an estimated duration for generating the result (which can be as simple as a duration multiplied by the number of objects) - there is a 'new value' object that allows setting the referenced objects (i.e., similar to a dynObj set command) - there are 'last error' and 'last error index' objects to provide insights into any issues that arise - there is a 'clear' object that allows clearing the definition of all fields defined for the object group - Added an indication of the type of storage to use - the table is dynamic with a RowStatus object. 1.3.6.1.4.1.1206.4.1.1.7.6.4.1" INDEX { watchBlockNumber } ::= { watchBlockTable 1 } WatchBlockEntry ::= SEQUENCE { watchBlockNumber Integer32, watchBlockStatus NtcipRowStatusStatic, watchBlockDescription OCTET STRING, watchBlockValue ITSOerString } -- 16.3.4.1 Watch Block Number watchBlockNumber OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The block number for this row in the table. This value shall not exceed the value indicated by the maxWatchBlocks object. OBJECT-GROUP-MIB.fdObjectGroupName (ISO 20684-7) The replacement object is the second part of a two-part index and is defined as an SnmpAdminString. 1.3.6.1.4.1.1206.4.1.1.7.6.4.1.1" ::= { watchBlockEntry 1 } -- 16.3.4.2 Watch Block Status watchBlockStatus OBJECT-TYPE SYNTAX NtcipRowStatusStatic MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The value of this object indicates the current status of this row in the table. OBJECT-GROUP-MIB.fdObjectGroupRowStatus (ISO 20684-7) The replacement object uses RowStatus to support a dynamic table 1.3.6.1.4.1.1206.4.1.1.7.6.4.1.2" DEFVAL { invalid } ::= { watchBlockEntry 2 } -- 16.3.4.3 Watch Block Description watchBlockDescription OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..20)) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object may be used to define a description of this watch block. OBJECT-GROUP-MIB.fdObjectGroupDescription (ISO 20684-7) The replacement object is defined as an SnmpAdminString to support any language with automatic display as text. 1.3.6.1.4.1.1206.4.1.1.7.6.4.1.3" DEFVAL { "" } ::= { watchBlockEntry 3 } -- 16.3.4.4 Watch Block Value watchBlockValue OBJECT-TYPE SYNTAX ITSOerString MAX-ACCESS read-only STATUS deprecated DESCRIPTION " An OER encoded string of all object values defined in watchObjectDefinitionTable, pointed at by watchOID (in watchID order) where the watchBlock IS watchBlockNumber AND the watchStatus IS available. OBJECT-GROUP-MIB.fdObjectGroupCurrentValue (ISO 20684-7) The original syntax for this object was OerString as defined in NTCIP 8004 v02. NTCIP 8004 v03 recommends the use of ITSOerString in SMIv2 modules as it is formally defined as a textual convention in ISO 20684-1. Both OerString and ITSOerString resolve to OCTET STRING, so while the written syntax has changed, there is no impact on how it is encoded. The replacement object, fdObjectGroupCurrentValue, is defined as an OCTET STRING because it can represent either an OER-string or a BER- string depending on the value of fdObjectGroupEncoding. 1.3.6.1.4.1.1206.4.1.1.7.6.4.1.4" DEFVAL { "" } ::= { watchBlockEntry 4 } -- 16.4 REPORT BLOCKS -- The reportBlocks feature is replaced by the same fdObjectGroup feature -- defined in ISO 20684-7 as used to replace the watchBlocks. The -- notes in this section are generally omitted as they would -- repeat the content contained in the watchBlocks section of the MIB. -- 16.4.1 Maximum Report Objects maxReportObjects OBJECT-TYPE SYNTAX Integer32 (150..8192) UNITS "report objects" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows that exist in the reportObjectDefinitionTable for this device. OBJECT-GROUP-MIB.fdObjectGroupsMaxObjects (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.1" ::= { reportBlocks 1 } -- 16.4.2 Maximum Report Blocks maxReportBlocks OBJECT-TYPE SYNTAX Integer32 (1..50) UNITS "report blocks" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows that exist in the reportBlockTable for this device. The watchBlockTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.1.1.7.7.2" ::= { reportBlocks 2 } -- 16.4.3 Report Object Configuration Table reportObjectDefinitionTable OBJECT-TYPE SYNTAX SEQUENCE OF ReportObjectDefinitionEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing Report Object definition information. The number of rows in this table is equal to the maxReportObjects object. static OBJECT-GROUP-MIB.fdObjectGroupFieldTable (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.3" ::= { reportBlocks 3 } reportObjectDefinitionEntry OBJECT-TYPE SYNTAX ReportObjectDefinitionEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines an entry in the Report Object Definition table. OBJECT-GROUP-MIB.fdObjectGroupFieldEntry (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.3.1" INDEX { reportID } ::= { reportObjectDefinitionTable 1 } ReportObjectDefinitionEntry ::= SEQUENCE { reportID Integer32, reportStatus NtcipRowStatusStatic, reportBlock Integer32, reportOID OBJECT IDENTIFIER } -- 16.4.3.1 Report Identification Parameter reportID OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the row number which is used to identify the objects associated with this row in the reportObjectDefinitionTable. This value shall not exceed the value indicated by the maxReportObjects object. OBJECT-GROUP-MIB.fdObjectGroupFieldIndex (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.3.1.1" ::= { reportObjectDefinitionEntry 1 } -- 16.4.3.2 Report Status Parameter reportStatus OBJECT-TYPE SYNTAX NtcipRowStatusStatic MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The value of this object indicates the current status of the this row in the table. The replacement table does not have a RowStatus object; when changes are necessary, the entire object needs to be cleared and redefined. 1.3.6.1.4.1.1206.4.1.1.7.7.3.1.2" DEFVAL { invalid } ::= { reportObjectDefinitionEntry 2 } -- 16.4.3.3 Report Block Parameter reportBlock OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the block number to assign to the log object associated with this row in the reportObjectDefinitionTable. This value shall not exceed the value indicated by the maxReportBlocks object. OBJECT-GROUP-MIB.fdObjectGroupName (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.3.1.3" DEFVAL { 1 } ::= { reportObjectDefinitionEntry 3 } -- 16.4.3.4 Report Object Identifier Parameter reportOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the object identifier of the object to log. The following objects shall NOT be assigned to any reportOID: All objects under the security node (Annex B) { nema transportation devices global security } All objects under the dynObjMgmt node (Annex A) {nema transportation protocols dynObjMgmt} All objects under the chap node (Annex B of NTCIP 2301) { nema transportation protocols layers chap } Any other report object or watch object Any objects so identified by various device standards Any objects that the agent/device does not support. An agent should return a badValue error if it receives a SET command for any of the above. OBJECT-GROUP-MIB.fdObjectGroupFieldObject (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.3.1.4" DEFVAL { zeroDotZero } ::= { reportObjectDefinitionEntry 4 } -- 16.4.4 Report Block Table reportBlockTable OBJECT-TYPE SYNTAX SEQUENCE OF ReportBlockEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " A table containing the Report blocks defined in the reportObjectDefinitionTable. The number of rows in this table is equal to the value of the maxReportBlocks object. static OBJECT-GROUP-MIB.fdObjectGroupTable (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.4" ::= { reportBlocks 4 } reportBlockEntry OBJECT-TYPE SYNTAX ReportBlockEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This defines a row in the reportBlockTable. OBJECT-GROUP-MIB.fdObjectGroupEntry (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.4.1" INDEX { reportBlockNumber } ::= { reportBlockTable 1 } ReportBlockEntry ::= SEQUENCE { reportBlockNumber Integer32, reportBlockStatus NtcipRowStatusStatic, reportBlockDescription OCTET STRING, reportBlockValue ITSOerString } -- 16.4.4.1 Report block Number reportBlockNumber OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The block number for this row in the table. This value shall not exceed the value indicated by the maxReportBlocks object. OBJECT-GROUP-MIB.fdObjectGroupName (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.4.1.1" ::= { reportBlockEntry 1 } -- 16.4.4.2 Report Block Status reportBlockStatus OBJECT-TYPE SYNTAX NtcipRowStatusStatic MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The value of this object indicates the current status of this row in the table. OBJECT-GROUP-MIB.fdObjectGroupRowStatus (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.4.1.2" DEFVAL { invalid } ::= { reportBlockEntry 2 } -- 16.4.4.3 Report Block Description reportBlockDescription OBJECT-TYPE SYNTAX OCTET STRING (SIZE(0..20)) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object may be used to define a description of this report block. OBJECT-GROUP-MIB.fdObjectGroupDescription (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.4.1.3" DEFVAL { "" } ::= { reportBlockEntry 3 } -- 16.4.4.4 Report Block Value reportBlockValue OBJECT-TYPE SYNTAX ITSOerString MAX-ACCESS read-only STATUS deprecated DESCRIPTION " An OER encoded string of all object values defined in reportObjectDefinitionTable, pointed at by reportOID (in reportID order) where the reportBlock IS reportBlockNumber AND the reportStatus IS available. OBJECT-GROUP-MIB.fdObjectGroupCurrentValue (ISO 20684-7) 1.3.6.1.4.1.1206.4.1.1.7.7.4.1.4" DEFVAL { "" } ::= { reportBlockEntry 4 } -- 16.5 TRAP MANAGEMENT -- 16.5.1 Trap Control trapControl OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The possible values are: 0 - disable NTCIP traps 1 - enable NTCIP traps The other values are reserved. NOTIFICATION-MIB.fdNotificationsEnabled (ISO 20684-4) The replacement object is defined as a TruthValue (RFC 2579), which is an enumeration where 1 = 'true' (in this case, enabled) and and 2 = 'false' (in this case, disabled). 1.3.6.1.4.1.1206.4.1.4.1.1" DEFVAL {0} ::= { trapMgmt 1 } -- 16.5.2 Trap Data trapData OBJECT-TYPE SYNTAX ITSOerString MAX-ACCESS read-only STATUS deprecated DESCRIPTION " It contains an octet string (event notification) with octet trap sequence number (trapMgmtSeqNum)and octet trap manager index (trapMgmtManagerIndex), followed by one or more OER encoded sequences of ventide (eventConfigID), eventTime (globalTime of the occurrence of the event), eventLogTimeMilliseconds (fractional second of the occurrence of the event), and reported data (as pointed to by eventConfigLogOID). For aggregated trap messages (ackTrapChain and noackTrapChain) the trapData contains the octet trap sequence number (trapMgmtSeqNum) and octet trap manager index (trapMgmtManagerIndex), followed by from 1 to trapMaxAggregationSize triplets. The sequence to which OER encoding is applied is formally defined by the TrapDataStructure (see Section 6.4.1). NOTIFICATION-MIB.fdNotificationData (ISO 20684-4) The original syntax for this object was OerString as defined in NTCIP 8004 v02. NTCIP 8004 v03 recommends the use of ITSOerString in SMIv2 modules as it is formally defined as a textual convention in ISO 20684-1. Both OerString and ITSOerString resolve to OCTET STRING, so while the written syntax has changed, there is no impact on how it is encoded. The replacement object switches the order of the initial index and sequence number. It also uses a ITSDailyTimeStamp, which indicates time of day to the millisecond. It also includes a latency of the data and each data field is presented as a CHOICE of either the data value or the PDU error that the get operation generated. 1.3.6.1.4.1.1206.4.1.4.1.2" ::= { trapMgmt 2 } -- 16.5.3 Trap Management Maximum Entries trapMgmtMaxEntries OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "entries" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The maximum number of entries in the trapMgmtTable. The trapMgmtTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.1.4.1.3" ::= { trapMgmt 3 } -- 16.5.4 Trap Maximum Aggregation Events trapMaxAggregationEvents OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "events" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object defines the maximum number of trap-events which can be aggregated. The object does not have a parallel in ISO 20684-4. 1.3.6.1.4.1.1206.4.1.4.1.4" ::= { trapMgmt 4 } -- 16.5.5 Trap Maximum Aggregation Size trapMaxAggregationSize OBJECT-TYPE SYNTAX Integer32 (1..1023) UNITS "octets" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object defines the maximum size (in bytes) of the aggregation chains that can be created during the aggregation process. NOTIFICATION-MIB.fdNotificationsMaxSize (ISO 20684-4) The replacement object is defined as an Unsigned32. 1.3.6.1.4.1.1206.4.1.4.1.5" ::= { trapMgmt 5 } -- 16.5.6 Trap Management Table trapMgmtTable OBJECT-TYPE SYNTAX SEQUENCE OF TrapMgmtEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " The table contains the list of management stations and their parameters where the agent traps are to be sent. static NOTIFICATION-MIB.fdNotifyChannelTable (ISO 20684-4) 1.3.6.1.4.1.1206.4.1.4.1.6" ::= { trapMgmt 6 } trapMgmtEntry OBJECT-TYPE SYNTAX TrapMgmtEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " This defines a row in the trapMgmtTable. NOTIFICATION-MIB.fdNotifyChannelEntry (ISO 20684-4) The replacement table has a dual-index of an owner and name, both SnmpAdminStrings; it is separately assigned an ID, which more closely relates to the trapMgmtManagerIndex. In addition to the changes described below, the replacement table adds the following columns: - A command to clear the current channel queue - A StorageType for the row - A RowStatus for the dynamic table 1.3.6.1.4.1.1206.4.1.4.1.6.1" INDEX { trapMgmtManagerIndex } ::= { trapMgmtTable 1 } TrapMgmtEntry ::= SEQUENCE { trapMgmtManagerIndex Integer32, trapMgmtManagerPointer Integer32, trapMgmtCommunityNamePointer Integer32, trapMgmtApplicationProtocol INTEGER, trapMgmtTransportProtocol INTEGER, trapMgmtPortNum Integer32, trapMgmtMaxRetries Integer32, trapMgmtRepeatInterval Integer32, trapMgmtDelta Integer32, trapMgmtQueueDepth Integer32, trapMgmtLinkStateStatus INTEGER, trapMgmtAntiStreamRate Integer32, trapMgmtErrStatus INTEGER, trapMgmtLostTraps Counter32, trapMgmtRowStatus NtcipRowStatusStatic, trapMgmtSeqNum Integer32, trapMgmtSeqNumAck Integer32 } -- 16.5.6.1 Trap Manager Index trapMgmtManagerIndex OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object provides the index into the trapMgmtTable. This value shall not exceed the trapMgmtMaxEntries object value. NOTIFICATION-MIB.fdNotifyChannelID (ISO 20684-4) The replacement object is defined as an ITSUnsigned16. 1.3.6.1.4.1.1206.4.1.4.1.6.1.1" ::= { trapMgmtEntry 1 } -- 16.5.6.2 Trap Logical Name Translation Entry Pointer trapMgmtManagerPointer OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " For UDP/IP stacks (trapMgmtTransportProtocol = 3), this value is equal to the logicalNameTranslationIndex for the logical name translation table entry where logicalNameTranslationName holds the logical name and logicalNameTranslationNetworkAddress holds the IP address of the destination management station for ntcip traps. Otherwise it is not used. This value shall not exceed the logicalNameTranslationTableMaxEntries object value. NOTIFICATION-MIB.fdNotifyChannelTarget (ISO 20684-4) The replacement object identifies an SNMP Target by its snmpTargetAddrName, as defined in RFC 3413. The snmpTargetAddrTable indicates the transport domain and address for the target. 1.3.6.1.4.1.1206.4.1.4.1.6.1.2" DEFVAL {1 } ::= { trapMgmtEntry 2 } -- 16.5.6.3 Trap Community Name Entry Pointer trapMgmtCommunityNamePointer OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This value is equal to the communityNameIndex for the community name table entry where communityNameUser holds the community name for ntcip traps sent to the destination management station. This value shall not exceed communityNamesMax object value. SNMP-TARGET-MIB.snmpTargetParamsSecurityModel, snmpTargetParamsSecurityName, & snmpTargetParamsSecurityLevel (RFC 3413) In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains the security information to be used to communicate with the Target. 1.3.6.1.4.1.1206.4.1.4.1.6.1.3" DEFVAL { 1 } ::= { trapMgmtEntry 3 } -- 16.5.6.4 Trap Application Layer Protocol trapMgmtApplicationProtocol OBJECT-TYPE SYNTAX INTEGER { other (1), snmp (2), sfmp (3) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object identifies the application layer protocol to use for TMP (Transportation Management Protocol) traps. The possible values are: 1 - other : not defined in this standard 2 - snmp : use SNMPv1 Trap 3 - sfmp : use SFMP Trap SNMP-TARGET-MIB.snmpTargetParamsMPModel (RFC 3413) In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which points to a row in the snmpTargetParamsTable, which contains snmpTargetParamsMPModel, which indicates a message processing model (i.e., SNMPv1 vs. SNMPv3). If the NTCIP (or NEMA) community desired, it could define its own processing model (e.g., something similar to SFMP with security) and assign it a value of (1206 * 256) + id, where id is between 0 and 255 (see RFC 3411). 1.3.6.1.4.1.1206.4.1.4.1.6.1.4" DEFVAL { snmp } ::= { trapMgmtEntry 4 } -- 16.5.6.5 Trap Transport Layer Protocol trapMgmtTransportProtocol OBJECT-TYPE SYNTAX INTEGER { other (1), t2 (2), udp (3) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object identifies the transport profile to use for TMP traps. The possible values are: 1 - other : not defined in standard 2 - t2 : use T2 encapsulation to omit the port number 3 - udp : use UDP/IP stack SNMP-TARGET-MIB.snmpTargetAddrTDomain (RFC 3413) In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which contains snmpTargetAddrTDomain, which identifies the transport domain to be used; registered domains can be found at https://www.iana.org/ assignments/snmp-number-spaces/snmp-number-spaces.xhtml. For example, the snmpTLSTCPDomain is 1.3.6.1.6.1.8 and snmpDTLSUDPDomain is 1.3.6.1.6.1.9. 1.3.6.1.4.1.1206.4.1.4.1.6.1.5" DEFVAL { udp } ::= { trapMgmtEntry 5 } -- 16.5.6.6 Trap Port Number trapMgmtPortNum OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " Port of the destination management station (e.g. 162 - default SNMP Trap port). SNMP-TARGET-MIB.snmpTargetAddrTAddress (RFC 3413) In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which contains snmpTargetAddrTAddress, which is defined in a format defined by the snmpTargetAddrTDomain. For snmpTLSTCPDomain and snmpDTLSUDPDomain, the Taddress includes the port number; other protocols support similar values. 1.3.6.1.4.1.1206.4.1.4.1.6.1.6" DEFVAL {162} ::= { trapMgmtEntry 6 } -- 16.5.6.7 Trap Maximum Retransmission Retries trapMgmtMaxRetries OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "tries" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The maximum number of times an agent attempts to retransmit a trap before transitioning to the error state. Note: A value of one indicates that the agent attempts a maximum of two transmissions. SNMP-TARGET-MIB.snmpTargetAddrRetryCount (RFC 3413) In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which contains snmpTargetAddrRetryCount, which is an equivalent object. 1.3.6.1.4.1.1206.4.1.4.1.6.1.7" DEFVAL {0} ::= { trapMgmtEntry 7 } -- 16.5.6.8 Trap Repeat Interval trapMgmtRepeatInterval OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The minimum number of seconds to wait before retransmitting a trap that has not been acknowledged. A value of zero (0) indicates an immediate retransmission of the trap. SNMP-TARGET-MIB.snmpTargetAddrTimeout (RFC 3413) In the replacement design, fdNotifyChannelTarget points to a row in the snmpTargetAddrTable, which contains snmpTargetAddrTimeout, which indicates the timeout in hundredths of a second (up to 24 million seconds, which is almost a year). 1.3.6.1.4.1.1206.4.1.4.1.6.1.8" DEFVAL {60} ::= { trapMgmtEntry 8 } -- 16.5.6.9 Trap Repeat Interval Timeout Delta trapMgmtDelta OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " A number of seconds to be added to the total timeout for the next trap retransmission. In the replacement design, there is no equivalent to this object because as the definition of the timeout parameter indicates that it is implementation dependent. 1.3.6.1.4.1.1206.4.1.4.1.6.1.9" DEFVAL {60} ::= { trapMgmtEntry 9 } -- 16.5.6.10 Trap Maximum Number of Queued Traps trapMgmtQueueDepth OBJECT-TYPE SYNTAX Integer32 (0..50) UNITS "traps" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The maximum number of traps that can be queued for the Management station. Setting this value to zero flushes and disables the queue, and prevents any queueable traps from being sent. NOTIFICATION-MIB.fdNotifyChannelQueueDepth (ISO 20684-4) The replacement object has a syntax of Unsigned32. 1.3.6.1.4.1.1206.4.1.4.1.6.1.10" DEFVAL {1} ::= { trapMgmtEntry 10 } -- 16.5.6.11 Trap State of Communications Link trapMgmtLinkStateStatus OBJECT-TYPE SYNTAX INTEGER { other (1), ready (2), pending (3), error (4) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object contains the current link state of the manager registered in this row. The states are defined as follows: other (1) - not defined in this standard; ready (2) - any trap can be sent to the manager (initial condition after power-on); if an ACK trap appears in the queue the agent sends the trap message to the manager, starts timer and internal retry counter, and sets the state to pending; pending (3) - waiting for the manager to acknowledge the last ACK trap; NOACK and forced mode traps can be transmitted to the manager; if after all retries and timeouts the management station did not acknowledge an ACK trap message the agent sets the state to error error (4) - an ACK trap has not been acknowledged within the specified number of retries for this management station. Only force mode traps are transmitted to the management station until the link state is reset to ready. The replacement design does not have a need for this object because it relies upon the native Confirmed-Class and Unconfirmed-Class PDUs. If the notification is sent via a Confirmed-Class, it is the responsibility of the SNMP engine to discover missing confirmations and retry. 1.3.6.1.4.1.1206.4.1.4.1.6.1.11" REFERENCE "NTCIP 1103 v03 Section 6.3" ::= { trapMgmtEntry 11 } -- 16.5.6.12 Trap Antistreaming Rate trapMgmtAntiStreamRate OBJECT-TYPE SYNTAX Integer32 (1..255) UNITS "traps/minute" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " The maximum number of traps that can be generated on a specific link (trap channel) in one minute. The agent shall reset the anti-streaming counter at the start of each minute. If the anti- streaming rate is reached the agent shall set the 'Trap channel anti- streaming mode activated' bit in the trapMgmtErrStatus, send the current trap and cease sending any additional traps on this link (trap channel) until the start of the next minute. NOTIFICATION-MIB.fdNotifyChannelAntiStreamRate (ISO 20684-4) The replacement object has a syntax of Unsigned32. 1.3.6.1.4.1.1206.4.1.4.1.6.1.12" DEFVAL {10} ::= { trapMgmtEntry 12 } -- 16.5.6.13 Trap Error Status trapMgmtErrStatus OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Trap channel status mask. When a bit = 1 the error status is true. When a bit = 0 the error status is false. Bit 7: Reserved Bit Bit 6: Reserved Bit Bit 5: Reserved Bit Bit 4: Reserved Bit Bit 3: Reserved Bit Bit 2: Trap channel has trapMgmtLinkStateStatus = error Bit 1: Trap channel anti-streaming mode activated Bit 0: Trap channel queue full The replacement design does not have an equivalent object. 1.3.6.1.4.1.1206.4.1.4.1.6.1.13" ::= { trapMgmtEntry 13 } -- 16.5.6.14 Trap Lost Trap Counter trapMgmtLostTraps OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS deprecated DESCRIPTION " Counter for the number of traps that have been discarded due to the queue for this trap channel being full. NOTIFICATION-MIB.fdNotifyChannelDroppedCount (ISO 20684-4) The replacement object expands the definition for dropping a notification packet for any reason before transmission. Note: Counters are not required to be zero-based. 1.3.6.1.4.1.1206.4.1.4.1.6.1.14" ::= { trapMgmtEntry 14 } -- 16.5.6.15 Trap Row Status trapMgmtRowStatus OBJECT-TYPE SYNTAX NtcipRowStatusStatic MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object allows for the management of rows within the table. NOTIFICATION-MIB.fdNotifyChannelRowStatus (ISO 20684-4) The replacement object has a syntax of RowStatus, which provides a dynamic table. 1.3.6.1.4.1.1206.4.1.4.1.6.1.15" DEFVAL { invalid } ::= { trapMgmtEntry 15 } -- 16.5.6.16 Trap Sequence Number trapMgmtSeqNum OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object contains the sequence number of the last new trap that has been sent on this link. It is included in the trap message to assist a management station in identifying duplicate trap messages or detect when trap messages are missed. The agent shall increment this counter on each new trap message, but not retries, sent to the management station. The first trap message sent after a power-on reset or after trapMgmtRowStatus is successfully activated has trapMgmtSeqNum = 1. The sequence number is reset to 1 after a trap is sent with trapMgmtSeqNum == 255. NOTIFICATION-MIB.fdNotifyChannelSeqNum (ISO 20684-4) The replacement object has a syntax of Counter32. 1.3.6.1.4.1.1206.4.1.4.1.6.1.16" REFERENCE "NTCIP 1103 v03 Section 6.2.6" ::= { trapMgmtEntry 16 } -- 16.5.6.17 Trap Acknowledge Sequence Number trapMgmtSeqNumAck OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object is set to the sequence number of the trap that is being acknowledged by the management station. If the value set equals either the current value of trapMgmtSeqNumAck or zero (0), then the agent changes the trapMgmtLinkStateStatus from pending or error to ready and set this object to zero (0) indicating no ack traps are awaiting acknowledgement. If this object is set to any other value, then the agent ignores the set and continue the normal acknowledge process including retries. Within the replacement design, it is the responsibility of the SNMP engine to ensure that Confirmed-Class notifications are acknowledged. 1.3.6.1.4.1.1206.4.1.4.1.6.1.17" REFERENCE "NTCIP 1103 v03 Section 6.2.7" ::= { trapMgmtEntry 17 } -- 16.5.7 Trap Table trapTable OBJECT-TYPE SYNTAX SEQUENCE OF TrapEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " The table specifies the trap operational mode for each event registered in the eventLogConfigTable (NTCIP 1201) and necessary to run NTCIP Trap operations. Each entry in the trapTable can be individually enabled and disabled and is assigned its own mode per trap channel. An event can be sent to multiple trap channels by creating multiple entries in the trapTable for the same event, each with a different trapMgmtManagerIndex. static NOTIFICATION-MIB.fdNotifyFactoryTable (ISO 20684-4) The replacement table is dynamic. 1.3.6.1.4.1.1206.4.1.4.1.7" ::= { trapMgmt 7 } trapEntry OBJECT-TYPE SYNTAX TrapEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION " This defines a row in the trapTable. NOTIFICATION-MIB.fdNotifyFactoryEntry (ISO 20684-4) The replacement table uses a dual index with owner and name. It is not directly connected to the trigger table; it is called by it as one potential action. The replacement table adds the following columns: - An event id that provides a concise identifier for the event, similar to eventConfigID. - The notification channel to use; i.e., in the new design, a specific event can result in multiple notifications (presumably to different managers) - The object to be sent (i.e., the new design allows for different information to be logged and to be sent) - A StorageType column - A RowStatus column 1.3.6.1.4.1.1206.4.1.4.1.7.1" INDEX { eventConfigID, trapMgmtManagerIndex } ::= { trapTable 1 } TrapEntry ::= SEQUENCE { trapDestEnable Integer32, trapMode Integer32, trapAggregationTime Integer32, trapCounter Counter32 } -- 16.5.7.1 Trap Destination Enabled trapDestEnable OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " Setting this object to one (1) enables the trap (eventConfigID) for transmission through the trap channel (trapMgmtManagerIndex). A value of zero (0) disables events with eventConfigID from being acted on with respect to the transmission of traps through the specific trap channel identified in the trapMgmtTable. Note: The transmission (or queuing) of the trap also depends on entries in the eventLogConfigTable and the trapMgmtTable. Entries in all three tables are required to be enabled for the trap to be queued or transmitted. NOTIFICATION-MIB.fdNotifyFactoryRowStatus (ISO 20684-4) The replacement object allows creation and deletion of the entry as well. 1.3.6.1.4.1.1206.4.1.4.1.7.1.1 " DEFVAL {0} ::= { trapEntry 1 } -- 16.5.7.2 Trap Mode trapMode OBJECT-TYPE SYNTAX INTEGER { forced (1), ack-noQ (2), ack (3), noack-noQ (4), noack (5), ack-Aggr (6), noack-Aggr (7) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object defines a number of different methods for handling the trap data prior to or as it is transferred to the trap channel. The trap modes are as follows: 1 - forced: NOACK, the trap is sent (not queued) regardless of the trapMgmtLinkStateStatus. 2 - ack_noQ: ACK, the trap is sent if the trapMgmtLinkStateStatus is READY; otherwise the trap is simply dropped (lost); however, if the trap is transmitted, it is acknowledged and the retry mechanism is invoked. 3 - ack: ACK, the trap is sent if the trapMgmtLinkStateStatus is READY, otherwise the trap message shall be queued. 4 - noack_noQ: NOACK, the trap is sent if the trapMgmtLinkStateStatus is READY or PENDING; otherwise the trap is simply dropped (lost). 5 - noack: NOACK, the trap is sent if the trapMgmtLinkStateStatus is READY or PENDING; it is queued if the channel status is ERROR. 6 - ack_Aggr: ACK, the trap data (eventConfigID, timestamp, and reported data) are added to the ackTrapChain for transmission to the management station when a chain termination condition occurs and the trapMgmtLinkStateStatus is READY. ackTrapChains are not queued and are transmitted prior to any queued traps. 7 - noack_Aggr: NOACK, the trap data (eventConfigID, timestamp, and reported data) are added to the noackTrapChain for transmission to the management station when a chain termination condition occurs and the trapMgmtLinkStateStatus is READY or PENDING; otherwise the noackTrapChain grows accepting new traps. 8+: reserved (not used in a proprietary manner) NOTIFICATION-MIB.fdNotifyFactoryAckEnabled & fdNotifyFactoryQueueEnabled (ISO 20684-4) The replacement object values map to the values of this object as follows: forced - there is no true parallel because the queue in trapMgmt is an artifact of the management of acknowledged traps with no defined role related to the anti-streaming rate. Within fdNotifyChannel, the queue solely relates to the antistreaming rate because the replacement design relies on the SNMP engine to manage responses and the link state is effectively always READY. There is no way to force an override of anti-streaming. Ack_noQ - AckEnabled = true and QueueEnabled = false: if the anti- streaming rate has not been exceeded, the notification is sent as an SNMP Inform message; otherwise, the notification is dropped. Ack - AckEnabled = true and QueueEnabled = true: if the anti- streaming rate has not been exceeded, the notification is sent as an SNMP Inform message; otherwise, it is added to the queue. If the addition of the packet to the queue would cause the queue depth to be exceeded, the oldest notification is deleted to make room for the most recent notification. Noack_noQ - AckEnabled = false and QueueEnabled = false: if the anti- streaming rate has not been exceeded, the notification is sent as an SNMP Trap message; otherwise, the notification is dropped. Noack - AckEnabled = false and QueueEnabled = true: if the anti- streaming rate has not been exceeded, the notification is sent as an SNMP Trap message; otherwise, the notification is added to the queue. If the addition of the packet to the queue would cause the queue depth to be exceeded, the oldest notification is deleted to make room for the most recent notification. Ack_Aggr - AckEnabled=true, QueueEnabled=false, AggregationTime>0: Same as ack_NoQ; there is no queue-jumping logic defined. Noack_Aggr - AckEnabled=false, QueueEnabled=false, AggregationTime>0: Same as noack_NoQ; there is no queue-jumping logic defined. 1.3.6.1.4.1.1206.4.1.4.1.7.1.2" REFERENCE "NTCIP 1103 v03, Sections 6.2.3 and 6.2.4" DEFVAL { forced } ::= { trapEntry 2 } -- 16.5.7.3 Trap Maximum Aggregation Time trapAggregationTime OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " maximum time (in seconds) that this trap can wait for transmission while being aggregated within a trap chain (for noack_Aggr and ack_Aggr traps only). The value of zero (0) indicates immediate trap chain transmission. The first trap with a mode specifying 'timed' aggregation starts this timer. The timer is reset when the trap chain is sent. The aggregation timers for each entry in the trap chain time concurrently and the first one to expire causes the entire trap chain to be sent to the management station. (Note that this is larger than 8 bits to allow aggregation times to support 5 minutes and longer). NOTIFICATION-MIB.fdNotifyFactoryAggregationTime (ISO 20684-4) 1.3.6.1.4.1.1206.4.1.4.1.7.1.3" REFERENCE "NTCIP 1103 v03 Section 6.2.4" DEFVAL {0} ::= { trapEntry 3 } -- 16.5.7.4 Trap Counter trapCounter OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS deprecated DESCRIPTION " this keeps track of the number of eventConfigID traps sent to the trap channel identified by the trapMgmtManagerIndex since the last (power-on) reset. It is incremented with the transmission or queuing (or addition to a trap chain) of each trap. By reading this parameter, a management station can verify the number of traps triggered for transmission or queuing by this event for this trap channel. NOTIFICATION-MIB.fdNotifyFactoryEventCount Counters are not zero-based. 1.3.6.1.4.1.1206.4.1.4.1.7.1.4" ::= {trapEntry 4 } -- 16.6 NTCIP TRAP DATA -- 16.6.1 Event Trap trapEvent NOTIFICATION-TYPE OBJECTS { trapData } STATUS deprecated DESCRIPTION " Indicates that one of the user-defined event specified in the eventLogConfigTable has occurred. The generation of the trap is governed by the rules defined in SNMP, Section 6 above, and the trapMgmtTable. The instances of the variables associates with this trap shall indicate those associated with the event notification being sent. NOTIFICATION-MIB.fdNotificationPacket 1.3.6.1.4.1.1206.4.1.4.2.0.1" ::= { ntcipTrapNotifications 1 } -- 16.7 CLEAR EVENT DATA -- 16.7.1 Clear Event Class eventClearClasses OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object identifies the event class to be cleared from the report node. A SET of n = 5..255, n <= maxEventClasses shall cause all information related to that class to be cleared from the report node. This includes clearing the event class table of eventClassNumber = n data, clearing all event configurations related to eventClassNumber = n, and clearing all event log entries for class n. A SET of 0 shall clear all classes as described. That is, completely clear the report node with the exception that the preconfigured event classes, their configurations, and their preconfigured event log entries are not cleared. A GET shall always return zero (0). If a device standard, Classes 1..4 are preconfigured and cannot be cleared. An attempt to clear Classes 1..4 shall return badValue. A value of n > maxEventClasses or > 255 if maxEventClasses is not configured, shall also return badValue. LOG-MIB.fdLogsDeleteAllConfiguration & fdLogManagerRowStatus (ISO 20684-5) An administrator can delete the configuration and data for all logs or an owner can choose to delete any specific configuration and associated data. 1.3.6.1.4.1.1206.4.1.1.7.8.1" ::= { eventClearObjects 1 } -- 16.7.2 Clear Event Configuration eventClearConfiguration OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the event configuration(s) to clear from the report node. A SET of n = 1..65535, n <= maxEventLogConfigs shall cause all information related to that configuration to be cleared from the report node. This includes clearing the event configuration table for all eventConfigID = n data, and clearing all event log entries for eventConfigID = n. A SET of 0 shall clear all configurations within the device as described (i.e. completely clear the report node with the exception that the eventClassTable is and preconfigured event configuration are not altered). A GET shall always return zero (0). Note: This object cannot be included in a block object. The device shall respond with badValue if the eventLogConfig = n does not exist. The device shall respond with badValue if an attempt to clear a preconfigured event log entries is made. LOG-MIB. fdLogEventFactoryRowStatus (ISO 20684-5) & COND-TRIGGER-MIB.fdCondTriggerRowStatus (ISO 20684-3) A user can separately delete the trigger and the factory. 1.3.6.1.4.1.1206.4.1.1.7.8.2" ::= { eventClearObjects 2 } -- 16.7.3 Clear Event Log Table eventClearLog OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to clear the eventLogTable. A SET of zero has no effect on the eventLogTable. A SET = 1 shall cause all event log entries to be deleted from the eventLogTable. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). LOG-MIB.fdLogsClearAllLogs The replacement object uses a syntax of TruthValue. 1.3.6.1.4.1.1206.4.1.1.7.8.3" ::= { eventClearObjects 3 } -- 16.7.4 Clear Report Objects clearReportObjects OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to effectively clear the report object and report block tables. A SET of zero has no effect on the tables. A SET = 1 shall set the row status object of all rows within both reportObjectDefinitionTable and reportBlockTable to invalid, effectively clearing the tables in one action. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). There is no parallel to this object in the replacement design. 1.3.6.1.4.1.1206.4.1.1.7.8.4" ::= { eventClearObjects 4 } -- 16.7.5 Clear Report Block Table clearReportBlockTable OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to effectively clear the report block table. A SET of zero (0) has no effect on the tables. A SET of one (1) shall set the row status object of all rows within reportBlockTable to invalid, effectively clearing the table in one action. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). There is no parallel to this object in the replacement design. 1.3.6.1.4.1.1206.4.1.1.7.8.5" ::= { eventClearObjects 5 } -- 16.7.6 Clear Watch Objects clearWatchObjects OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to effectively clear the watch object and watch block tables. A SET of zero has no effect on the tables. A SET = 1 shall set the row status object of all rows within both watchObjectDefinitionTable and watchBlockTable to 'invalid' effectively clearing the tables in one action. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). There is no parallel to this object in the replacement design. 1.3.6.1.4.1.1206.4.1.1.7.8.6" ::= { eventClearObjects 6 } -- 16.7.7 Clear Watch Block Table clearWatchBlockTable OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to effectively clear the watch block table. A SET of zero (0) has no effect on the tables. A SET of one (1) shall set the row status object of all rows within watchBlockTable to 'invalid' effectively clearing the table in one action. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). There is no parallel to this object in the replacement design. 1.3.6.1.4.1.1206.4.1.1.7.8.7" ::= { eventClearObjects 7 } -- 16.7.8 Clear Trap Management Table clearTrapMgmtTable OBJECT-TYPE SYNTAX Integer32 (0..1) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to effectively clear the trap management table and, as a consequence, the trap table. A SET of zero (0) has no effect on the tables. A SET of one (1) shall set the row status object of all rows within trapMgmtTable to 'invalid' effectively clearing the table in one action. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). Note: Because the trapMgmtIndex is also an index of trapTable, this action also effectively removes all rows of the trapTable. There is no parallel to this object in the replacement design. 1.3.6.1.4.1.1206.4.1.1.7.8.8" ::= { eventClearObjects 8 } -- 16.8 COMPLIANCE GROUPS -- 16.8.1 Watch Block Group watchBlockGroupR1 OBJECT-GROUP OBJECTS { maxWatchObjects, maxWatchBlocks, watchID, watchStatus, watchBlock, watchOID, watchBlockNumber, watchBlockStatus, watchBlockDescription, watchBlockValue } STATUS deprecated DESCRIPTION " The objects necessary for managing watch blocks. 1.3.6.1.4.1.1206.4.1.4.127.2.1" ::= {ntcipTrapGroups 1} -- 16.8.2 Report Block Group reportBlockGroupR1 OBJECT-GROUP OBJECTS { maxReportObjects, maxReportBlocks, reportID, reportStatus, reportBlock, reportOID, reportBlockNumber, reportBlockStatus, reportBlockDescription, reportBlockValue } STATUS deprecated DESCRIPTION " The objects necessary for managing watch blocks. 1.3.6.1.4.1.1206.4.1.4.127.2.2" ::= {ntcipTrapGroups 2} -- 16.8.3 Trap Management Group trapMgmtGroupR1 OBJECT-GROUP OBJECTS { trapControl, trapData, trapMgmtMaxEntries, trapMaxAggregationEvents, trapMaxAggregationSize, trapMgmtManagerIndex, trapMgmtManagerPointer, trapMgmtCommunityNamePointer, trapMgmtApplicationProtocol, trapMgmtTransportProtocol, trapMgmtPortNum, trapMgmtMaxRetries, trapMgmtRepeatInterval, trapMgmtDelta, trapMgmtQueueDepth, trapMgmtLinkStateStatus, trapMgmtAntiStreamRate, trapMgmtErrStatus, trapMgmtLostTraps, trapMgmtRowStatus, trapMgmtSeqNum, trapMgmtSeqNumAck, trapDestEnable, trapMode, trapAggregationTime, trapCounter } STATUS deprecated DESCRIPTION " The objects necessary for managing watch blocks. 1.3.6.1.4.1.1206.4.1.4.127.2.3" ::= {ntcipTrapGroups 3} -- 16.8.4 Trap Clear Group trapClearGroupR1 OBJECT-GROUP OBJECTS { eventClearClasses, eventClearConfiguration, eventClearLog, clearReportObjects, clearReportBlockTable, clearWatchObjects, clearWatchBlockTable, clearTrapMgmtTable } STATUS deprecated DESCRIPTION " The objects necessary for clearing trap-related information. 1.3.6.1.4.1.1206.4.1.4.127.2.4" ::= {ntcipTrapGroups 4} -- 16.8.5 Trap Group trapGroupR1 NOTIFICATION-GROUP NOTIFICATIONS { trapEvent } STATUS deprecated DESCRIPTION " The notification necessary for managing traps. 1.3.6.1.4.1.1206.4.1.4.127.2.5" ::= {ntcipTrapGroups 5} END -- NTCIP1201-NtcipTraps -- Section 17 -- 17.1 HEADER NTCIP1201-RecMech DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, Counter32, IpAddress, Opaque, zeroDotZero FROM SNMPv2-SMI -- RFC 2578 OBJECT-GROUP FROM SNMPv2-CONF -- RFC 2580 ITSOerString FROM FIELD-DEVICE-TC-MIB -- ISO 20684-1 Annex A application FROM NTCIP8004-Transportation; recMech MODULE-IDENTITY LAST-UPDATED "202210010000Z" ORGANIZATION "NTCIP BSP2 WG" CONTACT-INFO "name: NTCIP Coordinator email: ntcip@nema.org postal: National Electrical Manufacturers Association 1300 North 17th Street, Suite 1752 Rosslyn, Virginia 22209-3801" DESCRIPTION " This MIB defines the SMIv2 representation of the NTCIP1103v0352-recMech MIB, which was defined in NTCIP 1103. This MIB defines objects related to the recording mechanism functions that are found in devices. This MIB was deprecated in NTCIP 1201 v04 due to security issues in the structure of the MIB. The objects have been replaced by objects in the NTCIP1201v04-recMech MIB. *** All objects in this MIB have been deprecated. *** 1.3.6.1.4.1.1206.4.1.1.7.9 Copyright 1996, 2006, 2022 by the American Association of State Highway and Transportation Officials (AASHTO), the Institute of Transportation Engineers (ITE), and the National Electrical Manufacturers Association (NEMA). All intellectual property rights, including, but not limited to, the rights of reproduction in whole or in part in any form, translation into other languages and display are reserved by the copyright owners under the laws of the United States of America, the Universal Copyright Convention, the Berne Convention, and the International and Pan American Copyright Conventions. Joint NEMA, AASHTO, and ITE NTCIP Management Information Base DISTRIBUTION NOTICE To the extent and in the limited event these materials are distributed by AASHTO/ITE/NEMA in the form of a Management Information Base (MIB) module, AASHTO/ITE/NEMA extends the permission for users to make and/or distribute unlimited copies of the unedited MIB module, including copies for commercial distribution, provided that each copy made and/or distributed contains this Notice. The MIB module may be distributed with a companion MIB module that contains one or more invocations of the AGENT-CAPABILITIES macro that specifies the capabilities of a specific implementation. By convention, such a companion MIB module might have the same module name followed by '-', followed the enterprise's Internet Assigned Number Authority (IANA)-assigned enterprise number. These materials are delivered 'AS IS' without any warranties as to their use or performance. AASHTO/ITE/NEMA AND THEIR SUPPLIERS DO NOT WARRANT THE PERFORMANCE OR RESULTS YOU MAY OBTAIN BY USING THESE MATERIALS. AASHTO/ITE/NEMA AND THEIR SUPPLIERS MAKE NO WARRANTIES, EXPRESS OR IMPLIED, AS TO NONINFRINGEMENT OF THIRD-PARTY RIGHTS, MERCHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. IN NO EVENT WILL AASHTO, ITE OR NEMA OR THEIR SUPPLIERS BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY CLAIM OR FOR ANY CONSEQUENTIAL, INCIDENTAL OR SPECIAL DAMAGES, INCLUDING ANY LOST PROFITS OR LOST SAVINGS, ARISING FROM YOUR REPRODUCTION OR USE OF THESE MATERIALS, EVEN IF AN AASHTO, ITE, OR NEMA REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Some states or jurisdictions do not allow the exclusion or limitation of incidental, consequential or special damages, or the exclusion of implied warranties, so the above limitations may not apply to you. Use of these materials does not constitute an endorsement or affiliation by or between AASHTO, ITE, or NEMA and you, your company, or your products and services. NTCIP is a trademark of AASHTO/ITE/NEMA." REVISION "202210010000Z" DESCRIPTION "NTCIP 1201 v04 - Upgraded format to SMIv2 and deprecated all objects." REVISION "201612310000Z" DESCRIPTION "NTCIP 1103 v03 - Original version of this MIB." ::= { application 9 } -- 17.2 OBJECT IDENTITIES -- 17.2.1 Recording Mechanism Conformance Node recMechConformance OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the high- resolution recording mechanism. 1.3.6.1.4.1.1206.4.1.1.7.9.127" ::= { recMech 127 } recMechCompliances OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the high- resolution recording mechanism. 1.3.6.1.4.1.1206.4.1.1.7.9.127.1" ::= { recMechConformance 1 } recMechGroups OBJECT-IDENTITY STATUS deprecated DESCRIPTION " This node is an identifier used to manage the high- resolution recording mechanism. 1.3.6.1.4.1.1206.4.1.1.7.9.127.2" ::= { recMechConformance 2 } -- 17.3 OBJECTS -- NOTE-The recording mechanism class table is presented first to ease -- the readability of the standard. -- 17.3.1 Maximum Recording Mechanism Classes Parameter maxRecClasses OBJECT-TYPE SYNTAX Integer32 (1..254) UNITS "RecClasses" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The object defines the number of rows in the recClassTable that this device supports. This is a static table. The recClassTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.1.1.7.9.1" ::= { recMech 1 } -- 17.3.2 Recording Mechanism Class Table recClassTable OBJECT-TYPE SYNTAX SEQUENCE OF RecClassEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This table is used to configure recording mechanism limits and recording table maintenance. static NTCIP1201-RecMechV2.recMechV2ClassTable The replacement table is dynamic. 1.3.6.1.4.1.1206.4.1.1.7.9.2" ::= { recMech 2 } recClassEntry OBJECT-TYPE SYNTAX RecClassEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines a row in the Recording Mechanism Class Table NTCIP1201-RecMechV2.recMechV2ClassEntry The replacement table has a dual index consisting of an owner and a name, both SnmpAdminStrings. The table also adds columns for StorageType and RowStatus. 1.3.6.1.4.1.1206.4.1.1.7.9.2.1" INDEX { recClassNumber } ::= { recClassTable 1 } RecClassEntry ::= SEQUENCE { recClassNumber Integer32, recClassLimit Integer32, recClassClearTime Unsigned32, recClassDescription OCTET STRING, recClassNumRecordings Integer32, recClassRecordingCounter Integer32 } -- 17.3.2.1 Recording Mechanism Class Number Parameter recClassNumber OBJECT-TYPE SYNTAX Integer32 (1..254) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This is a class value that is to be configured. NTCIP1201-RecMechV2.recMechV2ClassName The replacement object is an SnmpAdminString. 1.3.6.1.4.1.1206.4.1.1.7.9.2.1.1" ::= { recClassEntry 1 } -- 17.3.2.2 Recording Mechanism Class Limit Parameter recClassLimit OBJECT-TYPE SYNTAX Integer32 (0..254) UNITS "recordings" MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies the maximum number of recordings of the associated class to store in the device. Once the limit is reached, the oldest recording of the matching class (based on recordingTriggerTime) is overwritten by any new recording of the same class. If the value of this object is set to a number smaller than the current number of rows within this class in the recRecordingTable, then the oldest entries shall be lost/deleted. The sum of all recording mechanism class limits shall not exceed the maxRecRecordings object; if a SET operation to this object causes the sum of recClassLimit objects to exceed maxRecRecordings, then the agent shall respond with a genErr. The recording cannot be logged if the recClass has an recClassLimit of zero (0). NTCIP1201-RecMechV2.recMechV2ClassSizeLimit The replacement object defines a maximum size in octets rather than the number of recordings. 1.3.6.1.4.1.1206.4.1.1.7.9.2.1.2" ::= { recClassEntry 2 } -- 17.3.2.3 Recording Mechanism Class Clear Time Parameter recClassClearTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object is used to clear multiple recordings from the recRecordingTable. All completed recordings of this class that have a recRecordingTriggerTime equal to or less than this object shall be cleared from the recRecordingTable. If this object has a value greater than the current value of globalTime, it shall prevent the triggering of any recordings of this class. NTCIP1201-RecMechV2.recMechV2ClassClearDate & recMechV2ClassClearTime The SMIv1 syntax for this object was Counter; however, by convention, an SNMPv1 Counter is not writable and SNMPv3 prohibits set operations. The syntax SMIv2 syntax for this object has been updated to Unsigned32 to avoid this conflict. The superseding objects provide a date/time pair. 1.3.6.1.4.1.1206.4.1.1.7.9.2.1.3" DEFVAL {0} ::= { recClassEntry 3 } -- 17.3.2.4 Recording Mechanism Class Description Parameter recClassDescription OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies a description of the class in ASCII characters. NTCIP1201-RecMechV2.recMechV2ClassDescription The replacement object uses a syntax of SnmpAdminString to clearly indicate that this should be readable text in any language. 1.3.6.1.4.1.1206.4.1.1.7.9.2.1.4" ::= { recClassEntry 4 } -- 17.3.2.5 Recording Mechanism Class Number of Rows in Recording Table Parameter recClassNumRecordings OBJECT-TYPE SYNTAX Integer32 (0..255) UNITS "recordings" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of recordings for this class that currently exist in the recRecordingTable. NTCIP1201-RecMechV2.recMechV2ClassNumRecordings 1.3.6.1.4.1.1206.4.1.1.7.9.2.1.5" ::= { recClassEntry 5 } -- 17.3.2.6 Class Recording Counter Parameter recClassRecordingCounter OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "recordings" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object is a counter that gets incremented every time a recording occurs for this class; it shall initialize to zero at power up. The value shall roll over each time it exceeds the maximum of 65535. NTCIP1201-RecMechV2.recMechV2ClassRecordingCtr The replacement object has a syntax of ZeroBasedCounter32. 1.3.6.1.4.1.1206.4.1.1.7.9.2.1.6" ::= { recClassEntry 6 } -- 17.3.3 Maximum Recording Configurations maxRecConfigs OBJECT-TYPE SYNTAX Integer32 (1..65534) UNITS "RecordType" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The number of rows that exist in the static recMechV2RecordingConfig table for this device. The recMechV2RecordingConfigTable has been replaced with a dynamic table, which does not require an object indicating the maximum number of rows. 1.3.6.1.4.1.1206.4.1.1.7.9.3" ::= { recMech 3} -- 17.3.4 Minimum Recording Sample Period recMinSamplePeriod OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "0.1 milliseconds" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The minimum sample period for recordings supported by the device in units of 0.1 milliseconds. NTCIP1201-RecMechV2.recMechMinSamplePeriod 1.3.6.1.4.1.1206.4.1.1.7.9.4" ::= { recMech 4} -- 17.3.5 Maximum Recording Sample Period recMaxSamplePeriod OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "0.1 milliseconds" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The maximum sample period for recordings supported by the device in units of 0.1 milliseconds. NTCIP1201-RecMechV2.recMechMaxSamplePeriod 1.3.6.1.4.1.1206.4.1.1.7.9.5" ::= { recMech 5} -- 17.3.6 Recording Sample Period Resolution recSamplePeriodResolution OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "0.1 milliseconds" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The sample period resolution for recordings supported by the device in units of 0.1 milliseconds. Allowable sample periods are restricted to (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution NTCIP1201-RecMechV2.recMechV2SamplePeriodResolution 1.3.6.1.4.1.1206.4.1.1.7.9.6" ::= { recMech 6} -- 17.3.7 Recording Configuration Table recConfigTable OBJECT-TYPE SYNTAX SEQUENCE OF RecConfigEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing Recording Mechanism Configuration information. The number of rows in this table is equal to the maxRecConfigs object. This table defines the parameters that the device monitors to create a recording. static NTCIP1201-RecMechV2.recMechV2FactoryTable & COND-TRIGGER-MIB.fdCondTriggerTable (ISO 20684-3) The replacement design divides the recConfigTable into two tables: one that defines triggers that can be used to start recordings or other actions and a second table that defines what to record when the recording action is triggered. 1.3.6.1.4.1.1206.4.1.1.7.9.7" ::= { recMech 7 } recConfigEntry OBJECT-TYPE SYNTAX RecConfigEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines an entry in the recording configuration table. NTCIP1201-RecMechV2.recMechV2FactoryEntry & COND-TRIGGER-MIB.fdCondTriggerEntry (ISO 20684-3) The replacement trigger table has two indicies: an owner and a name. The replacement recording factory table has three indicies, an owner, the class name, and the factory name. In addition to the other changes described, the trigger table adds the following columns: - a textual description of the trigger - an indication whether the comparison is based on the current object value or a delta from its previous reading - an octet-based comparison value since SNMPv3 discourages the use of Opaque - a wildcard that allows defining the same condition on multiple comparison OIDs (e.g., all rows of a table) - indications of the target and context of the comparison object; in other words, the comparison can be performed by a proxy agent or can reference another device to get the object value to compare against - the frequency at which the comparison is made - a truthDuration that allows the configuration to require the evaluation to be true for some length of time prior to firing the trigger. - startup states that define whether the triggers startup in a fired or unfired state (for hysteresis, there are two startups) - a pointer to the action table that identifies the action(s) to be performed. - an error message object that allows a device to report configuration errors. - counters for the number of times the trigger has fired, had evaluation errors, and activation errors. - an indication of the type of storage to use - a RowStatus object. The recMech factory table adds the following columns: - the security data used to activate the row and that will be used to retrieve values for the recording - object contexts, which allows a proxy/hrbrid agent to capture information from another context - A StorageType object 1.3.6.1.4.1.1206.4.1.1.7.9.7.1" INDEX { recConfigID } ::= { recConfigTable 1 } RecConfigEntry ::= SEQUENCE { recConfigID Integer32, recConfigClass Integer32, recConfigMode INTEGER, recConfigCompareValue Integer32, recConfigCompareValue2 Integer32, recConfigCompareOID OBJECT IDENTIFIER, recConfigRecordOID OBJECT IDENTIFIER, recConfigTriggerPoint Integer32, recConfigSamplePeriod Integer32, recConfigSampleOID OBJECT IDENTIFIER, recConfigNumEntries Integer32, recConfigAction INTEGER, recConfigStatus INTEGER } -- 17.3.7.1 Recording Configuration ID Parameter recConfigID OBJECT-TYPE SYNTAX Integer32 (1..65534) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the row number which is used to identify the recording associated with this row in the recConfigTable. The number of recording configuration IDs shall not exceed the value indicated in the maxRecConfigs object. NTCIP1201-RecMechV2.recMechV2FactoryName The replacement object is an SnmpAdminString 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.1" ::= { recConfigEntry 1 } -- 17.3.7.2 Recording Configuration Class Parameter recConfigClass OBJECT-TYPE SYNTAX Integer32 (1..254) MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the class value to assign to the recording associated with this row in the recording configuration table. This value is used in the recording table to organize various recordings defined in this table into logical groupings. This value shall not exceed the maxRecClasses object value. NOTE-A recording cannot be recorded if the RecClass has an recClassLimit of zero (0). NTCIP1201-RecMechV2.recMechV2ClassName The replacement object is an index for the table 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.2" DEFVAL {1} ::= { recConfigEntry 2 } -- 17.3.7.3 Recording Configuration Mode Parameter recConfigMode OBJECT-TYPE SYNTAX INTEGER { other (1), onChange (2), greaterThanValue (3), smallerThanValue (4), hysteresisBound (5), periodic (6), andedWithValue (7) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object specifies the mode of operation for this recording. The modes are defined as follows: Value Description other the recording mode of operation is not described in this standard, refer to the device manual. onChange trigger a recording when the object value referenced by recConfigCompareOID changes. The values of recConfigCompareValue and recConfigCompareValue2 are ignored in this mode. greaterThanValue trigger a recording when the object value referenced by recConfigCompareOID becomes greater than the value of recConfigCompareValue for the time (tenth seconds) defined by recConfigCompareValue2 (zero means immediate logging). smallerThanValue trigger a recording when the object value referenced by recConfigCompareOID becomes less than the value of recConfigCompareValue for the time (tenth seconds) defined by recConfigCompareValue2 (zero means immediate logging). hysteresisBound trigger a recording when the object value referenced by recConfigCompareOID becomes less than or greater than the bound values. The lowerbound value is the lower value of recConfigCompareValue and recConfigCompareValue2; the upperbound value is the higher value of the two values. When the object value becomes greater than the upper bound value, subsequent triggering of upperbound conditions shall not occur until the object value becomes less than the lower bound value. When the object value becomes less than the lower bound value, subsequent triggering of lowerbound conditions shall not occur until the object value becomes greater than the upper bound value. periodic trigger a recording every x seconds, where x is defined by the value stored in recConfigCompareValue. The values stored in recConfigCompareValue2 and recConfigCompareOID are ignored in this mode. andedWithValue trigger a recording when the object value referenced by recConfigCompareOID ANDED with the value of recConfigCompareValue is NOT equal to zero for the time (tenth seconds) defined by recConfigCompareValue2 (zero means immediate logging). This allows monitoring of a specific bit; the condition becomes true anytime that any one of the selected bits become true. COND-TRIGGER-MIB.fdCondTriggerMode (ISO 20684-3) The replacement object adds the following modes: equal, notEqual, creation, deletion. It also distinguishes between an integer-based and octet-string-based bitwise comparison, which is required due to the elimination of Opaque. 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.3" DEFVAL { onChange } ::= { recConfigEntry 3 } -- 17.3.7.4 Recording Configuration Compare Value Parameter recConfigCompareValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the comparison value to use with recConfigMode values (greaterThanValue, smallerThanValue, hysteresisBound ). No value within this object is necessary when the recConfigMode-object has the value onChange (2). COND-TRIGGER-MIB.fdCondTriggerValue (ISO 20684-3) The value is a signed, 4-octet integer 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.4" DEFVAL {0} ::= { recConfigEntry 4 } -- 17.3.7.5 Recording Configuration Compare Value 2 Parameter recConfigCompareValue2 OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS deprecated DESCRIPTION "If the recConfigMode is set to hysteresisBound, this object specifies the second comparison value for the hysteresis. If the recConfigMode is set to greaterThanValue, smallerThanValue, or andedWithValue, this object specifies the time (in tenth of seconds, +1 tenth / -0 tenths) for which the samples used for comparison are true prior to the triggering condition becoming true. If the recConfigMode is set to onChange or periodic, the value of this object shall be ignored. The amount of time the condition istrue is measured in tenths of a second. The accuracy of this timer is limited to +1 tenth of a second and:0 tenths of a second. If the trigger is true for at least the time shown in this parameter +1 tenth of a second, the condition shall trigger a recording. It is recognized that some designs only sample the condition periodically, in which case the condition is deemed true for at least the time indicated by this object before the trigger becomes true and the trigger shall always become true if the condition is true for a duration equal to the value shown in this object plus 1 tenth of a second. COND-TRIGGER-MIB.fdCondTriggerValue2 (ISO 20684-3) 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.5" DEFVAL {0} ::= { recConfigEntry 5 } -- 17.3.7.6 Recording Configuration Compare Object Identifier Parameter recConfigCompareOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the object identifier which references the value against which the comparison is made. If the recConfigMode is set to periodic, the value of this object shall be ignored. If the recConfigMode is set to greaterThanValue, smallerThanValue or hysteresisBound, this object is required to reference an object whose SYNTAX resolves to a ranged or unranged INTEGER. As with all other objects that are sub-ranged by a given implementation, an agent should return a badValue error if it receives a set command indicating a OID which is not supported by the implementation or which is not zeroDotZero. COND-TRIGGER-MIB.fdCondTriggerObject (ISO 20684-3) 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.6" DEFVAL { zeroDotZero } ::= { recConfigEntry 6 } -- 17.3.7.7 Recording Configuration Record Object Identifier Parameter recConfigRecordOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object contains the object identifier which indicates what value to record in a recording (e.g., signal states). As with all other objects that are sub-ranged by a given implementation, an agent should return a badValue error if it receives a set command indicating a value which is not supported by the implementation. The valid value range of this object shall not include any values, other than zeroDotZero, that do not correspond to objects that may exist within the agent, although it may be further restricted. The valid value range of this object shall not include objects under the following nodes: Security - { nema transportation devices global security } CHAP - { nema transportation protocols layers chap } NTCIP1201-RecMechV2.recMechV2FactorySampleOID The replacement object does not contrain values other than requiring the user to have rights to access the parameter when configuring and when sampling. 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.7" DEFVAL { zeroDotZero } ::= { recConfigEntry 7 } -- 17.3.7.8 Recording Configuration Trigger Point Parameter recConfigTriggerPoint OBJECT-TYPE SYNTAX Integer32 (0..100) UNITS "percent" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the value of the recording trigger point in percent relative to the recConfigNumEntries. The device needs to collect pre-event records prior to the trigger occurring and ends the recording after recConfigNumEntries have been recorded. A value of zero (0) means to start the recording once the trigger condition occurs whereas a value of 100 means to stop the recording with the last record being the one collected immediately following the trigger condition occurring. If the trigger point is less than 100 then at least one record entry needs to occur after the trigger point. NTCIP1201-RecMechV2.recMechV2FactoryPreSamples 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.8" DEFVAL {80} ::= { recConfigEntry 8 } -- 17.3.7.9 Recording Configuration Sample Period Parameter recConfigSamplePeriod OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "0.1 milliseconds" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the sample period for recordings collected at specified by this configuration. The sample period is expressed in units of 0.1 milliseconds. Allowable sample periods are restricted to a value of zero (0) or (recMinSamplePeriod + recSamplePeriodResolution * n) where n is integer, 0 <= n, and n <= (recMaxSamplePeriod-recMinSamplePeriod)/recSamplePeriodResolution If the value is zero (0), then the samples are not collected on a periodic basis, but rather a new sample is collected whenever the value of the object specified by recConfigSampleOID changes (i.e. similar to event log 'on-change' mode). A set to any other value results in a badValue response. NTCIP1201-RecMechV2.recMechV2FactorySamplePeriod 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.9" DEFVAL {1000} ::= { recConfigEntry 9 } -- 17.3.7.10 Recording Configuration Sample OID Parameter recConfigSampleOID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the object identifier which references the value against which the 'on-change' comparison is made. If recConfigSamplePeriod is non-zero, then the value of this object shall be ignored. As with all other objects that are sub-ranged by a given implementation, an agent should return a badValue error if it receives a set command indicating a OID which is not supported by the implementation or which is not zeroDotZero. NTCIP1201-RecMechV2.recMechV2FactoryMonitorOID 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.10" DEFVAL { zeroDotZero } ::= { recConfigEntry 10 } -- 17.3.7.11 Recording Configuration Number Entries Parameter recConfigNumEntries OBJECT-TYPE SYNTAX Integer32 (0..4095) UNITS "records" MAX-ACCESS read-write STATUS deprecated DESCRIPTION " This object contains the maximum number of records in a recording defined by this configuration. A recording which collects its full amount of pre-events and post events creates a recording of this number of entries. If this object is zero (0), then no recordings are created based on this configuration. Note: If one wants to use block objects to retrieve a recording, then one should consider that block starting index value is limited to the range 00..255, and the number of entries above 255 is dependent on the size of the recEntry and packet size limitations. NTCIP1201-RecMechV2.recMechV2FactorySampleLimit The replacement object has a syntax of ITSUnsigned16. 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.11" DEFVAL {100} ::= { recConfigEntry 11 } -- 17.3.7.12 Recording Configuration Action Parameter recConfigAction OBJECT-TYPE SYNTAX INTEGER { other (1), disabled (2), record (3) } MAX-ACCESS read-write STATUS deprecated DESCRIPTION "The value of this object indicates what action shall take place when this configuration is triggered. other - indicates that the action is other than defined in this standard. disabled - no recording is created due to this configuration. record - a recording is created in the recording table when this configuration is triggered. NTCIP1201-RecMechV2.recMechV2FactoryRowStatus The replacement table is dynamic. 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.12" DEFVAL {disabled} ::= { recConfigEntry 12 } -- 17.3.7.13 Recording Configuration Status Parameter recConfigStatus OBJECT-TYPE SYNTAX INTEGER { other (1), disabled (2), record (3), error (4) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The value of this object indicates the current status of the configured recording. Upon setting any object in this row of the recConfigTable, the agent determines if the setting is valid, and sets this object to one of the following states: other indicates that the action is successfully set to a mode other than that defined in this standard disabled indicates that the action is set to disabled record indicates that the action is successfully set to the record state after passing consistency checks. error indicates that the requested action could not be implemented due to a consistency check NTCIP1201-RecMechV2.recMechV2FactoryRowStatus The replacement table is dynamic. 1.3.6.1.4.1.1206.4.1.1.7.9.7.1.13" ::= { recConfigEntry 13 } -- 17.3.8 Maximum Recordings Parameter maxRecordings OBJECT-TYPE SYNTAX Integer32 (1..65534) UNITS "records" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The maximum, fixed number of rows that can be used within the recRecordingTable. The replacement for recRecordingTable is not associated with an explicit row limitation just a size limitation given by recMechV2ClassTableSizeLimit and adminRecMechSizeLimit. 1.3.6.1.4.1.1206.4.1.1.7.9.8" ::= { recMech 8} -- 17.3.9 Recording Table recRecordingTable OBJECT-TYPE SYNTAX SEQUENCE OF RecRecordingEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing information about Recordings both completed and in process. A request for an object from a row that has not been instantiated or has been cleared shall return a noSuchName error. dynamic NTCIP1201-RecMechV2.recMechV2RecordingTable 1.3.6.1.4.1.1206.4.1.1.7.9.9" ::= { recMech 9 } recRecordingEntry OBJECT-TYPE SYNTAX RecRecordingEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines an entry in the recording table NTCIP1201-RecMechV2.recMechV2RecordingEntry The index for the replacement table has a preceding owner column. It also has a delete column that allows for the deletion of the recording, including all of its samples. 1.3.6.1.4.1.1206.4.1.1.7.9.9.1" INDEX { recordingClass, recordingNumber } ::= { recRecordingTable 1 } RecRecordingEntry::= SEQUENCE { recordingClass Integer32, recordingNumber Integer32, recordingID Integer32, recordingConfigID Integer32, recordingTriggerTime OCTET STRING, recordingStatus INTEGER, recordingTriggerRecNum Integer32, recordingNumEntries Integer32 } -- 17.3.9.1 Recording Class Parameter recordingClass OBJECT-TYPE SYNTAX Integer32 (1..254) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the class of the associated recording as defined in the recConfigTable. NTCIP1201-RecMechV2.recMechV2ClassName The syntax of the replacement object is SnmpAdminString. 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.1" ::= { recRecordingEntry 1 } -- 17.3.9.2 Recording Number Parameter recordingNumber OBJECT-TYPE SYNTAX Integer32 (1..254) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The recording number within this class for this recording. Recording numbers shall be assigned starting at 1 and shall increase to the value specified by the associated recClassLimit for the class associated with the rows. Recordings shall maintain a chronological ordering in the table, based on their recordingTriggerTime value, with the oldest recording of a class occupying the row with recordingNumber = 1, and subsequent recordings filling subsequent rows. This ordering shall be maintained for those rows still remaining when recordings are cleared. NTCIP1201-RecMechV2.recMechV2RecordingIndex The syntax of the replacement object is ITSPositive16. The replacement table does not attempt to keep the oldest entry in slot one; clearance of rows is based on overall size rather than number of entries, which makes this type of row management more difficult - but since row numbers do not change, managers can keep track of the last row number retrieved and decrease the probability of missing a recording. A manager can also use a get-next operation to discover where the rows start in the table. 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.2" ::= { recRecordingEntry 2 } -- 17.3.9.3 Recording ID Parameter recordingID OBJECT-TYPE SYNTAX Integer32 (1..65534) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the recording ID that is used as an index into recording entries table (recEntriesTable) when accessing record entries that belong to this recording. The recording ID is assigned to a recording upon creation of its first record entry and does not change throughout the life of the recording. The recording IDs are not necessarily assigned sequentially. The replacement for the recEntriesTable uses the four indices owner, class name, recording ID, and sample number rather than using a single identifier to join class name and recording. 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.3" ::= { recRecordingEntry 3 } -- 17.3.9.4 Recording Configuration ID Parameter recordingConfigID OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the recording configuration ID (from the recConfigTable) that caused this table entry. It indicates the row in the recConfig table responsible for this recording entry. NTCIP1201-RecMechV2.recMechV2RecordingTrigger The syntax of the replacement object is SnmpAdminString. 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.4" ::= { recRecordingEntry 4 } -- 17.3.9.5 Recording Trigger Time Parameter recordingTriggerTime OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS deprecated DESCRIPTION " The time that the recording was triggered at. This object consists of a string of six (6) octets. The first four (4) octets reflect the value of globalTime when the recording was triggered. The last two (2) octets reflect the time in milliseconds the trigger occurred after the start of the second. The recording shall be detected and timestamped within one recSamplePeriodResolution unit of time from the recording being triggered. NTCIP1201-RecMechV2.recMechV2RecordingDate & recMechV2RecordingTime The replacement objects conform to the new date/time formats. 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.5" ::= { recRecordingEntry 5 } -- 17.3.9.6 Recording Status Parameter recordingStatus OBJECT-TYPE SYNTAX INTEGER { available (1), preevent (2), triggered (3), complete (4) } MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The value of this object reflects the state of the recording located in this row. Value Description available this row is available for a new recording to be initiated for this recording class. When a recording is cleared, the value is set to available preevent the recording defined by recConfigID is collecting pre-event record entries. Note: If the trigger point is set to zero (0) percent or the trigger condition is already satisfied when the recConfigID is configured, then the value transitions straight from available to triggered. triggered the recording defined by recConfigID has triggered and is now collecting post event records. If the trigger point was set to 100 percent, then the value transitions straight from preevent to complete. If a recording was triggered and the device experienced a power failure, then upon power restoration it shall change the value to complete. Triggered recordings shall survive a power outage. complete the recording defined by recConfigID is now complete (i.e. collected all of its post events) and ready for retrieval. Completed recordings shall survive a power outage. NTCIP1201-RecMechV2.recMechV2RecordingStatus 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.6" ::= { recRecordingEntry 6 } -- 17.3.9.7 Recording Trigger Record Number Parameter recordingTriggerRecNum OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "This object contains the record entry number of the trigger record entry. A value of zero (0) means that the recording has not triggered yet. NTCIP1201-RecMechV2.recMechV2RecordingTriggerSample 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.7" ::= { recRecordingEntry 7 } -- 17.3.9.8 Number of Entries in Recording Parameter recordingNumEntries OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "entries" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The current number of recording entries in this recording. A value of zero (0) is only valid if the recording is available for use. Note: A completed recording does not always have recConfigNumEntries record entries in it. NTCIP1201-RecMechV2.recMechV2RecordingNumSamples 1.3.6.1.4.1.1206.4.1.1.7.9.9.1.8" ::= { recRecordingEntry 8 } -- 17.3.10 Maximum Recording Entries Parameter maxRecEntries OBJECT-TYPE SYNTAX Integer32 (1..65535) UNITS "records" MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The maximum, fixed number of rows that can be used within the recEntriesTable. The replacement for recEntriesTable is not associated with an explicit row limitation just a size limitation given by recMechV2ClassTableSizeLimit and adminRecMechSizeLimit. 1.3.6.1.4.1.1206.4.1.1.7.9.10" ::= { recMech 10} -- 17.3.11 Recording EntriesTable recEntriesTable OBJECT-TYPE SYNTAX SEQUENCE OF RecEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "A table containing the discrete Recording entry records. A request for an object from a row that has not been instantiated or has been cleared shall return a noSuchName error. dynamic NTCIP1201-RecMechV2.recMechV2SampleTable 1.3.6.1.4.1.1206.4.1.1.7.9.11" ::= { recMech 11 } recEntry OBJECT-TYPE SYNTAX RecEntry MAX-ACCESS not-accessible STATUS deprecated DESCRIPTION "This object defines an entry in the recording entry table. All entries within a recording shall be ordered chronologically from oldest to newest. NTCIP1201-RecMechV2.recMechV2SampleEntry The index for the replacement table uses four fields: owner, class, recording, and sample. 1.3.6.1.4.1.1206.4.1.1.7.9.11.1" INDEX { recordingID, recEntryNumber } ::= { recEntriesTable 1 } RecEntry::= SEQUENCE { recEntryNumber Integer32, recSampleTime OCTET STRING, recValue Opaque } -- 17.3.11.1 Record Entry Number Parameter recEntryNumber OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The entry number within this recording for this record. Entry numbers shall be assigned starting at 1 and shall increase up to the value specified by the associated recConfigNumEntries. A value of zero indicates that the row is unused (cleared). NTCIP1201-RecMechV2.recMechV2SampleNum 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.1" ::= { recEntry 1 } -- 17.3.11.2 Record Entry Sample Time Parameter recSampleTime OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The time that the record entry was sampled at. This object consists of a string of six (6) octets. The first four (4) octets reflect the value of controllerLocalTime when the entry was sampled. The last two (2) octets reflect the time in milliseconds the sample occurred after the start of the second. The entry shall be collected within one recSamplePeriodResolution unit of time from the sample being triggered and timestamped with the time of collection NTCIP1201-RecMechV2.recMechV2SampleTime The syntax for the replacement object is ITSDailyTimeStamp, which does not provide the date. However, the date is provided in the Trigger time. Assuming the sample period is relatively short, this should not cause a problem. For recordings with many samples and/or long sample intervals, the date can be calculated - with the one exception of on change sampling for rare events. owner, class, recording, and sample. 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.2" ::= { recEntry 2 } -- 17.3.11.3 Record Entry Value Parameter recValue OBJECT-TYPE SYNTAX Opaque MAX-ACCESS read-only STATUS deprecated DESCRIPTION "The value of this object is set to the BER encoding of the value referenced by the recConfigRecordOID of the associated recordingConfigID when the entry was collected. Its length is variable. The value shall not contain any padding characters either before or after the values. NOTE: Opaque objects are doubly wrapped. For SNMP operations, which use BER, this would be {type, length, {type, length, value}}. For example, a zero-length octet string, would be encoded in BER as 0x44 02 04 00. For STMP or SFMP operations, which use OER, this would be { length, {type, length, value}}. For example, the same example would be encoded in OER as 0x02 04 00. NTCIP1201-RecMechV2.recMechV2SampleValue The syntax of the replacement object is ITSOerString. 1.3.6.1.4.1.1206.4.1.1.7.9.11.1.3" ::= { recEntry 3 } -- 17.3.12 Total Recordings Counter Parameter numRecordings OBJECT-TYPE SYNTAX Integer32 (0..65535) UNITS "recordings" MAX-ACCESS read-only STATUS deprecated DESCRIPTION " This object is a counter that gets incremented every time a recording is completed and shall initialize to zero at power up. The value shall roll over each time it exceeds the maximum of 65535. NTCIP1201-RecMechV2.recMechV2OwnerRecordingCtr & adminRecMechV2RecordingCtr The syntax of the replacement objects is ZeroBasedCounter32. 1.3.6.1.4.1.1206.4.1.1.7.9.12" ::= { recMech 12 } -- 17.3.13 Clear Recording Classes recClearClasses OBJECT-TYPE SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to clear a recording class from recClassTable. A SET of zero has no effect on any recording classes. A SET = n, n <= maxRecClasses, shall cause recClassNumber = n to be deleted from the recClassTable and all related recording configurations, their recordings, their recording entries, their recording activities shall be deleted from the recConfigTable, recRecordingTable, and recEntriesTable respectively. A SET of 255 shall cause all entries in the recClassTable, recConfigTable, recRecordingTable, and recEntriesTable to be deleted. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). NTCIP1201-RecMechV2.recMechV2ClassRowStatus, recMechV2OwnerClearAllClasses, & adminRecMechClearAllClasses 1.3.6.1.4.1.1206.4.1.1.7.9.13" ::= { recMech 13 } -- 17.3.14 Clear Recording Configurations recClearConfigurations OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to clear a recording configuration from the recConfigTable. A SET of zero has no effect on any recording configurations. A SET = n, n <= maxRecConfigs, shall cause recConfigID = n to be deleted from the recRecordingTable and all related recordings, their recording entries, and their recording activities shall be deleted from the recRecordingTable and recEntriesTable respectively. A SET of n = 65535 shall cause all entries in the recConfigTable, recRecordingTable, and recEntriesTable to be deleted. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). NTCIP1201-RecMechV2.recMechV2FactoryRowStatus, recMechV2OwnerClearAllFactories, adminRecMechClearAllFactories, COND_NOTIFICATIONS-MIB.fdCondTriggerRowStatus (ISO 20684-3) There is not a clear all for the conditional trigger. 1.3.6.1.4.1.1206.4.1.1.7.9.14" ::= { recMech 14 } -- 17.3.15 Clear Recording Data recClearRecordingData OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-write STATUS deprecated DESCRIPTION "This object commands the device to clear a recording from the recRecordingTable and recEntriesTable. A SET of zero has no effect on any recordings. A SET = n, n <= maxRecordings, shall cause recRecordingID = n to be deleted from the recRecordingTable and all record entries related to the recording to be deleted from recEntriesTable. A SET of n = 65535 shall cause all entries in both the recRecordingTable and recEntriesTable to be deleted. Note: a device shall immediately start collecting new pre-event records for all active recording configurations. Upon performing the action requested, the device shall SET this object to zero (0). A GET shall always return zero (0). NTCIP1201-RecMechV2.recMechV2RecordingDelete, recMechV2OwnerClearAllRecordings, & adminRecMechClearAllRecordings 1.3.6.1.4.1.1206.4.1.1.7.9.15" ::= { recMech 15 } -- 17.4 COMPLIANCE GROUPS -- 17.4.1 Watch Block Group recMechGroupR1 OBJECT-GROUP OBJECTS { maxRecClasses, recClassNumber, recClassLimit, recClassClearTime, recClassDescription, recClassNumRecordings, recClassRecordingCounter, maxRecConfigs, recMinSamplePeriod, recMaxSamplePeriod, recSamplePeriodResolution, recConfigID, recConfigClass, recConfigMode, recConfigCompareValue, recConfigCompareValue2, recConfigCompareOID, recConfigRecordOID, recConfigTriggerPoint, recConfigSamplePeriod, recConfigSampleOID, recConfigNumEntries, recConfigAction, recConfigStatus, maxRecordings, recordingClass, recordingNumber, recordingID, recordingConfigID, recordingTriggerTime, recordingStatus, recordingTriggerRecNum, recordingNumEntries, maxRecEntries, recEntryNumber, recSampleTime, recValue, numRecordings, recClearClasses, recClearConfigurations, recClearRecordingData } STATUS deprecated DESCRIPTION " The objects necessary for managing the high-resolution data recording mechanism. 1.3.6.1.4.1.1206.4.1.1.7.9.127.2.1" ::= {recMechGroups 1} END -- NTCIP1201-RechMech