OID reference

prvtConfigAction

1.3.6.1.4.1.738.10.111.1.1.2.3.1.5

Description

Represents a file action request to be committed immediately (with set request) or that is being commited (with get request). idle = there is no action being performed or prepared prepare = parameters of an action are being edited. This is used by the manager to willingly avoid editing parameters while another manager…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.738.10.111.1.1.2.3.1 (prvtConfigFileAction)
Node code
5
Node name
prvtConfigAction
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.738.10.111.1.1.2.3.1.5
URN notation
urn:oid:1.3.6.1.4.1.738.10.111.1.1.2.3.1.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 738 10 111 1 1 2 3 1 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) privateVendorOID(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) prvtVendorDefMIB(738) prvt-products(10) software(111) prvtInterworkingOSMIB(1) prvtInterworkingOSMIBObjects(1) management(2) prvtConfigFiles(3) prvtConfigFileAction(1) prvtConfigAction(5)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/738/10/111/1/1/2/3/1/5
  • /ISO/Identified-Organization/6/1/4/1/738/10/111/1/1/2/3/1/5
  • /ISO/3/6/1/4/1/738/10/111/1/1/2/3/1/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/738/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/enterprise/privateVendorOID/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/enterprise/prvtVendorDefMIB/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/enterprises/738/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/enterprises/privateVendorOID/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/enterprises/prvtVendorDefMIB/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/738/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/privateVendorOID/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/prvtVendorDefMIB/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/vendor-objects/738/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/vendor-objects/privateVendorOID/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/identified-organization/dod/internet/private/vendor-objects/prvtVendorDefMIB/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/org/dod/internet/private/enterprise/738/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/org/dod/internet/private/enterprise/privateVendorOID/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/org/dod/internet/private/enterprise/prvtVendorDefMIB/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • /iso/org/dod/internet/private/enterprises/738/prvt-products/software/prvtInterworkingOSMIB/prvtInterworkingOSMIBObjects/management/prvtConfigFiles/prvtConfigFileAction/prvtConfigAction
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current

Enumerated values

ValueName
1idle
2prepare
3copy
4rename
5merge

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.738.10.111.1.1.2.3.1.5.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

prvtConfigAction OBJECT-TYPE
    SYNTAX      INTEGER { idle(1), prepare(2), copy(3), rename(4), 
                    merge(5) }
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION 
        "Represents a file action request to be committed immediately (with set request) or that
         is being commited (with get request).
         
         idle = there is no action being performed or prepared
         prepare = parameters of an action are being edited. This is used by the manager to
           willingly avoid editing parameters while another manager does so.
         copy = copy a file from source to target, where source and target have a broad meaning
          (local/remote file system or running configuration). See details below.
         rename = rename a local file (see details below)
         merge = merge a local file to running configuration
         
         Allowed Transitions:
         * idle to prepare
         * prepare to any other
         
         Automatic Transitions:
         * copy to idle, when action is done
         * rename to idle, when action is done
         * merge to idle, when action is done
         
         ******************************
         *       Action = copy        *
         ******************************
         The following table gives the corresponding CLI command for each combination of source and target type.
         
         +--------------+----------------------+----------------------+---------------+----------------------+
         |      \ Target|fileSystem            |runningBinary         |runningScript  |ftp                   |
         |Source \      |                      |                      |               |                      |
         +--------------+----------------------+----------------------+---------------+----------------------+
         |fileSystem    |file cp from          |file restore          |file replace   |file cp from          |
         |              |SRC                   |binary-running-config |SRC            |SRC                   |
         |              |TRG                   |flash                 |               |FTP_TRG               |
         +--------------+----------------------+----------------------+---------------+----------------------+
         |techSupport   |file cp               |-- not legal --       |-- not legal --|file cp               |
         |              |technical-support     |                      |               |technical-support     |
         |              |TRG                   |                      |               |FTP_TRG               |
         +--------------+----------------------+----------------------+---------------+----------------------+
         |runningBinary |file backup           |-- not legal --       |-- not legal --|file backup           |
         |              |binary-running-config |                      |               |binary-running-config |
         |              |flash                 |                      |               |FTP_TRG               |
         +--------------+----------------------+----------------------+---------------+----------------------+
         |runningScript |file cp               |-- not legal --       |-- not legal --|file cp               |
         |              |running-configuration |                      |               |running-configuration |
         |              |TRG                   |                      |               |FTP_TRG               |
         +--------------+----------------------+----------------------+---------------+----------------------+
         |ftp           |file cp from          |file restore          |-- not legal --|-- not legal --       |
         |              |FTP_SRC               |binary-running-config |               |                      |
         |              |TRG                   |FTP_SRC               |               |                      |
         +--------------+----------------------+----------------------+---------------+----------------------+
         Comments:
         (a) FTP_SRC denotes ftp://[USER[:PSW]@]ADR[:PORT]/SRC
            FTP_TRG denotes ftp://[USER[:PSW]@]ADR[:PORT]/TRG
         (b) SRC, TRG, USER, PSW, ADR and PORT are respectively the values of prvtConfigSourceFileName,
            prvtConfigTargetFileName, prvtConfigRemoteUser, prvtConfigRemotePassword,
            prvtConfigRemoteAddress and prvtConfigRemotePort.
            When any of these are not mentioned in the command, then the value is not relevant.
         (c) tftp is the same as ftp, except that USER, PSW are not used
         (d) the error 'inconsistentValue' is returned for any combination marked 'not legal'
         (e) a successful execution of a copy action when target type is 'runningBinary' (equivalent CLI
            command is 'file restore binary-running config ...') results in a system reload
         (f) The above comments are also applicable to the other actions explained below.
         
         ******************************
         *       Action = rename      *
         ******************************
         equivalent to CLI command: file mv SRC TRG
         prvtConfigTargetType and prvtConfigSourceType must equal to 'fileSystem'
         
         ******************************
         *       Action = merge       *
         ******************************
         equivalent to CLI command: file merge SRC
         prvtConfigSourceType must equal 'fileSystem'
         prvtConfigTargetType must equal 'runningScript'
         
         ******************************
         *       Examples             *
         ******************************
         [1] To save the binary of the running configuration to a remote ftp server, with default username,
            default password, default port, IP = 10.2.144.20, and target file name 'example.bin', the
            procedure would be (assuming that prvtConfigAction is initially in 'idle' state):
         set prvtConfigAction <- 'prepare'
         set prvtConfigSourceType <- 'runningBinary'
         set prvtConfigTargetType <- 'ftp'
         set prvtConfigTargetFileName <- 'example.bin'
         set prvtConfigRemoteAddress  <- '10.2.144.20'
         set prvtConfigAction <- 'copy'
         
         [2] To rename a file named 'first.txt' to 'second.txt', the procedure would be
            (assuming that prvtConfigAction is initially in 'idle' state):
         set prvtConfigAction <- 'prepare'
         set prvtConfigSourceType <- 'fileSystem'
         set prvtConfigTargetType <- 'fileSystem'
         set prvtConfigSourceFileName <- 'first.txt'
         set prvtConfigTargetFileName <- 'second.txt'
         set prvtConfigAction <- 'rename'"
    ::= { prvtConfigFileAction 5 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Represents a file action request to be committed immediately (with set request) or that is being commited (with get request). idle = there is no action being performed or prepared prepare = parameters of an action are being edited. This is used by the manager to willingly avoid editing parameters while another manager does so. copy = copy a file from source to target, where source and target have a broad meaning (local/remote file system or running configuration). See details below. rename = rename a local file (see details below) merge = merge a local file to running configuration Allowed Transitions: * idle to prepare * prepare to any other Automatic Transitions: * copy to idle, when action is done * rename to idle, when action is done * merge to idle, when action is done ****************************** * Action = copy * ****************************** The following table gives the corresponding CLI command for each combination of source and target type. +--------------+----------------------+----------------------+---------------+----------------------+ | \ Target|fileSystem |runningBinary |runningScript |ftp | |Source \ | | | | | +--------------+----------------------+----------------------+---------------+----------------------+ |fileSystem |file cp from |file restore |file replace |file cp from | | |SRC |binary-running-config |SRC |SRC | | |TRG |flash | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |techSupport |file cp |-- not legal -- |-- not legal --|file cp | | |technical-support | | |technical-support | | |TRG | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |runningBinary |file backup |-- not legal -- |-- not legal --|file backup | | |binary-running-config | | |binary-running-config | | |flash | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |runningScript |file cp |-- not legal -- |-- not legal --|file cp | | |running-configuration | | |running-configuration | | |TRG | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |ftp |file cp from |file restore |-- not legal --|-- not legal -- | | |FTP_SRC |binary-running-config | | | | |TRG |FTP_SRC | | | +--------------+----------------------+----------------------+---------------+----------------------+ Comments: (a) FTP_SRC denotes ftp://[USER[:PSW]@]ADR[:PORT]/SRC FTP_TRG denotes ftp://[USER[:PSW]@]ADR[:PORT]/TRG (b) SRC, TRG, USER, PSW, ADR and PORT are respectively the values of prvtConfigSourceFileName, prvtConfigTargetFileName, prvtConfigRemoteUser, prvtConfigRemotePassword, prvtConfigRemoteAddress and prvtConfigRemotePort. When any of these are not mentioned in the command, then the value is not relevant. (c) tftp is the same as ftp, except that USER, PSW are not used (d) the error 'inconsistentValue' is returned for any combination marked 'not legal' (e) a successful execution of a copy action when target type is 'runningBinary' (equivalent CLI command is 'file restore binary-running config ...') results in a system reload (f) The above comments are also applicable to the other actions explained below. ****************************** * Action = rename * ****************************** equivalent to CLI command: file mv SRC TRG prvtConfigTargetType and prvtConfigSourceType must equal to 'fileSystem' ****************************** * Action = merge * ****************************** equivalent to CLI command: file merge SRC prvtConfigSourceType must equal 'fileSystem' prvtConfigTargetType must equal 'runningScript' ****************************** * Examples * ****************************** [1] To save the binary of the running configuration to a remote ftp server, with default username, default password, default port, IP = 10.2.144.20, and target file name 'example.bin', the procedure would be (assuming that prvtConfigAction is initially in 'idle' state): set prvtConfigAction <- 'prepare' set prvtConfigSourceType <- 'runningBinary' set prvtConfigTargetType <- 'ftp' set prvtConfigTargetFileName <- 'example.bin' set prvtConfigRemoteAddress <- '10.2.144.20' set prvtConfigAction <- 'copy' [2] To rename a file named 'first.txt' to 'second.txt', the procedure would be (assuming that prvtConfigAction is initially in 'idle' state): set prvtConfigAction <- 'prepare' set prvtConfigSourceType <- 'fileSystem' set prvtConfigTargetType <- 'fileSystem' set prvtConfigSourceFileName <- 'first.txt' set prvtConfigTargetFileName <- 'second.txt' set prvtConfigAction <- 'rename'

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

prvtConfigAction · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: prvtConfigAction

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "prvtConfigAction",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "idle",
    "(",
    "1",
    ")",
    ",",
    "prepare",
    "(",
    "2",
    ")",
    ",",
    "copy",
    "(",
    "3",
    ")",
    ",",
    "rename",
    "(",
    "4",
    ")",
    ",",
    "merge",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Represents a file action request to be committed immediately (with set request) or that is being commited (with get request). idle = there is no action being performed or prepared prepare = parameters of an action are being edited. This is used by the manager to willingly avoid editing parameters while another manager does so. copy = copy a file from source to target, where source and target have a broad meaning (local/remote file system or running configuration). See details below. rename = rename a local file (see details below) merge = merge a local file to running configuration Allowed Transitions: * idle to prepare * prepare to any other Automatic Transitions: * copy to idle, when action is done * rename to idle, when action is done * merge to idle, when action is done ****************************** * Action = copy * ****************************** The following table gives the corresponding CLI command for each combination of source and target type. +--------------+----------------------+----------------------+---------------+----------------------+ | \\ Target|fileSystem |runningBinary |runningScript |ftp | |Source \\ | | | | | +--------------+----------------------+----------------------+---------------+----------------------+ |fileSystem |file cp from |file restore |file replace |file cp from | | |SRC |binary-running-config |SRC |SRC | | |TRG |flash | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |techSupport |file cp |-- not legal -- |-- not legal --|file cp | | |technical-support | | |technical-support | | |TRG | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |runningBinary |file backup |-- not legal -- |-- not legal --|file backup | | |binary-running-config | | |binary-running-config | | |flash | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |runningScript |file cp |-- not legal -- |-- not legal --|file cp | | |running-configuration | | |running-configuration | | |TRG | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |ftp |file cp from |file restore |-- not legal --|-- not legal -- | | |FTP_SRC |binary-running-config | | | | |TRG |FTP_SRC | | | +--------------+----------------------+----------------------+---------------+----------------------+ Comments: (a) FTP_SRC denotes ftp://[USER[:PSW]@]ADR[:PORT]/SRC FTP_TRG denotes ftp://[USER[:PSW]@]ADR[:PORT]/TRG (b) SRC, TRG, USER, PSW, ADR and PORT are respectively the values of prvtConfigSourceFileName, prvtConfigTargetFileName, prvtConfigRemoteUser, prvtConfigRemotePassword, prvtConfigRemoteAddress and prvtConfigRemotePort. When any of these are not mentioned in the command, then the value is not relevant. (c) tftp is the same as ftp, except that USER, PSW are not used (d) the error 'inconsistentValue' is returned for any combination marked 'not legal' (e) a successful execution of a copy action when target type is 'runningBinary' (equivalent CLI command is 'file restore binary-running config ...') results in a system reload (f) The above comments are also applicable to the other actions explained below. ****************************** * Action = rename * ****************************** equivalent to CLI command: file mv SRC TRG prvtConfigTargetType and prvtConfigSourceType must equal to 'fileSystem' ****************************** * Action = merge * ****************************** equivalent to CLI command: file merge SRC prvtConfigSourceType must equal 'fileSystem' prvtConfigTargetType must equal 'runningScript' ****************************** * Examples * ****************************** [1] To save the binary of the running configuration to a remote ftp server, with default username, default password, default port, IP = 10.2.144.20, and target file name 'example.bin', the procedure would be (assuming that prvtConfigAction is initially in 'idle' state): set prvtConfigAction <- 'prepare' set prvtConfigSourceType <- 'runningBinary' set prvtConfigTargetType <- 'ftp' set prvtConfigTargetFileName <- 'example.bin' set prvtConfigRemoteAddress <- '10.2.144.20' set prvtConfigAction <- 'copy' [2] To rename a file named 'first.txt' to 'second.txt', the procedure would be (assuming that prvtConfigAction is initially in 'idle' state): set prvtConfigAction <- 'prepare' set prvtConfigSourceType <- 'fileSystem' set prvtConfigTargetType <- 'fileSystem' set prvtConfigSourceFileName <- 'first.txt' set prvtConfigTargetFileName <- 'second.txt' set prvtConfigAction <- 'rename'\"",
    "::=",
    "{",
    "prvtConfigFileAction",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "idle",
            1
          ],
          [
            "prepare",
            2
          ],
          [
            "copy",
            3
          ],
          [
            "rename",
            4
          ],
          [
            "merge",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Represents a file action request to be committed immediately (with set request) or that is being commited (with get request). idle = there is no action being performed or prepared prepare = parameters of an action are being edited. This is used by the manager to willingly avoid editing parameters while another manager does so. copy = copy a file from source to target, where source and target have a broad meaning (local/remote file system or running configuration). See details below. rename = rename a local file (see details below) merge = merge a local file to running configuration Allowed Transitions: * idle to prepare * prepare to any other Automatic Transitions: * copy to idle, when action is done * rename to idle, when action is done * merge to idle, when action is done ****************************** * Action = copy * ****************************** The following table gives the corresponding CLI command for each combination of source and target type. +--------------+----------------------+----------------------+---------------+----------------------+ | \\ Target|fileSystem |runningBinary |runningScript |ftp | |Source \\ | | | | | +--------------+----------------------+----------------------+---------------+----------------------+ |fileSystem |file cp from |file restore |file replace |file cp from | | |SRC |binary-running-config |SRC |SRC | | |TRG |flash | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |techSupport |file cp |-- not legal -- |-- not legal --|file cp | | |technical-support | | |technical-support | | |TRG | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |runningBinary |file backup |-- not legal -- |-- not legal --|file backup | | |binary-running-config | | |binary-running-config | | |flash | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |runningScript |file cp |-- not legal -- |-- not legal --|file cp | | |running-configuration | | |running-configuration | | |TRG | | |FTP_TRG | +--------------+----------------------+----------------------+---------------+----------------------+ |ftp |file cp from |file restore |-- not legal --|-- not legal -- | | |FTP_SRC |binary-running-config | | | | |TRG |FTP_SRC | | | +--------------+----------------------+----------------------+---------------+----------------------+ Comments: (a) FTP_SRC denotes ftp://[USER[:PSW]@]ADR[:PORT]/SRC FTP_TRG denotes ftp://[USER[:PSW]@]ADR[:PORT]/TRG (b) SRC, TRG, USER, PSW, ADR and PORT are respectively the values of prvtConfigSourceFileName, prvtConfigTargetFileName, prvtConfigRemoteUser, prvtConfigRemotePassword, prvtConfigRemoteAddress and prvtConfigRemotePort. When any of these are not mentioned in the command, then the value is not relevant. (c) tftp is the same as ftp, except that USER, PSW are not used (d) the error 'inconsistentValue' is returned for any combination marked 'not legal' (e) a successful execution of a copy action when target type is 'runningBinary' (equivalent CLI command is 'file restore binary-running config ...') results in a system reload (f) The above comments are also applicable to the other actions explained below. ****************************** * Action = rename * ****************************** equivalent to CLI command: file mv SRC TRG prvtConfigTargetType and prvtConfigSourceType must equal to 'fileSystem' ****************************** * Action = merge * ****************************** equivalent to CLI command: file merge SRC prvtConfigSourceType must equal 'fileSystem' prvtConfigTargetType must equal 'runningScript' ****************************** * Examples * ****************************** [1] To save the binary of the running configuration to a remote ftp server, with default username, default password, default port, IP = 10.2.144.20, and target file name 'example.bin', the procedure would be (assuming that prvtConfigAction is initially in 'idle' state): set prvtConfigAction <- 'prepare' set prvtConfigSourceType <- 'runningBinary' set prvtConfigTargetType <- 'ftp' set prvtConfigTargetFileName <- 'example.bin' set prvtConfigRemoteAddress <- '10.2.144.20' set prvtConfigAction <- 'copy' [2] To rename a file named 'first.txt' to 'second.txt', the procedure would be (assuming that prvtConfigAction is initially in 'idle' state): set prvtConfigAction <- 'prepare' set prvtConfigSourceType <- 'fileSystem' set prvtConfigTargetType <- 'fileSystem' set prvtConfigSourceFileName <- 'first.txt' set prvtConfigTargetFileName <- 'second.txt' set prvtConfigAction <- 'rename'"
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.738)

Killim Nahum

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.738.10.111.1.1.2.3.1.1 prvtConfigFileSource22
1.3.6.1.4.1.738.10.111.1.1.2.3.1.2 prvtConfigFileTarget22
1.3.6.1.4.1.738.10.111.1.1.2.3.1.3 prvtConfigFileRemote55
1.3.6.1.4.1.738.10.111.1.1.2.3.1.4 prvtConfigActionSpinLock00