OID reference

atFilev2SourceDevice

1.3.6.1.4.1.207.8.4.4.4.600.3.2

Description

Set to the value representing the source file system to be used for the file operation: 1. Flash 2. Card 3. NVS 4. TFTP 5. USB For copying files, any combination of source and destination file system types may be selected, with the exception of TFTP to TFTP, which is not supported. For moving files, TFTP may not be se…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.207.8.4.4.4.600.3 (atFilev2FileOperation)
Node code
2
Node name
atFilev2SourceDevice
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.207.8.4.4.4.600.3.2
URN notation
urn:oid:1.3.6.1.4.1.207.8.4.4.4.600.3.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 207 8 4 4 4 600 3 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ati(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesis(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) alliedTelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibObjects(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) alliedtelesyn(207) mibobjs(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ati(207) mibObject(8) brouterMib(4) atRouter(4) modules(4) atFilev2(600) atFilev2FileOperation(3) atFilev2SourceDevice(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/207/8/4/4/4/600/3/2
  • /ISO/Identified-Organization/6/1/4/1/207/8/4/4/4/600/3/2
  • /ISO/3/6/1/4/1/207/8/4/4/4/600/3/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/ati/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesis/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprise/alliedTelesyn/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibObjects/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprises/alliedtelesyn/mibobjs/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • /iso/identified-organization/dod/internet/private/enterprises/ati/mibObject/brouterMib/atRouter/modules/atFilev2/atFilev2FileOperation/atFilev2SourceDevice
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER, Integer32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
'1'b

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies

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

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

Value type
Integer32
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
'1'b
Allowed ranges
0–4

Enumerated values

Numbers refer to source variants above. Each value is shown only for variants that define it.

ValueNameSource variants
1flash1
2card1
3nvs1
4tftp1
5usb1

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.207.8.4.4.4.600.3.2.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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

atFilev2SourceDevice · current

atFilev2SourceDevice OBJECT-TYPE
            SYNTAX INTEGER
                {
                flash(1),
                card(2),
                nvs(3),
                tftp(4),
                usb(5)
                }
            MAX-ACCESS read-write
            STATUS current
            DESCRIPTION
                "Set to the value representing the source file system to be
                used for the file operation:

                  1. Flash
                  2. Card
                  3. NVS
                  4. TFTP
                  5. USB

                For copying files, any combination of source and destination
                file system types may be selected, with the exception of TFTP
                to TFTP, which is not supported.

                For moving files, TFTP may not be selected as the source or
                destination file system type.

                For deleting files, the source file system type cannot be TFTP.

                All required parameters must be fully configured before an
                operation can commence. Where a TFTP operation is configured,
                an IP address must also be set via atFilev2TftpIPAddr."
            ::= { atFilev2FileOperation 2 }

atFilev2SourceDevice · current

atFilev2SourceDevice OBJECT-TYPE
			SYNTAX Integer32 (0..4)
			MAX-ACCESS read-write
			STATUS current
			DESCRIPTION
				"Set an integer that corresponds with a device found below:
				
				0. Unconfigured (not settable)
				1. Flash
				2. Card
				3. NVS
				4. TFTP
				
				For copying, you may use any combination of devices for the
				source and destination except for copying from TFTP to TFTP.
				For moving files you cannot use TFTP as source or destination.
				For deleting, the source cannot be TFTP. 
				
				To copy a file from TFTP to flash, use 4 for source and 1 for
				destination.
				
				You must fully configure all required parameters for each
				device. Only TFTP has an IP address required."
			DEFVAL { '1'b }
			::= { atFilev2FileOperation 2 }

Meaning

Descriptions

2 unique

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

Description 1

Set to the value representing the source file system to be used for the file operation: 1. Flash 2. Card 3. NVS 4. TFTP 5. USB For copying files, any combination of source and destination file system types may be selected, with the exception of TFTP to TFTP, which is not supported. For moving files, TFTP may not be selected as the source or destination file system type. For deleting files, the source file system type cannot be TFTP. All required parameters must be fully configured before an operation can commence. Where a TFTP operation is configured, an IP address must also be set via atFilev2TftpIPAddr.

Sources for this description

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

See 1 matching source record

Description 2

Set an integer that corresponds with a device found below: 0. Unconfigured (not settable) 1. Flash 2. Card 3. NVS 4. TFTP For copying, you may use any combination of devices for the source and destination except for copying from TFTP to TFTP. For moving files you cannot use TFTP as source or destination. For deleting, the source cannot be TFTP. To copy a file from TFTP to flash, use 4 for source and 1 for destination. You must fully configure all required parameters for each device. Only TFTP has an IP address required.

Sources for this description

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

See 1 matching source record

Evidence

Source records

2 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), Netdisco MIB archive copies1 record · 2 sources

Description 1

atFilev2SourceDevice · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: atFilev2SourceDevice

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "atFilev2SourceDevice",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "flash",
    "(",
    "1",
    ")",
    ",",
    "card",
    "(",
    "2",
    ")",
    ",",
    "nvs",
    "(",
    "3",
    ")",
    ",",
    "tftp",
    "(",
    "4",
    ")",
    ",",
    "usb",
    "(",
    "5",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Set to the value representing the source file system to be used for the file operation: 1. Flash 2. Card 3. NVS 4. TFTP 5. USB For copying files, any combination of source and destination file system types may be selected, with the exception of TFTP to TFTP, which is not supported. For moving files, TFTP may not be selected as the source or destination file system type. For deleting files, the source file system type cannot be TFTP. All required parameters must be fully configured before an operation can commence. Where a TFTP operation is configured, an IP address must also be set via atFilev2TftpIPAddr.\"",
    "::=",
    "{",
    "atFilev2FileOperation",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "flash",
            1
          ],
          [
            "card",
            2
          ],
          [
            "nvs",
            3
          ],
          [
            "tftp",
            4
          ],
          [
            "usb",
            5
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Set to the value representing the source file system to be used for the file operation: 1. Flash 2. Card 3. NVS 4. TFTP 5. USB For copying files, any combination of source and destination file system types may be selected, with the exception of TFTP to TFTP, which is not supported. For moving files, TFTP may not be selected as the source or destination file system type. For deleting files, the source file system type cannot be TFTP. All required parameters must be fully configured before an operation can commence. Where a TFTP operation is configured, an IP address must also be set via atFilev2TftpIPAddr."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 2

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

Status in source: current.

Names: atFilev2SourceDevice

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "atFilev2SourceDevice",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "(",
    "0",
    ".",
    ".",
    "4",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Set an integer that corresponds with a device found below: 0. Unconfigured (not settable) 1. Flash 2. Card 3. NVS 4. TFTP For copying, you may use any combination of devices for the source and destination except for copying from TFTP to TFTP. For moving files you cannot use TFTP as source or destination. For deleting, the source cannot be TFTP. To copy a file from TFTP to flash, use 4 for source and 1 for destination. You must fully configure all required parameters for each device. Only TFTP has an IP address required.\"",
    "DEFVAL",
    "{",
    "'",
    "1",
    "'",
    "b",
    "}",
    "::=",
    "{",
    "atFilev2FileOperation",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32",
      [
        "integerSubType",
        [
          [
            0,
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Set an integer that corresponds with a device found below: 0. Unconfigured (not settable) 1. Flash 2. Card 3. NVS 4. TFTP For copying, you may use any combination of devices for the source and destination except for copying from TFTP to TFTP. For moving files you cannot use TFTP as source or destination. For deleting, the source cannot be TFTP. To copy a file from TFTP to flash, use 4 for source and 1 for destination. You must fully configure all required parameters for each device. Only TFTP has an IP address required."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "'1'b"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.207)

Scott Holley

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.207.8.4.4.4.600.3.1 atFilev2SourceStackID00
1.3.6.1.4.1.207.8.4.4.4.600.3.3 atFilev2SourceFilename00
1.3.6.1.4.1.207.8.4.4.4.600.3.4 atFilev2DestinationStackID00
1.3.6.1.4.1.207.8.4.4.4.600.3.5 atFilev2DestinationDevice00
1.3.6.1.4.1.207.8.4.4.4.600.3.6 atFilev2DestinationFilename00
1.3.6.1.4.1.207.8.4.4.4.600.3.7 atFilev2CopyBegin00
1.3.6.1.4.1.207.8.4.4.4.600.3.8 atFilev2MoveBegin00
1.3.6.1.4.1.207.8.4.4.4.600.3.9 atFilev2DeleteBegin00
1.3.6.1.4.1.207.8.4.4.4.600.3.10 atFilev2Flash100
1.3.6.1.4.1.207.8.4.4.4.600.3.11 atFilev2Card200
1.3.6.1.4.1.207.8.4.4.4.600.3.12 atFilev2Nvs300
1.3.6.1.4.1.207.8.4.4.4.600.3.13 atFilev2Tftp411
1.3.6.1.4.1.207.8.4.4.4.600.3.14 atFilev2DirOperation77
1.3.6.1.4.1.207.8.4.4.4.600.3.15 atFilev2Usb500