<Definition> A bitmap of summary errors. When a bit is set, the error is presently active. When a bit is clear the error is not currently active. If no sensor is present or supported (for a corresponding bit), the bit shall not be set. <Format> The bits are defined as follows: Bit 0- other - not defined by this standard, see the value of dmsOtherShortErrorDescr. The value of other was deprecated in v02 and reinstated in v04. Bit 1- communications error - this bit shall be set if any error associated with the communications between the central computer and the device occurs. Bit 2- power error - this bit shall be set if any error is detected for any power supply associated with any component (i.e., any bit set in fdSrsaTypeWarning.FPA, FPS, or FPV) or if the generator fuel level is below its minimum threshold or has an error (i.e., any bit set in fdSrsaTypeWarning.FGF). Bit 3- attached device error - this bit shall be set if any error associated with attached (supported, and enabled) external devices occurs (i.e., any bit set in any fdSrsaTypeWarning object that is not otherwise specified by other bots of this object). Bit 4- lamp error - this bit shall be set if any errors associated with any lamp occurs (i.e., any bit set in fdSrsaTypeWarning.MLS) This bit is only applicable to devices that support lamps such as fiber optic signs or front-illuminated reflective signs. This bit is not applicable to lamps or fluorescent lights illuminating the housing or cabinet. Bit 5- pixel error - this bit shall be set if any errors associated with any pixel occurs (see the objects pixelFailureTableNumRows for NTCIP 1203 v01 deployments, and pixelFailureTableNumRows, and/or dmsPixelFailureTestRows and dmsPixelFailureMessageRows for NTCIP 1203 v02 deployments.). This bit is only applicable to devices that support illumination of individual pixels, but not to drum signs. Note that certain sign technologies such as flip disk only sign may not be able to determine pixel errors. Bit 6- photocell error - this bit shall be set if any errors associated with the supported light sensors occurs (i.e., any bit set in fdSrsaTypeWarning.FAL). Bit 7- message error - this bit shall be set if any errors associated with activating and/or displaying a message occurs (see the object dmsActivateMsgError). Bit 8- controller error - this bit shall be set if any errors associated with the controller occurs (i.e., any bit set in fdControllerStatus). Bit 9- temperature warning - this bit shall be set if any of the temperature values detected by the device exceed non-standardized temperature values (i.e., any bit set in fdSrsaTypeWarning.FAT FET, or FPT). This bit is included to allow vendors or agencies to define vendor- or agency-specific threshold objects that indicate temperature changes that are of interest but not dangerous to the life-expectancy of the device (see also the 'critical temperature' bit) Bit 10- climate-control system error - this bit shall be set if any errors associated with the climate control systems such as fans and/or heaters occurs (i.e., any bit set in fdSrsaTypeWarning.FAC, FDC, FFO, FHO, or FTT). Bit 11- critical temperature error - this bit shall be set if the critical temperature as defined by the value of the critical temperature objects have been exceeded (i.e., any bit set in fdSrsaTypeStatus.FAT, FET, or FPT). Bit 12- Drum-sign Rotor error - This bit shall be set if any errors associated with the rotor of a drum sign occurs (i.e., any bit set in fdSrsaTypeWarning.MDS). Bit 13- This bit shall be set if any door to any DMS field component (cabinet or housing) is open (i.e., any bit set in fdSrsaTypeWarning.FDO). Bit 14- Humidity warning - This bit shall be set if any humidity sensor sensor is reporting a humidity warning (i.e., any bit set in fdSrsaTypeWarning.FAH or FEH). Bit 15- invisible default text - this bit shall be set if the value for defaultBackgroudRGB is equal to the value of defaultForegroundRGB, which would result in the message not being visible unless the MULTI string itself specifies alternate colors. <Informative> To track a history of transient error conditions utilize the event logging table located in the Global Objects Definitions (NTCIP 1201). <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.1
OID reference
shortErrorStatus
1.3.6.1.4.1.1206.4.2.6.9.7.1
Description
<Definition> A bitmap of summary errors. When a bit is set, the error is presently active. When a bit is clear the error is not currently active. If no sensor is present or supported (for a corresponding bit), the bit shall not be set. <Format> The bits are defined as follows: Bit 0- other - not defined by this standa…
Identification
Identifier and names
- Parent
- 1.3.6.1.4.1.1206.4.2.6.9.7 (statError)
- Node code
- 1
- Node name
- shortErrorStatus
- Category
- SNMP management object
- Numeric OID
- 1.3.6.1.4.1.1206.4.2.6.9.7.1
- URN notation
- urn:oid:1.3.6.1.4.1.1206.4.2.6.9.7.1
ASN.1, OID-IRI and named path variants
- ASN.1 notation
-
{1 3 6 1 4 1 1206 4 2 6 9 7 1}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) global(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) globalV2(9) statError(7) shortErrorStatus(1)}
- {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) dms(6) dmsStatus(9) statError(7) shortErrorStatus(1)}
- Additional combinations skipped.
- OID-IRI notation
- /1/3/6/1/4/1/1206/4/2/6/9/7/1
- /ISO/Identified-Organization/6/1/4/1/1206/4/2/6/9/7/1
- /ISO/3/6/1/4/1/1206/4/2/6/9/7/1
- Named path variants
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/global/dmsStatus/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/dms/dmsStatus/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/global/dmsStatus/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/dms/dmsStatus/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/global/dmsStatus/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/dms/dmsStatus/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/global/dmsStatus/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/globalV2/statError/shortErrorStatus
- /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/dms/dmsStatus/statError/shortErrorStatus
- Additional combinations skipped.
SNMP properties
- Value type
- NtcipIntegerBitmap16
- Maximum access defined by MIB
- read-only
- Status in MIB
- current
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Published definition
The displayed source records contain one distinct definition. Compare its source records.
shortErrorStatus OBJECT-TYPE
SYNTAX NtcipIntegerBitmap16
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"<Definition> A bitmap of summary errors. When a bit is set, the error is
presently active. When a bit is clear the error is not currently active. If
no sensor is present or supported (for a corresponding bit), the bit
shall not be set.
<Format> The bits are defined as follows:
Bit 0- other - not defined by this standard, see the value of
dmsOtherShortErrorDescr.
The value of other was deprecated in v02 and reinstated in v04.
Bit 1- communications error - this bit shall be set if any error
associated with the communications between the central
computer and the device occurs.
Bit 2- power error - this bit shall be set if any error is detected for any
power supply associated with any component (i.e., any bit set in
fdSrsaTypeWarning.FPA, FPS, or FPV) or if the generator fuel
level is below its minimum threshold or has an error
(i.e., any bit set in fdSrsaTypeWarning.FGF).
Bit 3- attached device error - this bit shall be set if any error
associated with attached (supported, and enabled) external
devices occurs (i.e., any bit set in any fdSrsaTypeWarning object
that is not otherwise specified by other bots of this object).
Bit 4- lamp error - this bit shall be set if any errors associated with any
lamp occurs (i.e., any bit set in fdSrsaTypeWarning.MLS) This bit
is only applicable to devices that support lamps such as fiber optic
signs or front-illuminated reflective signs. This bit is not applicable
to lamps or fluorescent lights illuminating the housing or cabinet.
Bit 5- pixel error - this bit shall be set if any errors associated with any
pixel occurs (see the objects pixelFailureTableNumRows for NTCIP 1203
v01 deployments, and pixelFailureTableNumRows, and/or
dmsPixelFailureTestRows and dmsPixelFailureMessageRows for NTCIP 1203
v02 deployments.).
This bit is only applicable to devices that support illumination of
individual pixels, but not to drum signs.
Note that certain sign technologies such as flip disk only sign may
not be able to determine pixel errors.
Bit 6- photocell error - this bit shall be set if any errors associated with
the supported light sensors occurs (i.e., any bit set in
fdSrsaTypeWarning.FAL).
Bit 7- message error - this bit shall be set if any errors associated with
activating and/or displaying a message occurs (see the object
dmsActivateMsgError).
Bit 8- controller error - this bit shall be set if any errors associated
with the controller occurs (i.e., any bit set in fdControllerStatus).
Bit 9- temperature warning - this bit shall be set if any of the
temperature values detected by the device exceed
non-standardized temperature values (i.e., any bit set in
fdSrsaTypeWarning.FAT FET, or FPT). This bit is included to allow
vendors or agencies to define vendor- or agency-specific
threshold objects that indicate temperature changes that are of
interest but not dangerous to the life-expectancy of the device
(see also the 'critical temperature' bit)
Bit 10- climate-control system error - this bit shall be set if any errors
associated with the climate control systems such as fans and/or
heaters occurs (i.e., any bit set in fdSrsaTypeWarning.FAC, FDC,
FFO, FHO, or FTT).
Bit 11- critical temperature error - this bit shall be set if the critical
temperature as defined by the value of the critical temperature
objects have been exceeded (i.e., any bit set in
fdSrsaTypeStatus.FAT, FET, or FPT).
Bit 12- Drum-sign Rotor error - This bit shall be set if any errors
associated with the rotor of a drum sign occurs (i.e., any bit set in
fdSrsaTypeWarning.MDS).
Bit 13- This bit shall be set if any door to any DMS field component
(cabinet or housing) is open (i.e., any bit set in
fdSrsaTypeWarning.FDO).
Bit 14- Humidity warning - This bit shall be set if any humidity sensor
sensor is reporting a humidity warning (i.e., any bit set in
fdSrsaTypeWarning.FAH or FEH).
Bit 15- invisible default text - this bit shall be set if the value for
defaultBackgroudRGB is equal to the value of defaultForegroundRGB, which
would result in the message not being visible unless the MULTI string itself
specifies alternate colors.
<Informative> To track a history of transient error conditions utilize the
event logging table located in the Global Objects Definitions (NTCIP 1201).
<Parameter Type> Status
<Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.1"
::= { statError 1 }
Meaning
Descriptions
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Evidence
Source records
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Records for description 1ITE public NTCIP working repository MIBs
shortErrorStatus · unconfirmedITE public NTCIP working repository MIBs
Status in source: unconfirmed.
Names: shortErrorStatus
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"shortErrorStatus",
"OBJECT-TYPE",
"SYNTAX",
"NtcipIntegerBitmap16",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"<Definition> A bitmap of summary errors. When a bit is set, the error is presently active. When a bit is clear the error is not currently active. If no sensor is present or supported (for a corresponding bit), the bit shall not be set. <Format> The bits are defined as follows: Bit 0- other - not defined by this standard, see the value of dmsOtherShortErrorDescr. The value of other was deprecated in v02 and reinstated in v04. Bit 1- communications error - this bit shall be set if any error associated with the communications between the central computer and the device occurs. Bit 2- power error - this bit shall be set if any error is detected for any power supply associated with any component (i.e., any bit set in fdSrsaTypeWarning.FPA, FPS, or FPV) or if the generator fuel level is below its minimum threshold or has an error (i.e., any bit set in fdSrsaTypeWarning.FGF). Bit 3- attached device error - this bit shall be set if any error associated with attached (supported, and enabled) external devices occurs (i.e., any bit set in any fdSrsaTypeWarning object that is not otherwise specified by other bots of this object). Bit 4- lamp error - this bit shall be set if any errors associated with any lamp occurs (i.e., any bit set in fdSrsaTypeWarning.MLS) This bit is only applicable to devices that support lamps such as fiber optic signs or front-illuminated reflective signs. This bit is not applicable to lamps or fluorescent lights illuminating the housing or cabinet. Bit 5- pixel error - this bit shall be set if any errors associated with any pixel occurs (see the objects pixelFailureTableNumRows for NTCIP 1203 v01 deployments, and pixelFailureTableNumRows, and/or dmsPixelFailureTestRows and dmsPixelFailureMessageRows for NTCIP 1203 v02 deployments.). This bit is only applicable to devices that support illumination of individual pixels, but not to drum signs. Note that certain sign technologies such as flip disk only sign may not be able to determine pixel errors. Bit 6- photocell error - this bit shall be set if any errors associated with the supported light sensors occurs (i.e., any bit set in fdSrsaTypeWarning.FAL). Bit 7- message error - this bit shall be set if any errors associated with activating and/or displaying a message occurs (see the object dmsActivateMsgError). Bit 8- controller error - this bit shall be set if any errors associated with the controller occurs (i.e., any bit set in fdControllerStatus). Bit 9- temperature warning - this bit shall be set if any of the temperature values detected by the device exceed non-standardized temperature values (i.e., any bit set in fdSrsaTypeWarning.FAT FET, or FPT). This bit is included to allow vendors or agencies to define vendor- or agency-specific threshold objects that indicate temperature changes that are of interest but not dangerous to the life-expectancy of the device (see also the 'critical temperature' bit) Bit 10- climate-control system error - this bit shall be set if any errors associated with the climate control systems such as fans and/or heaters occurs (i.e., any bit set in fdSrsaTypeWarning.FAC, FDC, FFO, FHO, or FTT). Bit 11- critical temperature error - this bit shall be set if the critical temperature as defined by the value of the critical temperature objects have been exceeded (i.e., any bit set in fdSrsaTypeStatus.FAT, FET, or FPT). Bit 12- Drum-sign Rotor error - This bit shall be set if any errors associated with the rotor of a drum sign occurs (i.e., any bit set in fdSrsaTypeWarning.MDS). Bit 13- This bit shall be set if any door to any DMS field component (cabinet or housing) is open (i.e., any bit set in fdSrsaTypeWarning.FDO). Bit 14- Humidity warning - This bit shall be set if any humidity sensor sensor is reporting a humidity warning (i.e., any bit set in fdSrsaTypeWarning.FAH or FEH). Bit 15- invisible default text - this bit shall be set if the value for defaultBackgroudRGB is equal to the value of defaultForegroundRGB, which would result in the message not being visible unless the MULTI string itself specifies alternate colors. <Informative> To track a history of transient error conditions utilize the event logging table located in the Global Objects Definitions (NTCIP 1201). <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.1\"",
"::=",
"{",
"statError",
"1",
"}"
],
"syntax_tree": [
[
"row",
"NtcipIntegerBitmap16"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"<Definition> A bitmap of summary errors. When a bit is set, the error is presently active. When a bit is clear the error is not currently active. If no sensor is present or supported (for a corresponding bit), the bit shall not be set. <Format> The bits are defined as follows: Bit 0- other - not defined by this standard, see the value of dmsOtherShortErrorDescr. The value of other was deprecated in v02 and reinstated in v04. Bit 1- communications error - this bit shall be set if any error associated with the communications between the central computer and the device occurs. Bit 2- power error - this bit shall be set if any error is detected for any power supply associated with any component (i.e., any bit set in fdSrsaTypeWarning.FPA, FPS, or FPV) or if the generator fuel level is below its minimum threshold or has an error (i.e., any bit set in fdSrsaTypeWarning.FGF). Bit 3- attached device error - this bit shall be set if any error associated with attached (supported, and enabled) external devices occurs (i.e., any bit set in any fdSrsaTypeWarning object that is not otherwise specified by other bots of this object). Bit 4- lamp error - this bit shall be set if any errors associated with any lamp occurs (i.e., any bit set in fdSrsaTypeWarning.MLS) This bit is only applicable to devices that support lamps such as fiber optic signs or front-illuminated reflective signs. This bit is not applicable to lamps or fluorescent lights illuminating the housing or cabinet. Bit 5- pixel error - this bit shall be set if any errors associated with any pixel occurs (see the objects pixelFailureTableNumRows for NTCIP 1203 v01 deployments, and pixelFailureTableNumRows, and/or dmsPixelFailureTestRows and dmsPixelFailureMessageRows for NTCIP 1203 v02 deployments.). This bit is only applicable to devices that support illumination of individual pixels, but not to drum signs. Note that certain sign technologies such as flip disk only sign may not be able to determine pixel errors. Bit 6- photocell error - this bit shall be set if any errors associated with the supported light sensors occurs (i.e., any bit set in fdSrsaTypeWarning.FAL). Bit 7- message error - this bit shall be set if any errors associated with activating and/or displaying a message occurs (see the object dmsActivateMsgError). Bit 8- controller error - this bit shall be set if any errors associated with the controller occurs (i.e., any bit set in fdControllerStatus). Bit 9- temperature warning - this bit shall be set if any of the temperature values detected by the device exceed non-standardized temperature values (i.e., any bit set in fdSrsaTypeWarning.FAT FET, or FPT). This bit is included to allow vendors or agencies to define vendor- or agency-specific threshold objects that indicate temperature changes that are of interest but not dangerous to the life-expectancy of the device (see also the 'critical temperature' bit) Bit 10- climate-control system error - this bit shall be set if any errors associated with the climate control systems such as fans and/or heaters occurs (i.e., any bit set in fdSrsaTypeWarning.FAC, FDC, FFO, FHO, or FTT). Bit 11- critical temperature error - this bit shall be set if the critical temperature as defined by the value of the critical temperature objects have been exceeded (i.e., any bit set in fdSrsaTypeStatus.FAT, FET, or FPT). Bit 12- Drum-sign Rotor error - This bit shall be set if any errors associated with the rotor of a drum sign occurs (i.e., any bit set in fdSrsaTypeWarning.MDS). Bit 13- This bit shall be set if any door to any DMS field component (cabinet or housing) is open (i.e., any bit set in fdSrsaTypeWarning.FDO). Bit 14- Humidity warning - This bit shall be set if any humidity sensor sensor is reporting a humidity warning (i.e., any bit set in fdSrsaTypeWarning.FAH or FEH). Bit 15- invisible default text - this bit shall be set if the value for defaultBackgroudRGB is equal to the value of defaultForegroundRGB, which would result in the message not being visible unless the MULTI string itself specifies alternate colors. <Informative> To track a history of transient error conditions utilize the event logging table located in the Global Objects Definitions (NTCIP 1201). <Parameter Type> Status <Object Identifier> 1.3.6.1.4.1.1206.4.2.3.9.7.1"
],
null,
null,
null,
null
]
}- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1203 — NTCIP1203-Dms.mib
Module: NTCIP1203-Dms
See published definition above
Module imports
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'DisplayString', 'StorageType', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'Counter32', 'IpAddress'], 'SNMPv2-CONF': ['OBJECT-GROUP'], 'ISO26048-1-Srsa': ['fdSrsaTypeCode', 'fdSrsaPortIndex'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString'], 'ISO26048-1-Global-TC': ['ITSDirection', 'ITSInteger8', 'ITSLatitude84', 'ITSLongitude84', 'ITSBitmap'], 'TRANSPORT-ADDRESS-MIB': ['TransportAddressType', 'TransportAddress'], 'NTCIP8004-Transportation': ['NtcipOwnerString', 'NtcipIntegerBitmap8', 'NtcipIntegerBitmap16', 'NtcipTwoColors', 'devices']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
Source data warning: Published module-root disagreement: dms has an SMI assignment resolving to 1.3.6.1.4.1.1206.4.2.6, while its DESCRIPTION explicitly prints 1.3.6.1.4.1.1206.4.2.3. All dependent assignments from this module require verification. No root number has been silently corrected.
Source data warning: Published source disagreement: this literal SMI assignment resolves to 1.3.6.1.4.1.1206.4.2.6.9.7.1, but its DESCRIPTION explicitly lists 1.3.6.1.4.1.1206.4.2.3.9.7.1. Both published numeric claims are retained as unconfirmed evidence. Neither value is presented as a verified correction or an independently confirmed registration; consult the original file and the applicable standard edition.
· Download NTCIP-1203 — NTCIP1203-Dms.mib
Registration