Reference record for OID 1.3.6.1.2.1.69.1.4.1


parent
1.3.6.1.2.1.69.1.4 (docsDevServer)
node code
1
node name
docsDevServerBootState
dot oid
1.3.6.1.2.1.69.1.4.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) docsDev(69) docsDevMIBObjects(1) docsDevServer(4) docsDevServerBootState(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) docsDev(69) docsDevMIBObjects(1) docsDevServer(4) docsDevServerBootState(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) docsDev(69) docsDevMIBObjects(1) docsDevServer(4) docsDevServerBootState(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) docsDev(69) docsDevMIBObjects(1) docsDevServer(4) docsDevServerBootState(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) docsDev(69) docsDevMIBObjects(1) docsDevServer(4) docsDevServerBootState(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) docsDev(69) docsDevMIBObjects(1) docsDevServer(4) docsDevServerBootState(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/docsDev/docsDevMIBObjects/docsDevServer/docsDevServerBootState
  • /iso/identified-organization/dod/internet/mgmt/mib/docsDev/docsDevMIBObjects/docsDevServer/docsDevServerBootState
  • /iso/org/dod/internet/mgmt/mib-2/docsDev/docsDevMIBObjects/docsDevServer/docsDevServerBootState
  • /iso/org/dod/internet/mgmt/mib/docsDev/docsDevMIBObjects/docsDevServer/docsDevServerBootState
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/docsDev/docsDevMIBObjects/docsDevServer/docsDevServerBootState
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/docsDev/docsDevMIBObjects/docsDevServer/docsDevServerBootState
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/69/1/4/1

    Description by circitor

    If operational(1), the device has completed loading and
    processing of configuration parameters and the CMTS has
    completed the Registration exchange.
    If disabled(2) then the device was administratively
    disabled, possibly by being refused network access in the
    configuration file.
    If waitingForDhcpOffer(3) then a DHCP Discover has been
    transmitted and no offer has yet been received.
    If waitingForDhcpResponse(4) then a DHCP Request has been
    transmitted and no response has yet been received.
    If waitingForTimeServer(5) then a Time Request has been
    transmitted and no response has yet been received.
    If waitingForTftp(6) then a request to the TFTP parameter
    server has been made and no response received.
    If refusedByCmts(7) then the Registration Request/Response
    exchange with the CMTS failed.
    If forwardingDenied(8) then the registration process
    completed, but the network access option in the received
    configuration file prohibits forwarding.

    Parsed from file DOCS-CABLE-DEVICE-MIB.mib
    Module: DOCS-CABLE-DEVICE-MIB

    Description by cisco_v1

    If operational(1), the device has completed loading and
    processing of configuration parameters, and the CMTS has
    completed the Registration exchange.

    If disabled(2), then the device was administratively
    disabled, possibly by being refused network access in
    the configuration file.

    If waitingForDhcpOffer(3), then a Dynamic Host
    Configuration Protocol (DHCP) Discover has been
    transmitted, and no offer has yet been received.

    If waitingForDhcpResponse(4), then a DHCP Request has
    been transmitted, and no response has yet been received.

    If waitingForTimeServer(5), then a Time Request has been
    transmitted, and no response has yet been received.

    If waitingForTftp(6), then a request to the TFTP
    parameter server has been made, and no response
    received.

    If refusedByCmts(7), then the Registration
    Request/Response exchange with the CMTS failed.

    If forwardingDenied(8), then the registration process
    was completed, but the network access option in the
    received configuration file prohibits forwarding.

    If other(9), then the registration process reached a
    point that does not fall into one of the above
    categories.

    If unknown(10), then the device has not yet begun the
    registration process or is in some other indeterminate
    state.

    Description by oid_info

    docsDevServerBootState OBJECT-TYPE
    SYNTAX INTEGER {
    operational(1),
    disabled(2),
    waitingForDhcpOffer(3),
    waitingForDhcpResponse(4),
    waitingForTimeServer(5),
    waitingForTftp(6),
    refusedByCmts(7),
    forwardingDenied(8),
    other(9),
    unknown(10)
    }
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
    "If operational(1), the device has completed loading and
    processing of configuration parameters and the CMTS has
    completed the Registration exchange.
    If disabled(2) then the device was administratively
    disabled, possibly by being refused network access in the
    configuration file.
    If waitingForDhcpOffer(3) then a DHCP Discover has been
    transmitted and no offer has yet been received.
    If waitingForDhcpResponse(4) then a DHCP Request has been
    transmitted and no response has yet been received.
    If waitingForTimeServer(5) then a Time Request has been
    transmitted and no response has yet been received.
    If waitingForTftp(6) then a request to the TFTP parameter
    server has been made and no response received.
    If refusedByCmts(7) then the Registration Request/Response
    exchange with the CMTS failed.
    If forwardingDenied(8) then the registration process
    completed, but the network access option in the received
    configuration file prohibits forwarding. "
    REFERENCE
    "DOCSIS Radio Frequency Interface Specification, Figure
    7-1, CM Initialization Overview."

    View at oid-info.com

    Description by mibdepot

    If operational(1), the device has completed loading and
    processing of configuration parameters, and the CMTS has
    completed the Registration exchange.

    If disabled(2), then the device was administratively
    disabled, possibly by being refused network access in
    the configuration file.

    If waitingForDhcpOffer(3), then a Dynamic Host
    Configuration Protocol (DHCP) Discover has been
    transmitted, and no offer has yet been received.

    If waitingForDhcpResponse(4), then a DHCP Request has
    been transmitted, and no response has yet been received.

    If waitingForTimeServer(5), then a Time Request has been
    transmitted, and no response has yet been received.

    If waitingForTftp(6), then a request to the TFTP
    parameter server has been made, and no response
    received.

    If refusedByCmts(7), then the Registration
    Request/Response exchange with the CMTS failed.

    If forwardingDenied(8), then the registration process
    was completed, but the network access option in the
    received configuration file prohibits forwarding.

    If other(9), then the registration process reached a
    point that does not fall into one of the above
    categories.

    If unknown(10), then the device has not yet begun the
    registration process or is in some other indeterminate
    state.

    Parsed from file rfc4639-DOCSIS-Cable-Device.mib.txt
    Company: None
    Module: DOCS-CABLE-DEVICE-MIB

    Description by cisco

    If operational(1), the device has completed loading and
    processing of configuration parameters, and the CMTS has
    completed the Registration exchange.

    If disabled(2), then the device was administratively
    disabled, possibly by being refused network access in
    the configuration file.

    If waitingForDhcpOffer(3), then a Dynamic Host
    Configuration Protocol (DHCP) Discover has been
    transmitted, and no offer has yet been received.

    If waitingForDhcpResponse(4), then a DHCP Request has
    been transmitted, and no response has yet been received.

    If waitingForTimeServer(5), then a Time Request has been
    transmitted, and no response has yet been received.

    If waitingForTftp(6), then a request to the TFTP
    parameter server has been made, and no response
    received.

    If refusedByCmts(7), then the Registration
    Request/Response exchange with the CMTS failed.

    If forwardingDenied(8), then the registration process
    was completed, but the network access option in the
    received configuration file prohibits forwarding.

    If other(9), then the registration process reached a
    point that does not fall into one of the above
    categories.

    If unknown(10), then the device has not yet begun the
    registration process or is in some other indeterminate
    state.

    Information by circitor

    docsDevServerBootState OBJECT-TYPE SYNTAX INTEGER { operational(1), disabled(2), waitingForDhcpOffer(3), waitingForDhcpResponse(4), waitingForTimeServer(5), waitingForTftp(6), refusedByCmts(7), forwardingDenied(8), other(9), unknown(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "If operational(1), the device has completed loading and processing of configuration parameters and the CMTS has completed the Registration exchange. If disabled(2) then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3) then a DHCP Discover has been transmitted and no offer has yet been received. If waitingForDhcpResponse(4) then a DHCP Request has been transmitted and no response has yet been received. If waitingForTimeServer(5) then a Time Request has been transmitted and no response has yet been received. If waitingForTftp(6) then a request to the TFTP parameter server has been made and no response received. If refusedByCmts(7) then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8) then the registration process completed, but the network access option in the received configuration file prohibits forwarding. " REFERENCE "DOCSIS Radio Frequency Interface Specification, Figure 7-1, CM Initialization Overview." ::= { docsDevServer 1 }

    Information by cisco_v1

    docsDevServerBootState OBJECT-TYPE SYNTAX INTEGER { operational(1), disabled(2), waitingForDhcpOffer(3), waitingForDhcpResponse(4), waitingForTimeServer(5), waitingForTftp(6), refusedByCmts(7), forwardingDenied(8), other(9) } ACCESS read-only STATUS mandatory DESCRIPTION "If operational(1), the device has completed loading and processing of configuration parameters, and the CMTS has completed the Registration exchange. If disabled(2), then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3), then a Dynamic Host Configuration Protocol (DHCP) Discover has been transmitted, and no offer has yet been received. If waitingForDhcpResponse(4), then a DHCP Request has been transmitted, and no response has yet been received. If waitingForTimeServer(5), then a Time Request has been transmitted, and no response has yet been received. If waitingForTftp(6), then a request to the TFTP parameter server has been made, and no response received. If refusedByCmts(7), then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8), then the registration process was completed, but the network access option in the received configuration file prohibits forwarding. If other(9), then the registration process reached a point that does not fall into one of the above categories. If unknown(10), then the device has not yet begun the registration process or is in some other indeterminate state." REFERENCE "DOCSIS RFI 1.0 Specification, Figure 7-1, and DOCSIS RFI 1.1 Specification, Figure 9-1 and DOCSIS RFI 2.0 Specification, Figure 11-1." ::= { docsDevServer 1 }

    Information by oid_info

    Automatically extracted from RFC2669

    Information by mibdepot

    docsDevServerBootState OBJECT-TYPE SYNTAX INTEGER { operational(1), disabled(2), waitingForDhcpOffer(3), waitingForDhcpResponse(4), waitingForTimeServer(5), waitingForTftp(6), refusedByCmts(7), forwardingDenied(8), other(9), unknown(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "If operational(1), the device has completed loading and processing of configuration parameters, and the CMTS has completed the Registration exchange. If disabled(2), then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3), then a Dynamic Host Configuration Protocol (DHCP) Discover has been transmitted, and no offer has yet been received. If waitingForDhcpResponse(4), then a DHCP Request has been transmitted, and no response has yet been received. If waitingForTimeServer(5), then a Time Request has been transmitted, and no response has yet been received. If waitingForTftp(6), then a request to the TFTP parameter server has been made, and no response received. If refusedByCmts(7), then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8), then the registration process was completed, but the network access option in the received configuration file prohibits forwarding. If other(9), then the registration process reached a point that does not fall into one of the above categories. If unknown(10), then the device has not yet begun the registration process or is in some other indeterminate state." REFERENCE "DOCSIS RFI 1.0 Specification, Figure 7-1, and DOCSIS RFI 1.1 Specification, Figure 9-1 and DOCSIS RFI 2.0 Specification, Figure 11-1." ::= { docsDevServer 1 }

    Information by cisco

    docsDevServerBootState OBJECT-TYPE SYNTAX INTEGER { operational(1), disabled(2), waitingForDhcpOffer(3), waitingForDhcpResponse(4), waitingForTimeServer(5), waitingForTftp(6), refusedByCmts(7), forwardingDenied(8), other(9), unknown(10) } MAX-ACCESS read-only STATUS current DESCRIPTION "If operational(1), the device has completed loading and processing of configuration parameters, and the CMTS has completed the Registration exchange. If disabled(2), then the device was administratively disabled, possibly by being refused network access in the configuration file. If waitingForDhcpOffer(3), then a Dynamic Host Configuration Protocol (DHCP) Discover has been transmitted, and no offer has yet been received. If waitingForDhcpResponse(4), then a DHCP Request has been transmitted, and no response has yet been received. If waitingForTimeServer(5), then a Time Request has been transmitted, and no response has yet been received. If waitingForTftp(6), then a request to the TFTP parameter server has been made, and no response received. If refusedByCmts(7), then the Registration Request/Response exchange with the CMTS failed. If forwardingDenied(8), then the registration process was completed, but the network access option in the received configuration file prohibits forwarding. If other(9), then the registration process reached a point that does not fall into one of the above categories. If unknown(10), then the device has not yet begun the registration process or is in some other indeterminate state." REFERENCE "DOCSIS RFI 1.0 Specification, Figure 7-1, and DOCSIS RFI 1.1 Specification, Figure 9-1 and DOCSIS RFI 2.0 Specification, Figure 11-1." ::= { docsDevServer 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.69.1.4.1.0 docsDevServerBootState 0 0 None

    Brothers (10)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.69.1.4.2 docsDevServerDhcp 1 1 The IP address of the DHCP server that assigned an IP
    address to this device. Returns 0.0.0.0 if DHCP was not
    used for IP address…
    1.3.6.1.2.1.69.1.4.3 docsDevServerTime 1 1 The IP address of the Time server (RFC-868). Returns
    0.0.0.0 if the time server IP address is unknown, or if
    the time server was …
    1.3.6.1.2.1.69.1.4.4 docsDevServerTftp 1 1 The IP address of the TFTP server responsible for
    downloading provisioning and configuration parameters
    to this device. Returns 0…
    1.3.6.1.2.1.69.1.4.5 docsDevServerConfigFile 1 1 The name of the device configuration file read from the
    TFTP server. Returns an empty string if the configuration
    file name is un…
    1.3.6.1.2.1.69.1.4.6 docsDevServerDhcpAddressType, docsDevServerDhcpAddress 1 1 The type of address of docsDevServerDhcpAddress. If
    DHCP was not used, this value should return
    unknown(0).
    1.3.6.1.2.1.69.1.4.7 docsDevServerDhcpAddress, docsDevServerTimeAddress 1 1 The IP V4 or V6 address of the Time server
    (RFC-868). Returns the zero length octet string if the time
    server IP address is unkno…
    1.3.6.1.2.1.69.1.4.8 docsDevServerTimeAddressType, docsDevServerConfigTftpAddress 1 1 The type of address of docsDevServerTimeAddress. If
    no time server exists, this value should return
    unknown(0).
    1.3.6.1.2.1.69.1.4.9 docsDevServerTimeAddress 1 1 The Internet address of the RFC 868 Time server,
    as provided by DHCP option 4.

    Note that if multiple values are provided to the
    CM…
    1.3.6.1.2.1.69.1.4.10 docsDevServerConfigTftpAddressType 1 1 The type of address of docsDevServerConfigTftpAddress.
    If no TFTP server exists, this value should return
    unknown(0).
    1.3.6.1.2.1.69.1.4.11 docsDevServerConfigTftpAddress 1 1 The internet address of the TFTP server responsible for
    downloading provisioning and configuration parameters
    to this device. Re…