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) |
|
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) |
|
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 |
|
|