Reference record for OID 1.3.6.1.4.1.1795.2.24.2.10.7.1.1



parent
1.3.6.1.4.1.1795.2.24.2.10.7.1 (devFileXferConfigTable)
node code
1
node name
devFileXferConfigEntry
dot oid
1.3.6.1.4.1.1795.2.24.2.10.7.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) pdyn(1795) pdn-mgmt(2) paradyne(24) pdn-common(2) pdn-control(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) pdyn(1795) pdn-mgmt(2) paradyne(24) pdn-common(2) pdnControl(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) thenewpdn(1795) thenewpdn-mgmt(2) paradyne(24) pdn-common(2) pdn-control(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) thenewpdn(1795) thenewpdn-mgmt(2) paradyne(24) pdn-common(2) pdnControl(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) pdyn(1795) pdn-mgmt(2) paradyne(24) pdn-common(2) pdn-control(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) pdyn(1795) pdn-mgmt(2) paradyne(24) pdn-common(2) pdnControl(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) thenewpdn(1795) thenewpdn-mgmt(2) paradyne(24) pdn-common(2) pdn-control(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) thenewpdn(1795) thenewpdn-mgmt(2) paradyne(24) pdn-common(2) pdnControl(10) devFileXferMIBObjects(7) devFileXferConfigTable(1) devFileXferConfigEntry(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/pdyn/pdn-mgmt/paradyne/pdn-common/pdn-control/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • /iso/identified-organization/dod/internet/private/enterprise/pdyn/pdn-mgmt/paradyne/pdn-common/pdnControl/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • ...skipped...
  • /iso/org/dod/internet/private/enterprise/thenewpdn/thenewpdn-mgmt/paradyne/pdn-common/pdn-control/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • /iso/org/dod/internet/private/enterprise/thenewpdn/thenewpdn-mgmt/paradyne/pdn-common/pdnControl/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • /iso/org/dod/internet/private/enterprises/pdyn/pdn-mgmt/paradyne/pdn-common/pdn-control/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • /iso/org/dod/internet/private/enterprises/pdyn/pdn-mgmt/paradyne/pdn-common/pdnControl/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/private/enterprises/thenewpdn/thenewpdn-mgmt/paradyne/pdn-common/pdn-control/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • /iso/iso-identified-organization/dod/internet/private/enterprises/thenewpdn/thenewpdn-mgmt/paradyne/pdn-common/pdnControl/devFileXferMIBObjects/devFileXferConfigTable/devFileXferConfigEntry
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/1795/2/24/2/10/7/1/1

    Description by mibdepot

    Use of the File Tranfer MIB could be used with other MIBS in
    the following manner:
    a) Use another MIB/means to verify available space /make room
    for a file to be transfered to this device
    b) Use this MIB to download the file
    c) Use another MIB/means to select the file you want to make
    active
    if your selecting firmware for example.
    d) Use another MIB/means to reset the device.

    A management station wishing to initiate a file transfer needs to
    create an entry in this table. To do so, you must
    first identify the ifIndex of the device you intend to
    do the transfer with. You should
    then create the associated instance of the row status
    It must also, either in the same
    or in successive PDUs, create an instance of
    devFileXferFileName, DevFileXferFileType,
    . devFileXferServerIpAddress,
    devFileXferOperation.

    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, either by an explicit SNMP
    set request or by default, the row status should be set
    to active to initiate the request. Note that this entire
    procedure may 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 DevFileXferConfigEntry request has been created (i.e. the
    devFileXferRowStatus 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 could be aged out,
    but an entry will never be deleted within 5 minutes of
    completing.

    Parsed from file pdn_control.mib.txt
    Company: None
    Module: PDN-CONTROL-MIB

    Description by circitor

    Use of the File Tranfer MIB could be used with other MIBS in
    the following manner:
    a) Use another MIB/means to verify available space /make room
    for a file to be transfered to this device
    b) Use this MIB to download the file
    c) Use another MIB/means to select the file you want to make
    active
    if your selecting firmware for example.
    d) Use another MIB/means to reset the device.

    A management station wishing to initiate a file transfer needs to
    create an entry in this table. To do so, you must
    first identify the ifIndex of the device you intend to
    do the transfer with. You should
    then create the associated instance of the row status
    It must also, either in the same
    or in successive PDUs, create an instance of
    devFileXferFileName, DevFileXferFileType,
    . devFileXferServerIpAddress,
    devFileXferOperation.

    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, either by an explicit SNMP
    set request or by default, the row status should be set
    to active to initiate the request. Note that this entire
    procedure may 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 DevFileXferConfigEntry request has been created (i.e. the
    devFileXferRowStatus 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 could be aged out,
    but an entry will never be deleted within 5 minutes of
    completing.

    Parsed from file PDN-CONTROL-MIB.mib
    Module: PDN-CONTROL-MIB

    Information by oid_info

    Vendor: Paradyne
    Module: PDN-CONTROL-MIB

    [Automatically extracted from oidview.com]

    Information by mibdepot

    devFileXferConfigEntry OBJECT-TYPE SYNTAX DevFileXferConfigEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION " Use of the File Tranfer MIB could be used with other MIBS in the following manner: a) Use another MIB/means to verify available space /make room for a file to be transfered to this device b) Use this MIB to download the file c) Use another MIB/means to select the file you want to make active if your selecting firmware for example. d) Use another MIB/means to reset the device. A management station wishing to initiate a file transfer needs to create an entry in this table. To do so, you must first identify the ifIndex of the device you intend to do the transfer with. You should then create the associated instance of the row status It must also, either in the same or in successive PDUs, create an instance of devFileXferFileName, DevFileXferFileType, . devFileXferServerIpAddress, devFileXferOperation. 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, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may 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 DevFileXferConfigEntry request has been created (i.e. the devFileXferRowStatus 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 could be aged out, but an entry will never be deleted within 5 minutes of completing. " INDEX { ifIndex } ::= { devFileXferConfigTable 1 }

    Information by circitor

    devFileXferConfigEntry OBJECT-TYPE SYNTAX DevFileXferConfigEntry ACCESS not-accessible STATUS mandatory DESCRIPTION " Use of the File Tranfer MIB could be used with other MIBS in the following manner: a) Use another MIB/means to verify available space /make room for a file to be transfered to this device b) Use this MIB to download the file c) Use another MIB/means to select the file you want to make active if your selecting firmware for example. d) Use another MIB/means to reset the device. A management station wishing to initiate a file transfer needs to create an entry in this table. To do so, you must first identify the ifIndex of the device you intend to do the transfer with. You should then create the associated instance of the row status It must also, either in the same or in successive PDUs, create an instance of devFileXferFileName, DevFileXferFileType, . devFileXferServerIpAddress, devFileXferOperation. 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, either by an explicit SNMP set request or by default, the row status should be set to active to initiate the request. Note that this entire procedure may 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 DevFileXferConfigEntry request has been created (i.e. the devFileXferRowStatus 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 could be aged out, but an entry will never be deleted within 5 minutes of completing. " INDEX { ifIndex } ::= { devFileXferConfigTable 1 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.1795)

    Baughman Kevin

    Children (17)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.1 devFileXferFileName 0 0 This object contains the name of the filetransfer file.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.2 devFileXferCopyProtocol 0 0 The transfer protocol that should be used to copy the file
    across the network. If the file transfer is to occur locally on the
    SN…
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.3 devFileXferFileType 0 0 Specifies the type of file your want to transfer.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.4 devFileXferServerIpAddress 0 0 This object contains the file transfer server's IP address.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.5 devFileXferUserName 0 0 This object contains the username if a username is needed
    to login to the server.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.6 devFileXferUserPassword 0 0 This object contains the password if a password is needed
    to login to the server. This object will return null on a read
    operatio…
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.7 devFileXferOperation 0 0 This object contains the operation the file transfer wants to
    perform.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.8 devFileXferPktsSent 0 0 This object contains the the number of packets sent to the
    server at the time of interrogation.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.9 devFileXferPktsRecv 0 0 This object contains the the number of packets received from the
    server at the time of interrogation.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.10 devFileXferOctetsSent 0 0 This object contains the the number of octets sent to the
    server at the time of interrogation.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.11 devFileXferOctetsRecv 0 0 This object contains the the number of octets received from the
    server at the time of interrogation.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.12 devFileXferOwnerString 0 0 The entity which currently has the 'ownership'
    required to invoke the operation on this index.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.13 devFileXferStatus 0 0 This object contains the status of the file transfer.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.14 devFileXferErrorStatus 0 0 This object contains the reason code of the failure determined in
    devFileXferStatus.
    The reason code are specific to the file tra…
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.15 devFileXferSendEvent 0 0 This object indicates whether or not to send the
    devFileXferEvent event trap .
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.16 devFileXferRowStatus 0 0 This object is used to create
    a new row or delete an
    existing row in this table.
    1.3.6.1.4.1.1795.2.24.2.10.7.1.1.17 devFileXferXferTime 0 0 This object indicates the elapsed time
    (in hundredths of a second) of the file transfer.