MIB Discovery
1856 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 9 (ciscoMgmt). 312 (ciscoDataCollectionMIB). 1 (ciscoDataCollMIBObjects). 1 (cdcVFile). 3 (cdcVFileTable). 1 (cdcVFileEntry). 2 (cdcVFileName)
OID : 1.3.6.1.4.1.9.9.312.1.1.3.1.2
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoMgmt. ciscoDataCollectionMIB. ciscoDataCollMIBObjects. cdcVFile. cdcVFileTable. cdcVFileEntry. cdcVFileName
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.4.1.9.9.312.1.1.3.1.2
Module CISCO-DATA-COLLECTION-MIB (CISCO)
NomcdcVFileName
Accesreadwrite
Statuscurrent
DescriptionThe base-name of the VFiles (created by data collection operations corresponding to this entry) into which data is to be collected. When a VFile is created, it's full name is obtained by the concatentation of a suffix to this value. The suffix will be chosen by the agent such that the VFiles created for this entry have unique names. For e.g. the suffix could be a string representation of the date and time when the VFile was created. If VFiles are to be placed in the agent's local filesystem (provided the agent supports it) then this value should also contain the absolute path of the location as a prefix to the base name. An agent will respond with inconsistentValue to a management set operation which attempts to modify the value of this object to the same value as already held by another instance of cdcVFileName, or wrongValue if the new value is invalid for use as a file name on the local file system (e.g., many file systems do not support white space embedded in file names). This object's value may be modified at any time. However the new name will be used only when the next VFile is created for this entry.
SyntaxeOctetString (0...255)