Reference record for OID 1.3.6.1.2.1.34.8.1.1.1.7



parent
1.3.6.1.2.1.34.8.1.1.1 (tn3270eSrvrConfEntry)
node code
7
node name
tn3270eSrvrConfAdminStatus
dot oid
1.3.6.1.2.1.34.8.1.1.1.7
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snanauMIB(34) tn3270eMIB(8) tn3270eObjects(1) tn3270eSrvrConfTable(1) tn3270eSrvrConfEntry(1) tn3270eSrvrConfAdminStatus(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) snanauMIB(34) tn3270eMIB(8) tn3270eObjects(1) tn3270eSrvrConfTable(1) tn3270eSrvrConfEntry(1) tn3270eSrvrConfAdminStatus(7)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) snanauMIB(34) tn3270eMIB(8) tn3270eObjects(1) tn3270eSrvrConfTable(1) tn3270eSrvrConfEntry(1) tn3270eSrvrConfAdminStatus(7)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) snanauMIB(34) tn3270eMIB(8) tn3270eObjects(1) tn3270eSrvrConfTable(1) tn3270eSrvrConfEntry(1) tn3270eSrvrConfAdminStatus(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snanauMIB(34) tn3270eMIB(8) tn3270eObjects(1) tn3270eSrvrConfTable(1) tn3270eSrvrConfEntry(1) tn3270eSrvrConfAdminStatus(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) snanauMIB(34) tn3270eMIB(8) tn3270eObjects(1) tn3270eSrvrConfTable(1) tn3270eSrvrConfEntry(1) tn3270eSrvrConfAdminStatus(7)}
    • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/snanauMIB/tn3270eMIB/tn3270eObjects/tn3270eSrvrConfTable/tn3270eSrvrConfEntry/tn3270eSrvrConfAdminStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/snanauMIB/tn3270eMIB/tn3270eObjects/tn3270eSrvrConfTable/tn3270eSrvrConfEntry/tn3270eSrvrConfAdminStatus
  • /iso/org/dod/internet/mgmt/mib-2/snanauMIB/tn3270eMIB/tn3270eObjects/tn3270eSrvrConfTable/tn3270eSrvrConfEntry/tn3270eSrvrConfAdminStatus
  • /iso/org/dod/internet/mgmt/mib/snanauMIB/tn3270eMIB/tn3270eObjects/tn3270eSrvrConfTable/tn3270eSrvrConfEntry/tn3270eSrvrConfAdminStatus
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/snanauMIB/tn3270eMIB/tn3270eObjects/tn3270eSrvrConfTable/tn3270eSrvrConfEntry/tn3270eSrvrConfAdminStatus
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/snanauMIB/tn3270eMIB/tn3270eObjects/tn3270eSrvrConfTable/tn3270eSrvrConfEntry/tn3270eSrvrConfAdminStatus
    • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/34/8/1/1/1/7

    Description by circitor

    The desired state of the TN3270E server represented
    by this entry in the table:

    up(1) - Activate this TN3270E server.
    down(2) - Informs the associated TN3270E
    server to gracefully terminate
    its processing.
    stopImmediate(3) - Informs the associated TN3270E
    server to terminate itself
    immediately.

    When a managed system creates an entry in this table,
    tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
    are initialized as up(1) by default.

    The exact behavior of a server in response to a down(2)
    or stopImmediate(3) command is left implementation-
    dependent. A TN3270E server that is capable of it
    SHOULD close all of its TN3270 and TN3270E sessions
    during a graceful termination.

    Often the function enabled via stopImmediate(3) is used
    as a last resort by a system administrator, to attempt
    to either bring down a hung TN3270E server or free up
    its resources immediately to aid in general system
    availability, or to shut down a TN3270E server that is
    not recognizing a down(2) request.

    A TN3270E server that does not distinguish between
    down(2) or stopImmediate(3) transitions should not
    support stopImmediate(3).

    Parsed from file TN3270E-MIB.mib
    Module: TN3270E-MIB

    Description by cisco_v1

    The desired state of the TN3270E server represented
    by this entry in the table:

    up(1) - Activate this TN3270E server.
    down(2) - Informs the associated TN3270E
    server to gracefully terminate
    its processing.
    stopImmediate(3) - Informs the associated TN3270E
    server to terminate itself
    immediately.

    When a managed system creates an entry in this table,
    tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
    are initialized as up(1) by default.

    The exact behavior of a server in response to a down(2)
    or stopImmediate(3) command is left implementation-
    dependent. A TN3270E server that is capable of it
    SHOULD close all of its TN3270 and TN3270E sessions
    during a graceful termination.

    Often the function enabled via stopImmediate(3) is used
    as a last resort by a system administrator, to attempt
    to either bring down a hung TN3270E server or free up
    its resources immediately to aid in general system
    availability, or to shut down a TN3270E server that is
    not recognizing a down(2) request.

    A TN3270E server that does not distinguish between
    down(2) or stopImmediate(3) transitions should not
    support stopImmediate(3).

    Description by oid_info

    tn3270eSrvrConfAdminStatus OBJECT-TYPE
    SYNTAX INTEGER {
    up(1),
    down(2),
    stopImmediate(3)
    }
    MAX-ACCESS read-create
    STATUS current
    DESCRIPTION
    "The desired state of the TN3270E server represented
    by this entry in the table:
    up(1) - Activate this TN3270E server.
    down(2) - Informs the associated TN3270E
    server to gracefully terminate
    its processing.
    stopImmediate(3) - Informs the associated TN3270E
    server to terminate itself
    immediately.
    When a managed system creates an entry in this table,
    tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
    are initialized as up(1) by default.
    The exact behavior of a server in response to a down(2)
    or stopImmediate(3) command is left implementation-
    dependent. A TN3270E server that is capable of it
    SHOULD close all of its TN3270 and TN3270E sessions
    during a graceful termination.
    Often the function enabled via stopImmediate(3) is used
    as a last resort by a system administrator, to attempt
    to either bring down a hung TN3270E server or free up
    its resources immediately to aid in general system
    availability, or to shut down a TN3270E server that is
    not recognizing a down(2) request.
    A TN3270E server that does not distinguish between
    down(2) or stopImmediate(3) transitions should not
    support stopImmediate(3)."
    DEFVAL { up }
    View at oid-info.com

    Description by mibdepot

    The desired state of the TN3270E server represented
    by this entry in the table:

    up(1) - Activate this TN3270E server.
    down(2) - Informs the associated TN3270E
    server to gracefully terminate
    its processing.
    stopImmediate(3) - Informs the associated TN3270E
    server to terminate itself
    immediately.

    When a managed system creates an entry in this table,
    tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
    are initialized as up(1) by default.

    The exact behavior of a server in response to a down(2)
    or stopImmediate(3) command is left implementation-

    dependent. A TN3270E server that is capable of it
    SHOULD close all of its TN3270 and TN3270E sessions
    during a graceful termination.

    Often the function enabled via stopImmediate(3) is used
    as a last resort by a system administrator, to attempt
    to either bring down a hung TN3270E server or free up
    its resources immediately to aid in general system
    availability, or to shut down a TN3270E server that is
    not recognizing a down(2) request.

    A TN3270E server that does not distinguish between
    down(2) or stopImmediate(3) transitions should not
    support stopImmediate(3).

    Parsed from file rfc2561-TN3270E.mib.txt
    Company: None
    Module: TN3270E-MIB

    Description by cisco

    The desired state of the TN3270E server represented
    by this entry in the table:

    up(1) - Activate this TN3270E server.
    down(2) - Informs the associated TN3270E
    server to gracefully terminate
    its processing.
    stopImmediate(3) - Informs the associated TN3270E
    server to terminate itself
    immediately.

    When a managed system creates an entry in this table,
    tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
    are initialized as up(1) by default.

    The exact behavior of a server in response to a down(2)
    or stopImmediate(3) command is left implementation-
    dependent. A TN3270E server that is capable of it
    SHOULD close all of its TN3270 and TN3270E sessions
    during a graceful termination.

    Often the function enabled via stopImmediate(3) is used
    as a last resort by a system administrator, to attempt
    to either bring down a hung TN3270E server or free up
    its resources immediately to aid in general system
    availability, or to shut down a TN3270E server that is
    not recognizing a down(2) request.

    A TN3270E server that does not distinguish between
    down(2) or stopImmediate(3) transitions should not
    support stopImmediate(3).

    Information by circitor

    tn3270eSrvrConfAdminStatus OBJECT-TYPE
      SYNTAX  INTEGER {
                        up(1),
                        down(2),
                        stopImmediate(3)
                      }
      MAX-ACCESS  read-create
      STATUS      current
      DESCRIPTION
          "The desired state of the TN3270E server represented
           by this entry in the table:

           up(1)            - Activate this TN3270E server.
           down(2)          - Informs the associated TN3270E
                              server to gracefully terminate
                              its processing.
           stopImmediate(3) - Informs the associated TN3270E
                              server to terminate itself
                              immediately.

           When a managed system creates an entry in this table,
           tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
           are initialized as up(1) by default.

           The exact behavior of a server in response to a down(2)
           or stopImmediate(3) command is left implementation-
           dependent.  A TN3270E server that is capable of it
           SHOULD close all of its TN3270 and TN3270E sessions
           during a graceful termination.

           Often the function enabled via stopImmediate(3) is used
           as a last resort by a system administrator, to attempt
           to either bring down a hung TN3270E server or free up
           its resources immediately to aid in general system
           availability, or to shut down a TN3270E server that is
           not recognizing a down(2) request.

           A TN3270E server that does not distinguish between
           down(2) or stopImmediate(3) transitions should not
           support stopImmediate(3)."
      DEFVAL { up }
      ::= { tn3270eSrvrConfEntry 7 }

    Information by cisco_v1

    tn3270eSrvrConfAdminStatus OBJECT-TYPE
    SYNTAX INTEGER {
        up(1),
        down(2),
        stopImmediate(3)
        }
    ACCESS read-write
    STATUS mandatory
    DESCRIPTION
        "The desired state of the TN3270E server represented
         by this entry in the table:
        
         up(1)            - Activate this TN3270E server.
         down(2)          - Informs the associated TN3270E
                            server to gracefully terminate
                            its processing.
         stopImmediate(3) - Informs the associated TN3270E
                            server to terminate itself
                            immediately.
        
         When a managed system creates an entry in this table,
         tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
         are initialized as up(1) by default.
        
         The exact behavior of a server in response to a down(2)
         or stopImmediate(3) command is left implementation-
         dependent.  A TN3270E server that is capable of it
         SHOULD close all of its TN3270 and TN3270E sessions
         during a graceful termination.
        
         Often the function enabled via stopImmediate(3) is used
         as a last resort by a system administrator, to attempt
         to either bring down a hung TN3270E server or free up
         its resources immediately to aid in general system
         availability, or to shut down a TN3270E server that is
         not recognizing a down(2) request.
        
         A TN3270E server that does not distinguish between
         down(2) or stopImmediate(3) transitions should not
         support stopImmediate(3)."
    DEFVAL { up }
    ::= { tn3270eSrvrConfEntry 7 }

    Information by oid_info

    Automatically extracted from Cisco "SNMP v2 MIBs".

    Information by mibdepot

    tn3270eSrvrConfAdminStatus OBJECT-TYPE
      SYNTAX  INTEGER {
                        up(1),
                        down(2),
                        stopImmediate(3)
                      }
      MAX-ACCESS  read-create
      STATUS      current
      DESCRIPTION
          "The desired state of the TN3270E server represented
           by this entry in the table:

           up(1)            - Activate this TN3270E server.
           down(2)          - Informs the associated TN3270E
                              server to gracefully terminate
                              its processing.
           stopImmediate(3) - Informs the associated TN3270E
                              server to terminate itself
                              immediately.

           When a managed system creates an entry in this table,
           tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
           are initialized as up(1) by default.

           The exact behavior of a server in response to a down(2)
           or stopImmediate(3) command is left implementation-

           dependent.  A TN3270E server that is capable of it
           SHOULD close all of its TN3270 and TN3270E sessions
           during a graceful termination.

           Often the function enabled via stopImmediate(3) is used
           as a last resort by a system administrator, to attempt
           to either bring down a hung TN3270E server or free up
           its resources immediately to aid in general system
           availability, or to shut down a TN3270E server that is
           not recognizing a down(2) request.

           A TN3270E server that does not distinguish between
           down(2) or stopImmediate(3) transitions should not
           support stopImmediate(3)."
      DEFVAL { up }
      ::= { tn3270eSrvrConfEntry 7 }

    Information by cisco

    tn3270eSrvrConfAdminStatus OBJECT-TYPE
      SYNTAX  INTEGER {
                        up(1),
                        down(2),
                        stopImmediate(3)
                      }
      MAX-ACCESS  read-create
      STATUS      current
      DESCRIPTION
          "The desired state of the TN3270E server represented
           by this entry in the table:

           up(1)            - Activate this TN3270E server.
           down(2)          - Informs the associated TN3270E
                              server to gracefully terminate
                              its processing.
           stopImmediate(3) - Informs the associated TN3270E
                              server to terminate itself
                              immediately.

           When a managed system creates an entry in this table,
           tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
           are initialized as up(1) by default.

           The exact behavior of a server in response to a down(2)
           or stopImmediate(3) command is left implementation-
           dependent.  A TN3270E server that is capable of it
           SHOULD close all of its TN3270 and TN3270E sessions
           during a graceful termination.

           Often the function enabled via stopImmediate(3) is used
           as a last resort by a system administrator, to attempt
           to either bring down a hung TN3270E server or free up
           its resources immediately to aid in general system
           availability, or to shut down a TN3270E server that is
           not recognizing a down(2) request.

           A TN3270E server that does not distinguish between
           down(2) or stopImmediate(3) transitions should not
           support stopImmediate(3)."
      DEFVAL { up }
      ::= { tn3270eSrvrConfEntry 7 }

    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

    Brothers (13)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.34.8.1.1.1.1 tn3270eSrvrConfIndex 0 0 Identifier for a single TN3270E server.

    tn3270eSrvrConfIndex values need not be
    contiguous.
    1.3.6.1.2.1.34.8.1.1.1.2 tn3270eSrvrConfInactivityTimeout 0 0 The inactivity time-out specified in seconds. When a
    connection has been inactive for the number of seconds
    specified by this ob…
    1.3.6.1.2.1.34.8.1.1.1.3 tn3270eSrvrConfConnectivityChk, tn3270eSrvrConfActivityCheck 0 0 This object enables TIMING-MARK processing, NOP
    processing, or neither for a TN3270E server.
    1.3.6.1.2.1.34.8.1.1.1.4 tn3270eSrvrConfTmNopInactTime, tn3270eSrvrConfActivityTimeout 0 0 The TIMEMARK or NOP processing time-out specified in seconds.
    Note that a value of 0 is not allowed for this object since
    the fun…
    1.3.6.1.2.1.34.8.1.1.1.5 tn3270eSrvrConfTmNopInterval, tn3270eSrvrConfActivityInterval 0 0 The scan interval to be used by a TN3270E server.
    TIMEMARK or NOP processing scans the Telnet sessions
    on the interval provided b…
    1.3.6.1.2.1.34.8.1.1.1.6 tn3270eSrvrFunctionsSupported 0 0 This object indicates the functions supported by a
    TN3270E server.
    1.3.6.1.2.1.34.8.1.1.1.8 tn3270eSrvrConfOperStatus 0 0 The current operational state of a TN3270E server.
    The following values are defined:

    up(1) - the server is active and …
    1.3.6.1.2.1.34.8.1.1.1.9 tn3270eSrvrConfSessionTermState 0 0 This object determines what a TN3270E server
    should do when a TN3270 Session terminates:
    terminate(1) => Terminate the TCP co…
    1.3.6.1.2.1.34.8.1.1.1.10 tn3270eSrvrConfSrvrType 0 0 This object indicates the type of TN3270E server.
    The existence of MIB tables and objects that will be
    defined by follow-on MIBs …
    1.3.6.1.2.1.34.8.1.1.1.11 tn3270eSrvrConfContact 0 0 This object provides a scratch pad for a TN3270E
    server administrator for storing information for
    later retrieval.
    1.3.6.1.2.1.34.8.1.1.1.12 tn3270eSrvrConfRowStatus 0 0 This object allows entries to be created and deleted
    in the tn3270eSrvrConfTable. Entries may also be
    created and deleted as a r…
    1.3.6.1.2.1.34.8.1.1.1.13 tn3270eSrvrConfLastActTime 0 0 tn3270eSrvrConfLastActTime OBJECT-TYPE
    SYNTAX DateAndTime
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
    "This object reports …
    1.3.6.1.2.1.34.8.1.1.1.14 tn3270eSrvrConfTmTimeout 0 0 The TIMING-MARK time-out, specified in seconds.