SAMSUNG-GENERAL-TC

File: SAMSUNG-GENERAL-TC.mib (61198 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SAMSUNG-COMMON-MIB

Imported symbols

MODULE-IDENTITY OBJECT-IDENTITY OBJECT-TYPE
Counter32 Gauge32 Integer32
TEXTUAL-CONVENTION samsungCommonMIB

Defined Types

Cardinal16  
The representation for non-negative integers. Used for indices in small tables where 0 means not specified. It avoids use of the sign bit.
TEXTUAL-CONVENTION    
  INTEGER 0..32767  

Cardinal32  
The representation for non-negative integers. Used for indices in large tables where 0 means not specified. Same size as ISO 10175 (avoids use of sign bit).
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Cardinal64High  
The high-order 31 bits of a 62-bit non-negative integer (0..2**62-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Cardinal64Low  
The low-order 31 bits of a 62-bit non-negative integer (0..2**62-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

CodedCountry  
A two character country or territory abbreviation from ISO/IEC 3166:1993 - Codes for the Representation of Names of Countries. Examples: US, FR, DE A null string SHALL indicate that the country or territory is not defined.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..2)  

CodedLanguage  
A two character language abbreviation as defined in ISO/IEC 639:1988 - Codes For the Representation of Names of Languages. Examples EN, GB, CA, FR, DE. An empty string SHALL indicate that the language is not defined.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..2)  

CodeIndexedStringIndex  
The representation of string data which the agent can provide in one or more character sets (but not further localized). Typically this representation is used because the string data is relatively dynamic, changing too rapidly for full localization; or because the data exists inherently in only one or a limited number of character sets and cannot meaningfully be further localized. The value is an index into a single global string table, scmGenCodeIndexedStringTable. A subsidiary index into the scmGenCodeIndexedStringTable is the IANA registered enum (see the CodedCharSet textual-convention in RFC 1759) for the coded character set desired by the management station (from among the coded character sets supported by the SNMP agent). A 0 index value SHALL indicate that there is no associated entry in the string table. 32 bits are needed because Jobs can use up 10-12 code-indexed strings per job.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Counter64High  
The high-order 32 bits of a 63-bit counter (0..2**63-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  Counter32  

Counter64Low  
The low-order 31 bits of a 63-bit counter (0..2**63-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Gauge64High  
The high-order 32 bits of a 63-bit gauge (0..2**63-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  Gauge32  

Gauge64Low  
The low-order 31 bits of a 63-bit gauge (0..2**63-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Integer64High  
The high-order 32 bits of a 63-bit signed integer (-2**62..2**62-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  Integer32  

Integer64Low  
The low-order 31 bits of a 63-bit signed integer (-2**62..2**62-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Ordinal16  
The representation for positive integers. Used for indices in small tables where 0 is illegal. It avoids use of the sign bit..
TEXTUAL-CONVENTION    
  INTEGER 1..32767  

Ordinal32  
The representation for positive integers. Same size as ISO 10175 (avoids use of sign bit).
TEXTUAL-CONVENTION    
  INTEGER 1..2147483647  

Ordinal64High  
The high-order 31 bits of a 62-bit positive integer (1..2**62-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

Ordinal64Low  
The low-order 31 bits of a 62-bit positive integer (1..2**62-1). A manager must get or set the high and low parts in the same operation.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

ScmFixedLocaleDisplayString  
This data type is used to model textual information in some localization (language, country, and character set), which is fixed (ie, NOT capable of being altered by management station request). This textual information SHALL be represented in the localization which is indicated by the current value of 'scmGenFixedLocalizationIndex'.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..255)  

ScmFixedLocaleUtf8String  
This data type is used to model textual information in the UTF-8 character set and some locale (language/country), which is fixed (ie, NOT capable of being altered by management station request). This textual information SHALL be represented in UTF-8 and the locale which is indicated by the current value of 'scmGenFixedLocalizationIndex'.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..255)  

ScmNamedLocaleUtf8String  
This data type is used to model textual information in the UTF-8 character set and some locale (language/country), which is named (ie, explicitly named by a parallel column or attribute or by the operation context).
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..255)  

ScmGenGroupSupport  
The terse conformance statement of ALL mandatory, conditionally mandatory, and optional SCMI General MIB object groups which are supported by this management agent implementation (ie, version) on this host system, specified in a bit-mask. The current set of values (which MAY be extended in the future) is given below: 1 : scmGenCurrentLocalizationGroup -- 2**0 2 : scmGenLocalizationGroup -- 2**1 4 : scmGenCodeIndexedStringGroup -- 2**2 8 : scmGenCodedCharSetGroup -- 2**3 16 : scmGenFixedLocalizationGroup -- 2**4 32 : scmGenLockGroup -- 2**5 64 : scmGenReconfGroup -- 2**6 128 : scmGenOptionGroup -- 2**7 256 : scmGenClientDataGroup -- 2**8 512 : scmGenTrapClientGroup -- 2**9 1024 : scmGenTrapViewGroup -- 2**10 2048 : scmGenBaseGroup -- 2**11 4096 : scmGenMessageMapGroup -- 2**12 8192 : scmGenMessageTextGroup -- 2**13 16384 : scmGenNotifyRuleGroup -- 2**14 32768 : scmGenNotifyDetailGroup -- 2**15 Usage: Conforming management agents SHALL accurately report their support for SCMI General MIB object groups.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

ScmGenLogFullPolicy  
The current policy for handling job/request/event log 'full' (in MIBs, in shared RAM, on disk, etc), on this host system.
TEXTUAL-CONVENTION    
  INTEGER other(1), unknown(2), disableService(3), disableAndPauseService(4), enableServiceAndFlushLog(5), enableServiceAndFlushOldest(6)  

ScmGenMessageMapStringLabel  
This syntax is used to specify a Samsung standard or experiemental message string label associated with the current value of the message string pointed to by 'scmGenMessageMapStringIndexOID'. Usage: Experimental message string labels SHOULD NOT be used in shipping versions of Samsung-branded products or services. They exist solely to facilitate rapid product development cycles. Usage: All Samsung message string label values SHALL be specified using display (NOT space) characters from the IANA registered charset 'utf-8' (ie, the UTF-8 octet-stream encoding of ISO-10646 UCS-4, described in RFC 2279). Usage: All Samsung message string label values SHALL contain no more than 64 UTF-8 display characters AND no more than 128 total octets (in some scripts, less than 64 characters in UTF-8 octet-stream encoding). Usage: All Samsung message string label values SHALL conform to the syntax specified below. A 'format', 'namespace', 'module', or 'field' component SHALL NOT contain hyphens. A 'format', 'namespace', or 'module' component SHALL use lowercase. A 'field' or 'qualifier' component MAY use mixed case (see examples below). A 'field' component MAY be use an abbreviated MIB object tag or other standardized identifier. ONLY a terminal 'qualifier' component MAY contain hyphens. Each component SHALL be separated by a hyphen '-' character. -- Samsung message string label general ABNF syntax msg_label = format '-' namespace '-' module '-' field '-' qualifier -- Samsung message string label alternatives ABNF syntax msg_label = std_label / exp_label Usage: All Samsung standard message string label values SHALL conform to the refined syntax specified below. -- Samsung standard message label refined ABNF syntax std_label = std_fmt '-' std_ns '-' module '-' field '-' qualifier -- Samsung standard format std_fmt = 'xs' -- Samsung standard format / 'x?' -- Samsung reserved formats (2 characters) -- Samsung standard namespace std_ns = 'ansi' -- American National Standards Institute / 'dmtf' -- Desktop Management Task Force / 'ecma' -- European Computer Manufacturers Assn / 'ieee' -- Institute Electrical/Electronic Engineers / 'ietf' -- Internet Engineering Task Force / 'iso' -- Int'l Organization for Standardization / 'itu' -- Int'l Telecommunication Union (aka CCITT) / 'omg' -- Object Management Group / 'pwg' -- Printer Working Group / 'scmi' -- Samsung Common Management Interface / 'xopen' -- X/Open (aka Open Group) / 'w3c' -- World Wide Web Consortium -- Samsung message label common components module = -- module identifier w/out hyphens field = -- field identifier w/out hyphens qualifier = -- qualifer (MAY contain hyphens) Examples of well-formed standard message string labels: -- Examples of ISO standard media sizes xs-iso-10175-mediaSize-iso-a4 -- 210 mm by 297 mm xs-iso-10175-mediaSize-iso-b4 -- 250 mm by 353 mm -- Examples of ISO standard media types xs-iso-10175-mediaType-envelope xs-iso-10175-mediaType-transparency -- Examples of ISO standard media colors xs-iso-10175-mediaColor-white xs-iso-10175-mediaColor-yellow -- Examples of standard MIB objects xs-ietf-rfc1759-alertDescription-coverOpen xs-pwg-jobmon-processingMessage-completed xs-scmi-11hostx-deviceDescription-dc230ST Usage: All Samsung experimental message string label values SHALL conform to the refined syntax specified below. -- Samsung experimental message label refined ABNF syntax exp_label = exp_fmt '-' exp_ns '-' module '-' field '-' qualifier -- Samsung experimental format exp_fmt = 'xx' -- Samsung experimental format -- Samsung experimental namespace exp_ns = std_ns '.' prod_ns std_ns = -- as defined above for standard labels prod_ns = -- 'official' / 'working' product identifier -- Samsung message label common components module = -- as defined above for standard labels field = -- as defined above for standard labels qualifier = -- as defined above for standard labels Examples of well-formed experimental message string labels: xx-ietf.dcs265-rfc1759-alertDescription-skyIsFalling xx-scmi.dc230-11hostx-deviceDescription-dc230ST xx-scmi.belize-11hostx-systemFaultString-missingWidgets Note: New or refined message label syntaxes MAY be defined in future versions of this SCMI General TC.
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..128)  

ScmGenNotifyDetailType  
The type of notify detail stored in this conceptual row in 'scmGenNotifyDetailTable'. Usage: Conforming SCMI management stations and agents SHALL encode notify details as UTF-8 strings (like SLPv2, RFC 2608). - Integers SHALL be encoded as (signed) decimal strings. - Booleans SHALL be encoded as 'true' or 'false' strings. - Strings SHALL be encoded as UTF-8 character strings. - Binary data (e.g., 'userCertificate') SHALL be stored in SLPv2 opaque encoding (leading '\FF' and escaped octets). Usage: Conformant implementations MUST encrypt passwords, keys, and other security information in 'scmGenNotifyDetailString'.
TEXTUAL-CONVENTION    
  INTEGER other(1), unknown(2), notifyRecipientURI(10), notifyEventNames(20), notifyEventDelay(21), notifySeverityFilter(22), notifyTrainingFilter(23), notifyMessageHeaderKeys(30), notifyMessageHeaderText(31), notifyMessageContentKeys(32), notifyMessageContentText(33)  

ScmGenNotifySchemeSupport  
The terse conformance statement of ALL notification URI schemes which are supported by this management agent implementation (ie, version) on this host system, specified in a bit-mask. The current set of values (which MAY be extended in the future) is given below: 1 : uriNotifySNMP -- RFC 1215/1906 - 2**0 (SNMP) 2 : uriNotifyMailto -- RFC 1738/2368 - 2**1 (SMTP) 4 : uriNotifyHTTP -- RFC 1738/2616 - 2**2 (HTTP) 8 : uriNotifyHTTPS -- RFC 1738/2396 - 2**3 (HTTPS) 16 : uriNotifyFTP -- RFC 1738/959 - 2**4 (FTP) Usage: Conforming management agents SHALL accurately report their support for notification URI schemes.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

ScmGenNotifySeverityFilter  
This type is used to specify a notification severity filter supported by this management agent for notification traffic in ALL domains specified by 'scmGenBaseSNMPDomainSupport' and 'scmGenBaseNotifySchemeSupport' (for URI-based notification), specified in a bit-mask. The current set of values (which MAY be extended in the future) is given below: 1 : severityReport -- 2**0 (informational) 2 : severityWarning -- 2**1 (eg, low toner) 4 : severitySoftError -- 2**2 (non-critical) 8 : severityHardError -- 2**3 (critical) 16 : severityTestReport -- 2**4 (product-specific) 32 : severityTestWarning -- 2**5 (product-specific) 64 : severityTestSoftError -- 2**6 (product-specific) 128 : severityTestHardError -- 2**7 (product-specific) 256 : severityInternalError -- 2**8 (product-specific) Usage: The terminology 'report', 'warning', and 'error' is coherent with the IETF IPP event notification work-in-progress and with the IETF Printer MIB (RFC 1759). Usage: Individual trap definitions MAY further constrain which notifications are 'in scope'. Usage: Conforming management agents SHALL accurately report their support for notification severity filters.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

ScmGenNotifyTrainingFilter  
This type is used to specify a notification training filter supported by this management agent for notification traffic in ALL domains specified by 'scmGenBaseSNMPDomainSupport' and 'scmGenBaseNotifySchemeSupport' (for URI-based notification), specified in a bit-mask. The current set of values (which MAY be extended in the future) is given below: 1 : trainingOther -- 2**0 (extension) 2 : trainingUnknown -- 2**1 (unknown) 4 : trainingNone -- 2**2 (untrained) 8 : trainingTrained -- 2**3 (trained) 16 : trainingFieldService -- 2**4 (field service) 32 : trainingManagement -- 2**5 (management) 64 : trainingNoIntervention -- 2**6 (management) Usage: The terminology used here is coherent with the IETF Printer MIB (RFC 1759). Usage: Individual trap definitions MAY further constrain which notifications are 'in scope'. Usage: Conforming management agents SHALL accurately report their support for notification training filters.
TEXTUAL-CONVENTION    
  INTEGER 0..2147483647  

ScmGenOptionValueSyntax  
A reconfiguration option, device detail, storage detail, service detail, or security profile detail value syntax, used by system administrators and end users to specify the correct value syntax for this option or detail. Usage: This option or detail value syntax is used to select which of the three value objects SHALL be used to contain the value of this option or detail. * An option or detail value syntax of 'oidObject' indicates that 'scm...ValueOID' SHALL be used to specify an actual object type, defined with 'OBJECT-TYPE'. * An option or detail value syntax of 'oidAutonomous' indicates that 'scm...ValueOID' SHALL be used to specify an autonomous object type, defined with 'OBJECT-IDENTITY' or simply 'OBJECT IDENTIFIER'. * An option or detail value syntax of 'stringBinary' indicates that 'scm...ValueString' SHALL be used to specify a (possibly) 'binary' (or 'non-printing') value string. * An option or detail value syntax of 'stringDisplay' indicates that 'scm...ValueString' SHALL be used to specify a 'displayable' (or 'printing') value string. * An option or detail value syntax of 'stringLocalization' indicates that 'scm...ValueLocalization' (for options) or 'scmGenFixedLocalizationIndex' (for details) SHALL be used to control the localization of the value string (with an underlying type of 'ScmGenFixedLocaleDisplayString'). * An option or detail value syntax of 'stringCodedCharSet' indicates that 'scm...ValueCodedCharSet' (for options) or 'scmGenFixedLocalizationIndex' (for details) SHALL be used to control the character set ONLY of the value string (with an underlying type of 'CodeIndexedStringIndex'). * An option or detail value syntax of 'stringDynamicLocalization' indicates that 'scmGenCurrentLocalization' SHALL be used to control the localization of the value string (with an underlying type of 'InternationalDisplayString'). * An option or detail value syntax of 'stringUtf8Localization' indicates that 'scm...ValueLocalization' (for options) or 'scmGenFixedLocalizationIndex' (for details) SHALL be used to control the localization of the value string (with an underlying type of 'ScmGenFixedLocaleUtf8String').
TEXTUAL-CONVENTION    
  INTEGER other(1), unknown(2), integerNumber(3), integerCounter(4), integerEnum(5), integerGauge(6), integerIndex(7), integerTruthValue(8), oidObject(9), oidAutonomous(10), stringBinary(11), stringDisplay(12), stringLocalization(13), stringCodedCharSet(14), stringDynamicLocalization(15), stringUtf8Localization(16)  

ScmGenReconfOptionState  
The processing state of ALL pending reconfiguration options of this host system. A write to this object by an (authorized) management station invokes a request for validation (or activation) of ALL pending reconfiguration options of this host system. A read of this object returns 'idle', 'validateInProgress', or 'activateInProgress' to report the processing state of the last 'validate...' or 'activate...' request. It is mandatory that a conforming management agent ensure that, at system initialization, this object SHALL be set to a value of 'idle'. * 'idle' - NO processing is 'in progress' for either 'validate...' or 'activate...' of any pending reconfiguration options. * 'validateForImmediateChange' - this management agent (and host system) SHALL perform ALL possible and appropriate validation of ALL pending reconfiguration options (reporting the FIRST error encountered during validation), so that reconfiguration could be performed successfully via 'activateForImmediateChange'. * 'validateForRebootChange' - this management agent (and host system) SHALL perform ALL possible and appropriate validation of ALL pending reconfiguration options (reporting the FIRST error encountered during validation), so that reconfiguration could be performed successfully via 'activateForRebootChange'. * 'validateForImmediateReboot' - this management agent (and host system) SHALL perform ALL possible and appropriate validation of ALL pending reconfiguration options (reporting the FIRST error encountered during validation), so that reconfiguration could be performed successfully via 'activateForImmediateReboot'. * 'validateInProgress' - indicates that this management agent (and host system) are currently performing validation of ALL pending reconfiguration options. Note: Conforming implementations NEED NOT support more than ONE of the above three 'validation...' operations. * 'activateForImmediateChange' - this management agent (and host system) SHALL perform immediate reconfiguration, NOT reboot, for ALL pending reconfiguration options (reporting the FIRST error encountered during validation). For all conforming implementations, this reconfiguration SHALL ALWAYS take effect immediately, WITHOUT host system reboot! Note: Conforming implementations are STRONGLY encouraged to consider supporting 'benign' reconfiguration in this manner. * 'activateForRebootChange' - this management agent (and host system) SHALL perform delayed reconfiguration, NOT reboot, for ALL pending reconfiguration options (reporting the FIRST error encountered during validation). For all conforming implementations, this reconfiguration SHALL ALWAYS take effect delayed, AFTER subsequent host system reboot! Note: Conforming implementations NEED NOT support 'caching' of multiple outstanding 'sets of reconfiguration' in this manner. * 'activateForImmediateReboot' - this management agent (and host system) SHALL perform immediate reconfiguration, AND reboot, for ALL pending reconfiguration options (reporting the FIRST error encountered during validation). For all conforming implementations, this reconfiguration SHALL ALWAYS take effect immediately, WITH host system reboot! Note: Conforming implementations are STRONGLY encouraged to consider secure alternatives (eg, Device Mgmt) for system reset. * 'activateInProgress' - indicates that this management agent (and host system) are currently performing activation of ALL pending reconfiguration options. Note: Conforming implementations NEED NOT support more than ONE of the above three 'activation...' operations.
TEXTUAL-CONVENTION    
  INTEGER idle(1), validateForImmediateChange(2), validateForRebootChange(3), validateForImmediateReboot(4), validateInProgress(5), activateForImmediateChange(6), activateForRebootChange(7), activateForImmediateReboot(8), activateInProgress(9)  

ScmGenRowPersistence  
This type is used to specify the persistence of this conceptual row in a table. Usage: Conforming management agents SHALL interpret persistence as follows: 1) 'volatile' rows NEED NOT be saved across power cycles, MAY contain one or more 'read-[create|write|only]' objects, and their underlying storage MAY be removable, and conforming management agents NEED NOT delete such rows (eg, a block in RAM, PCMCIA card, etc); 2) 'nonvolatile' rows SHALL be saved across power cycles, MAY contain one or more 'read-[write|only]' objects, and their underlying storage MAY be removable, and conforming management agents MAY delete such rows (eg, a sector on CD-ROM, font cartridge, hard disk, etc); 3) 'permanent' rows SHALL be saved across power cycles, MAY contain one or more 'read-[write|only]' objects, and their underlying storage SHALL NOT be removable, and conforming management agents SHALL NOT delete such rows (eg, a sector on EEPROM, battery-backed RAM, bubble, etc); 4) 'readonly' rows SHALL be saved across power cycles, SHALL contain exclusively 'read-only' objects, and their underlying storage SHALL NOT be removable, and conforming management agents SHALL NOT delete such rows (eg, a sector on ROM, ASIC, etc). Usage: Dynamically created rows MAY ONLY be given 'volatile' or 'nonvolatile' persistence. Note: Equivalent to SNMPv2 'StorageType' textual convention, which has an unfortunately ambiguous name.
TEXTUAL-CONVENTION    
  INTEGER other(1), unknown(2), volatile(3), nonvolatile(4), permanent(5), readonly(6)  

ScmGenSNMPDomain  
This type is used to specify a transport domain (address and name space) which is supported by this management agent for SNMP protocol traffic (SNMP responses, SNMP traps, etc), in ALL versions specified by 'scmGenBaseSNMPVersionSupport'. This type is also used to allow the 'scmGenTrapClientTable' to be used with any URI scheme (e.g., 'mailto:') for notifications, by specifying 'uriNotifyDomain'.
TEXTUAL-CONVENTION    
  INTEGER snmpUDPDomain(1), snmpCLNSDomain(2), snmpCONSDomain(3), snmpDDPDomain(4), snmpIPXDomain(5), snmpNetBIOSDomain(10), snmpNetBEUIDomain(11), snmpTCPDomain(20), uriNotifyDomain(30)  

ScmGenSNMPVersion  
This type is used to specify an SNMP version (RFC 1157, RFC 1905, etc) which is supported by this management agent for SNMP protocol traffic (SNMP responses, SNMP traps, etc), in ALL domains specified by 'scmGenBaseSNMPDomainSupport'.
TEXTUAL-CONVENTION    
  INTEGER unknown(1), other(2), snmpV1Community(3), snmpV1Party(4), snmpV2Party(5), snmpV2Community(6), snmpV2Usec(7), snmpV2Star(8), snmpV2Secure(9), snmpV3Secure(10)  

ScmGenSNMPv2ErrorStatus  
Usage: This type specifies the SMIv2 equivalent of the SMIv1 'ErrorStatus' textual convention as an enumerated type. Note: The enum of '0' (zero) in this textual convention is illegal in strict SMIv1 (see section 3.2.1.1 of RFC 1155), so this TC must be converted to an integer range for pure SMIv1.
TEXTUAL-CONVENTION    
  INTEGER noError(0), tooBig(1), noSuchName(2), badValue(3), readOnly(4), genErr(5), noAccess(6), wrongType(7), wrongLength(8), wrongEncoding(9), wrongValue(10), noCreation(11), inconsistentValue(12), resourceUnavailable(13), commitFailed(14), undoFailed(15), authorizationError(16), notWritable(17), inconsistentName(18)  

ScmGlobalUniqueID  
A management station or management agent specifies an object of type 'GlobalUniqueID' to uniquely label a client job request, a system administration request, or ANY other managed object (or set of managed objects) which are required to be unambiguously identified in a distributed network environment. An object of type 'GlobalUniqueID' SHALL be a textual string representation in standard 'dotted decimal' form of an OID. An object of type 'GlobalUniqueID' SHALL be composed of three mandatory sections (plus zero or more optional sections), as follows: nodeID.userID.seqID[[.subID1]...[.subIDn]] Each of the sections SHALL be separated by a dot ('.'). The three mandatory sections and any specified optional sections (in left to right order) SHALL be: 1) A globally unambiguous (within at least the network domain of the Requestor and Responder host systems) dotted decimal 'nodeID' of the Requestor host system which explicitly or implicitly labelled this managed object, either: a) A domain specific network layer address (eg, IETF IP address for 'nodeIDTypeIP'); OR b) A domain specific datalink MAC sublayer address (eg, ISO 8802-5 MAC address for 'nodeIDType88025'). 2) A locally unambiguous (within at least the Requestor and/or Responder host systems) dotted decimal 'userID' (ie, user identifier) of the user who explicitly or implicitly labelled this managed object. 3) A locally unambiguous (within at least the Requestor and/or Responder host systems) dotted decimal 'seqID' (ie, sequence identifier) assigned by the host system or user who explicitly or implicitly labelled this managed object. 4) A locally unambiguous (within at least the Requestor and/or Responder host systems) dotted decimal 'subID' (ie, sequence sub-identifier) assigned by the host system or user who explicitly or implicitly labelled this managed object. Usage: Conforming implementations MAY use one or more optional sections in an 'ScmGlobalUniqueID', for example to assign a sub-job identifier for job distribution services (e.g., fax to multiple destinations specified in the PDL of an input 'print' job - using an original 'scmJobClientId' which is augmented by the server that splits up the destinations into separate jobs). Usage: Conforming implementations SHALL NOT specify BOTH the first ('nodeID') and second ('userID') sections as 'empty', but one OR the other section MAY take on an 'empty' value (see below). The third ('seqID') section SHALL NOT be 'empty'. Each of the three mandatory sections and any optional sections SHALL be composed of one mandatory and two optional subsections, as follows: sectionLength.sectionType.sectionValue Each of the subsections SHALL be separated by a dot ('.'). The three subsections (in left to right order) SHALL be: 1) A mandatory 'sectionLength', which specifies the decimal count of dotted decimal 'components' in the associated 'sectionValue' - this 'sectionLength' SHALL NOT be self-inclusive and SHALL NOT include the single 'component' of the 'sectionType' - a 'sectionLength' of decimal zero ('0') SHALL indicate an 'empty' section, and the associated two subsections ('sectionType' and 'sectionValue') SHALL be omitted. 2) An optional 'sectionType', selected from the standard 'sectionType' choices applicable to this section (below). 3) An optional 'sectionValue', specified as a dotted decimal string of 'components', each 'component' separated by a dot ('.'). The standard 'sectionType' choices (one set for each section) SHALL be as follows: 1) 'nodeIDType' -- for mandatory 'nodeID' section 1 : nodeIDTypeOther -- Other 2 : nodeIDTypeUnknown -- Unknown 11 : nodeIDTypeIP -- Internet IP 12 : nodeIDTypeCLNS -- OSI CLNS 13 : nodeIDTypeCONS -- OSI CONS 14 : nodeIDTypeDDP -- AppleTalk DDP 15 : nodeIDTypeIPX -- NetWare IPX 16 : nodeIDTypeNetBIOS -- IBM NetBIOS 31 : nodeIDType88023 -- ISO 8802-3 (Ethernet LAN) 32 : nodeIDType88024 -- ISO 8802-4 (TokenBus LAN) 33 : nodeIDType88025 -- ISO 8802-5 (TokenRing LAN) 34 : nodeIDType88026 -- ISO 8802-6 (SlottedRing MAN) 2) 'userIDType' -- for mandatory 'userID' section 1 : userIDTypeOther -- Other 2 : userIDTypeUnknown -- Unknown 11 : userIDTypeSystem -- System scope 12 : userIDTypeSubnet -- Subnet scope 13 : userIDTypeNetwork -- Network scope 14 : userIDTypeGlobal -- Global scope 3) 'seqIDType' -- for mandatory 'seqID' section 1 : seqIDTypeOther -- Other 2 : seqIDTypeUnknown -- Unknown 11 : seqIDTypeSystem -- System generated 12 : seqIDTypeProcess -- Process generated 13 : seqIDTypeThread -- Thread generated 4) 'subIDType' -- for optional 'subID' sections 1 : subIDTypeOther -- Other 2 : subIDTypeUnknown -- Unknown 11 : subIDTypeSystem -- System generated 12 : subIDTypeProcess -- Process generated 13 : subIDTypeThread -- Thread generated Usage: A 'seqID' of any type SHALL be system-unique. Usage: A 'seqID' of type 'seqIDTypeProcess' SHALL be prefixed (if necessary) by a system-unique dotted decimal 'processID'. Usage: A 'seqID' of type 'seqIDTypeThread' SHALL be prefixed (if necessary) by a system-unique dotted decimal 'threadID' (possibly itself prefixed by a system-unique 'processID'). Example: A request submitted from a client end system running the IETF Internet Protocol Suite (IPS), with an IP address of '13.240.128.21', without a specified dotted decimal 'userID', might include an 'scmJobClientId' of the following form: '4.11.13.240.128.21.0.1.11.3045.1.11.23' [GlobalUniqueID] |---------1--------|2|----3----|---4---| [Sections] 1) The mandatory first section ('nodeID') consists of: a) 'sectionLength' of '4'; b) 'sectionType' of '11' ('nodeIDTypeIP'); and c) 'sectionValue' of '13.240.128.21' (4 components). 2) The mandatory second section ('userID') consists of: a) 'sectionLength' of '0' (ie, 'empty' section). 3) The mandatory third section ('seqID') consists of: a) 'sectionLength' of '1'; b) 'sectionType' of '11' ('seqIDTypeSystem'); and c) 'sectionValue' of '3045' (one component). 4) The optional fourth section ('subID') consists of: a) 'sectionLength' of '1'; b) 'sectionType' of '11' ('subIDTypeSystem'); and c) 'sectionValue' of '23' (one component).
TEXTUAL-CONVENTION    
  OCTET STRING Size(0..255)  

Defined Values

scmGeneralTC 1.3.6.1.4.1.236.11.5.11.50
Version: 1.00 Samsung General Textual Conventions See section 9 'Supplement' of SCMI General TC for implementation and conformance guidance for this TC module. Copyright (C) 1995-2002 Samsung Corporation. All Rights Reserved.
MODULE-IDENTITY    

zeroDotZero 0.0
OBJECT IDENTIFIER    

scmGenZeroDotZero 0.0.0
A value used for null object identifiers prior to SCMI v5.1. Do not use. Instead use the standard definition in RFC 1902/2578 - 'zeroDotZero' - left here for compatibility.
Status: current Access: read-only
OBJECT-IDENTITY    

sCmGeneralDummy 1.3.6.1.4.1.236.11.5.11.50.999
OBJECT IDENTIFIER    

sCmGenCardinal16 1.3.6.1.4.1.236.11.5.11.50.999.1
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Cardinal16  

sCmGenCardinal32 1.3.6.1.4.1.236.11.5.11.50.999.2
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Cardinal32  

sCmGenCardinal64High 1.3.6.1.4.1.236.11.5.11.50.999.3
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Cardinal64High  

sCmGenCardinal64Low 1.3.6.1.4.1.236.11.5.11.50.999.4
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Cardinal64Low  

sCmGenCodedCountry 1.3.6.1.4.1.236.11.5.11.50.999.5
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  CodedCountry  

sCmGenCodedLanguage 1.3.6.1.4.1.236.11.5.11.50.999.6
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  CodedLanguage  

sCmGenCodeIndexedStringIndex 1.3.6.1.4.1.236.11.5.11.50.999.7
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  CodeIndexedStringIndex  

sCmGenCounter64High 1.3.6.1.4.1.236.11.5.11.50.999.8
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Counter64High  

sCmGenCounter64Low 1.3.6.1.4.1.236.11.5.11.50.999.9
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Counter64Low  

sCmGenGauge64High 1.3.6.1.4.1.236.11.5.11.50.999.10
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge64High  

sCmGenGauge64Low 1.3.6.1.4.1.236.11.5.11.50.999.11
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Gauge64Low  

sCmGenInteger64High 1.3.6.1.4.1.236.11.5.11.50.999.12
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer64High  

sCmGenInteger64Low 1.3.6.1.4.1.236.11.5.11.50.999.13
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Integer64Low  

sCmGenOrdinal16 1.3.6.1.4.1.236.11.5.11.50.999.14
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Ordinal16  

sCmGenOrdinal32 1.3.6.1.4.1.236.11.5.11.50.999.15
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Ordinal32  

sCmGenOrdinal64High 1.3.6.1.4.1.236.11.5.11.50.999.16
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Ordinal64High  

sCmGenOrdinal64Low 1.3.6.1.4.1.236.11.5.11.50.999.17
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  Ordinal64Low  

sCmGenFixedLocaleDisplayString 1.3.6.1.4.1.236.11.5.11.50.999.18
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmFixedLocaleDisplayString  

sCmGenGroupSupport 1.3.6.1.4.1.236.11.5.11.50.999.19
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenGroupSupport  

sCmGenLogFullPolicy 1.3.6.1.4.1.236.11.5.11.50.999.20
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenLogFullPolicy  

sCmGenOptionValueSyntax 1.3.6.1.4.1.236.11.5.11.50.999.21
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenOptionValueSyntax  

sCmGenReconfOptionState 1.3.6.1.4.1.236.11.5.11.50.999.22
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenReconfOptionState  

sCmGenRowPersistence 1.3.6.1.4.1.236.11.5.11.50.999.23
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenRowPersistence  

sCmGenSNMPDomain 1.3.6.1.4.1.236.11.5.11.50.999.24
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenSNMPDomain  

sCmGenSNMPVersion 1.3.6.1.4.1.236.11.5.11.50.999.25
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenSNMPVersion  

sCmGenSNMPv2ErrorStatus 1.3.6.1.4.1.236.11.5.11.50.999.26
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenSNMPv2ErrorStatus  

sCmGenGlobalUniqueID 1.3.6.1.4.1.236.11.5.11.50.999.27
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGlobalUniqueID  

sCmGenFixedLocaleUtf8String 1.3.6.1.4.1.236.11.5.11.50.999.28
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmFixedLocaleUtf8String  

sCmGenMessageMapStringLabel 1.3.6.1.4.1.236.11.5.11.50.999.29
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenMessageMapStringLabel  

sCmGenNamedLocaleUtf8String 1.3.6.1.4.1.236.11.5.11.50.999.30
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmNamedLocaleUtf8String  

sCmGenNotifySchemeSupport 1.3.6.1.4.1.236.11.5.11.50.999.31
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenNotifySchemeSupport  

sCmGenNotifySeverityFilter 1.3.6.1.4.1.236.11.5.11.50.999.32
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenNotifySeverityFilter  

sCmGenNotifyTrainingFilter 1.3.6.1.4.1.236.11.5.11.50.999.33
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenNotifyTrainingFilter  

sCmGenNotifyDetailType 1.3.6.1.4.1.236.11.5.11.50.999.34
Dummy - DO NOT USE
Status: current Access: not-accessible
OBJECT-TYPE    
  ScmGenNotifyDetailType