A table containing 'client data' objects for use by conforming
management stations/agents, particularly during installation
of this host system.
Usage: To allocate 'client data' on managed host system,
a conforming management station (or management agent) shall
ALWAYS examine 'xcmGenClientDataLastIndex', to determine the
appropriate value of 'xcmGenClientDataIndex' to use when
creating a new conceptual row in the 'xcmGenClientDataTable'.
Usage: Throughout this specification, the term 'stable storage'
refers to storage which is reliable over long durations (years)
and is NOT destroyed by host system reboot (eg, battery-backed
DRAM is 'stable storage' - while simple DRAM is NOT 'stable
storage'). Examples of valid 'stable storage' include: NVRAM,
hard disk, EEPROM, etc.
Usage: Conforming implementations shall ALWAYS preserve active
'client data' objects across management agent power cycles,
and shall implement one of the following two methods:
1) The agent shall store 'client data' objects directly in
'stable storage'; or
2) The agent shall automatically checkpoint all active 'client
data' objects to 'stable storage' with reasonable frequency
(either due to a write to some 'client data' object, or upon
expiration of a product-specific timeout).
Usage: Conforming implementations may (optionally) support
one of the following two 'checkpoint protocols':
1) A client sends a 'Set' of 'xcmGenClientDataRowStatus' to
'active(1)', to request that a 'checkpoint' be performed;
2a) An agent which supports 'rapid checkpoint',
completes the checkpoint to 'stable storage', and
sends a 'SetResponse' with 'noError(0)';
2b) An agent which supports 'delayed checkpoint',
changes 'xcmGenClientDataRowStatus' to 'notInService(2)',
sends a 'SetResponse' with 'noError(0)',
completes the checkpoint to 'stable storage', and
changes 'xcmGenClientDataRowStatus' back to 'active(1)'.
Parsed from file XEROX-GENERAL-MIB.mib.txt
Company: None
Module: XEROX-GENERAL-MIB
A table containing 'client data' objects for use by conforming
management stations/agents, particularly during installation
of this host system.
Usage: To allocate 'client data' on managed host system,
a conforming management station (or management agent) shall
ALWAYS examine 'xcmGenClientDataLastIndex', to determine the
appropriate value of 'xcmGenClientDataIndex' to use when
creating a new conceptual row in the 'xcmGenClientDataTable'.
Usage: Throughout this specification, the term 'stable storage'
refers to storage which is reliable over long durations (years)
and is NOT destroyed by host system reboot (eg, battery-backed
DRAM is 'stable storage' - while simple DRAM is NOT 'stable
storage'). Examples of valid 'stable storage' include: NVRAM,
hard disk, EEPROM, etc.
Usage: Conforming implementations shall ALWAYS preserve active
'client data' objects across management agent power cycles,
and shall implement one of the following two methods:
1) The agent shall store 'client data' objects directly in
'stable storage'; or
2) The agent shall automatically checkpoint all active 'client
data' objects to 'stable storage' with reasonable frequency
(either due to a write to some 'client data' object, or upon
expiration of a product-specific timeout).
Usage: Conforming implementations may (optionally) support
one of the following two 'checkpoint protocols':
1) A client sends a 'Set' of 'xcmGenClientDataRowStatus' to
'active(1)', to request that a 'checkpoint' be performed;
2a) An agent which supports 'rapid checkpoint',
completes the checkpoint to 'stable storage', and
sends a 'SetResponse' with 'noError(0)';
2b) An agent which supports 'delayed checkpoint',
changes 'xcmGenClientDataRowStatus' to 'notInService(2)',
sends a 'SetResponse' with 'noError(0)',
completes the checkpoint to 'stable storage', and
changes 'xcmGenClientDataRowStatus' back to 'active(1)'.
Parsed from file XEROX-GENERAL-MIB.mib
Module: XEROX-GENERAL-MIB
Vendor: Xerox
Module: XEROX-GENERAL-MIB
[Automatically extracted from oidview.com]
xcmGenClientDataTable OBJECT-TYPE SYNTAX SEQUENCE OF XcmGenClientDataEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " A table containing 'client data' objects for use by conforming management stations/agents, particularly during installation of this host system. Usage: To allocate 'client data' on managed host system, a conforming management station (or management agent) shall ALWAYS examine 'xcmGenClientDataLastIndex', to determine the appropriate value of 'xcmGenClientDataIndex' to use when creating a new conceptual row in the 'xcmGenClientDataTable'. Usage: Throughout this specification, the term 'stable storage' refers to storage which is reliable over long durations (years) and is NOT destroyed by host system reboot (eg, battery-backed DRAM is 'stable storage' - while simple DRAM is NOT 'stable storage'). Examples of valid 'stable storage' include: NVRAM, hard disk, EEPROM, etc. Usage: Conforming implementations shall ALWAYS preserve active 'client data' objects across management agent power cycles, and shall implement one of the following two methods: 1) The agent shall store 'client data' objects directly in 'stable storage'; or 2) The agent shall automatically checkpoint all active 'client data' objects to 'stable storage' with reasonable frequency (either due to a write to some 'client data' object, or upon expiration of a product-specific timeout). Usage: Conforming implementations may (optionally) support one of the following two 'checkpoint protocols': 1) A client sends a 'Set' of 'xcmGenClientDataRowStatus' to 'active(1)', to request that a 'checkpoint' be performed; 2a) An agent which supports 'rapid checkpoint', completes the checkpoint to 'stable storage', and sends a 'SetResponse' with 'noError(0)';
2b) An agent which supports 'delayed checkpoint', changes 'xcmGenClientDataRowStatus' to 'notInService(2)', sends a 'SetResponse' with 'noError(0)', completes the checkpoint to 'stable storage', and changes 'xcmGenClientDataRowStatus' back to 'active(1)'." ::= { xcmGenClientData 2 }
xcmGenClientDataTable OBJECT-TYPE SYNTAX SEQUENCE OF XcmGenClientDataEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " A table containing 'client data' objects for use by conforming management stations/agents, particularly during installation of this host system. Usage: To allocate 'client data' on managed host system, a conforming management station (or management agent) shall ALWAYS examine 'xcmGenClientDataLastIndex', to determine the appropriate value of 'xcmGenClientDataIndex' to use when creating a new conceptual row in the 'xcmGenClientDataTable'. Usage: Throughout this specification, the term 'stable storage' refers to storage which is reliable over long durations (years) and is NOT destroyed by host system reboot (eg, battery-backed DRAM is 'stable storage' - while simple DRAM is NOT 'stable storage'). Examples of valid 'stable storage' include: NVRAM, hard disk, EEPROM, etc. Usage: Conforming implementations shall ALWAYS preserve active 'client data' objects across management agent power cycles, and shall implement one of the following two methods: 1) The agent shall store 'client data' objects directly in 'stable storage'; or 2) The agent shall automatically checkpoint all active 'client data' objects to 'stable storage' with reasonable frequency (either due to a write to some 'client data' object, or upon expiration of a product-specific timeout). Usage: Conforming implementations may (optionally) support one of the following two 'checkpoint protocols': 1) A client sends a 'Set' of 'xcmGenClientDataRowStatus' to 'active(1)', to request that a 'checkpoint' be performed; 2a) An agent which supports 'rapid checkpoint', completes the checkpoint to 'stable storage', and sends a 'SetResponse' with 'noError(0)';
2b) An agent which supports 'delayed checkpoint', changes 'xcmGenClientDataRowStatus' to 'notInService(2)', sends a 'SetResponse' with 'noError(0)', completes the checkpoint to 'stable storage', and changes 'xcmGenClientDataRowStatus' back to 'active(1)'." ::= { xcmGenClientData 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.253.8.51.11.2.1 | xcmGenClientDataEntry | 7 | 7 | An entry containing 'client data' objects for use by conforming management stations/agents, particularly during installation of t… |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.253.8.51.11.1 | xcmGenClientDataSimple | 2 | 4 | This subtree is current. Subordinate objects are leaf objects. |