OID reference

copyEntry

1.3.6.1.4.1.3902.3.202.1.1.1.1.1

Description

A config-copy request. A management station wishing to create an entry should first generate a random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row index objects. It __MUST__ in the same PDUs, create an instance of copySourc…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3902.3.202.1.1.1.1 (copyTable)
Node code
1
Node name
copyEntry
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3902.3.202.1.1.1.1.1
URN notation
urn:oid:1.3.6.1.4.1.3902.3.202.1.1.1.1.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3902 3 202 1 1 1 1 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxr10(3) mgmt(202) configCopyMIB(1) configCopyMIBObjects(1) copy(1) copyTable(1) copyEntry(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3902/3/202/1/1/1/1/1
  • /ISO/Identified-Organization/6/1/4/1/3902/3/202/1/1/1/1/1
  • /ISO/3/6/1/4/1/3902/3/202/1/1/1/1/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/3902/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zte/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/enterprises/3902/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zte/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zxEnterpriseMib/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/3902/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/zte/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/identified-organization/dod/internet/private/vendor-objects/zxEnterpriseMib/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/org/dod/internet/private/enterprise/3902/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/org/dod/internet/private/enterprise/zte/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/org/dod/internet/private/enterprise/zxEnterpriseMib/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • /iso/org/dod/internet/private/enterprises/3902/zxr10/mgmt/configCopyMIB/configCopyMIBObjects/copy/copyTable/copyEntry
  • Additional combinations skipped.

SNMP properties

Value type
CopyEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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.

copyEntry OBJECT-TYPE
        SYNTAX CopyEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION                "A config-copy request.

                A management station wishing to create an entry should
                first generate a random serial number to be used
                as the index to this sparse table.  The station should
                then create the associated instance of the row status
                and row index objects.  It __MUST__ in the same PDUs, 
                create an instance of copySourceFileType and copyDestFileType.
                At least one of the FileTypes must be an agent-config
                file type (i.e.        startupConfig or runningConfig).
                If one of the file types is a networkFile, a valid
                copyServerAddress and copyFileName must be
                created as well. For a file type of localFile, only
                a valid fileName needs to be created as an extra 
                parameter.

                It should also modify the default values for the other
                configuration objects if the defaults are not 
                appropriate.
                
                Once the appropriate instance of all the configuration
                objects have been created, the row status will automatically 
                be set to active to initiate the request. Note that this entire
                procedure __MUST__ be initiated via a single set request 
                which specifies a row status of createAndGo as well as
                specifies valid values for the non-defaulted 
                configuration objects.

                Once the config-copy request has been created (i.e. the
                copyEntryRowStatus has been made active), the entry
                cannot be modified - the only operation possible
                after this is to delete the row.

                Once the request completes, the management station 
                should retrieve the values of the status objects of 
                interest, and should then delete the entry.  In order 
                to prevent old entries from clogging the table, 
                entries will be aged out, but an entry will never be 
                deleted within 5 minutes of completing."
        INDEX { copyIndex }
        ::= { copyTable 1 }

Meaning

Descriptions

1 unique

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

A config-copy request. A management station wishing to create an entry should first generate a random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row index objects. It __MUST__ in the same PDUs, create an instance of copySourceFileType and copyDestFileType. At least one of the FileTypes must be an agent-config file type (i.e. startupConfig or runningConfig). If one of the file types is a networkFile, a valid copyServerAddress and copyFileName must be created as well. For a file type of localFile, only a valid fileName needs to be created as an extra parameter. It should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, the row status will automatically be set to active to initiate the request. Note that this entire procedure __MUST__ be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. Once the config-copy request has been created (i.e. the copyEntryRowStatus has been made active), the entry cannot be modified - the only operation possible after this is to delete the row. Once the request completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.

Sources for this description

ZTE 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 1ZTE MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

copyEntry · currentZTE MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: copyEntry

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "copyEntry",
    "OBJECT-TYPE",
    "SYNTAX",
    "CopyEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"A config-copy request. A management station wishing to create an entry should first generate a random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row index objects. It __MUST__ in the same PDUs, create an instance of copySourceFileType and copyDestFileType. At least one of the FileTypes must be an agent-config file type (i.e. startupConfig or runningConfig). If one of the file types is a networkFile, a valid copyServerAddress and copyFileName must be created as well. For a file type of localFile, only a valid fileName needs to be created as an extra parameter. It should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, the row status will automatically be set to active to initiate the request. Note that this entire procedure __MUST__ be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. Once the config-copy request has been created (i.e. the copyEntryRowStatus has been made active), the entry cannot be modified - the only operation possible after this is to delete the row. Once the request completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing.\"",
    "INDEX",
    "{",
    "copyIndex",
    "}",
    "::=",
    "{",
    "copyTable",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "CopyEntry"
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "A config-copy request. A management station wishing to create an entry should first generate a random serial number to be used as the index to this sparse table. The station should then create the associated instance of the row status and row index objects. It __MUST__ in the same PDUs, create an instance of copySourceFileType and copyDestFileType. At least one of the FileTypes must be an agent-config file type (i.e. startupConfig or runningConfig). If one of the file types is a networkFile, a valid copyServerAddress and copyFileName must be created as well. For a file type of localFile, only a valid fileName needs to be created as an extra parameter. It should also modify the default values for the other configuration objects if the defaults are not appropriate. Once the appropriate instance of all the configuration objects have been created, the row status will automatically be set to active to initiate the request. Note that this entire procedure __MUST__ be initiated via a single set request which specifies a row status of createAndGo as well as specifies valid values for the non-defaulted configuration objects. Once the config-copy request has been created (i.e. the copyEntryRowStatus has been made active), the entry cannot be modified - the only operation possible after this is to delete the row. Once the request completes, the management station should retrieve the values of the status objects of interest, and should then delete the entry. In order to prevent old entries from clogging the table, entries will be aged out, but an entry will never be deleted within 5 minutes of completing."
    ],
    null,
    null,
    [
      "INDEX",
      [
        [
          0,
          "copyIndex"
        ]
      ]
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.3902)

Xianlin Luo

Direct children (15)