Reference record for OID 1.3.6.1.2.1.27.2.1.2


parent
1.3.6.1.2.1.27.2.1 (assocEntry)
node code
2
node name
assocRemoteApplication
dot oid
1.3.6.1.2.1.27.2.1.2
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) application(27) assocTable(2) assocEntry(1) assocRemoteApplication(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) application(27) assocTable(2) assocEntry(1) assocRemoteApplication(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) application(27) assocTable(2) assocEntry(1) assocRemoteApplication(2)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) application(27) assocTable(2) assocEntry(1) assocRemoteApplication(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) application(27) assocTable(2) assocEntry(1) assocRemoteApplication(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) application(27) assocTable(2) assocEntry(1) assocRemoteApplication(2)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/application/assocTable/assocEntry/assocRemoteApplication
  • /iso/identified-organization/dod/internet/mgmt/mib/application/assocTable/assocEntry/assocRemoteApplication
  • /iso/org/dod/internet/mgmt/mib-2/application/assocTable/assocEntry/assocRemoteApplication
  • /iso/org/dod/internet/mgmt/mib/application/assocTable/assocEntry/assocRemoteApplication
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/application/assocTable/assocEntry/assocRemoteApplication
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/application/assocTable/assocEntry/assocRemoteApplication
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/27/2/1/2

    Description by oid_info

    assocRemoteApplication OBJECT-TYPE SYNTAX SnmpAdminString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION
    "The name of the system running remote network service
    application. For an IP-based application this should be
    either a domain name or IP address. For an OSI application
    it should be the string encoded distinguished name of the
    managed object. For X.400(1984) MTAs which do not have a
    Distinguished Name, the RFC 2156 syntax mta in
    globalid used in X400-Received: fields can be used. Note,
    however, that not all connections an MTA makes are
    necessarily to another MTA."

    View at oid-info.com

    Description by mibdepot

    The name of the system running remote network service
    application. For an IP-based application this should be
    either a domain name or IP address. For an OSI application
    it should be the string encoded distinguished name of the
    managed object. For X.400(84) MTAs which do not have a
    Distinguished Name, the RFC1327 [6] syntax
    'mta in globalid' should be used.

    Parsed from file application.txt
    Company: None
    Module: APPLICATION-MIB

    Description by circitor

    The name of the system running remote network service
    application. For an IP-based application this should be
    either a domain name or IP address. For an OSI application
    it should be the string encoded distinguished name of the
    managed object. For X.400(1984) MTAs which do not have a
    Distinguished Name, the RFC 2156 syntax 'mta in
    globalid' used in X400-Received: fields can be used. Note,
    however, that not all connections an MTA makes are
    necessarily to another MTA.

    Parsed from file NETWORK-SERVICES-MIB.mib
    Module: NETWORK-SERVICES-MIB

    Information by oid_info

    Automatically extracted from RFC2788

    Information by mibdepot

    assocRemoteApplication OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the system running remote network service application. For an IP-based application this should be either a domain name or IP address. For an OSI application it should be the string encoded distinguished name of the managed object. For X.400(84) MTAs which do not have a Distinguished Name, the RFC1327 [6] syntax 'mta in globalid' should be used." ::= {assocEntry 2}

    Information by circitor

    assocRemoteApplication OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-only STATUS current DESCRIPTION "The name of the system running remote network service application. For an IP-based application this should be either a domain name or IP address. For an OSI application it should be the string encoded distinguished name of the managed object. For X.400(1984) MTAs which do not have a Distinguished Name, the RFC 2156 syntax 'mta in globalid' used in X400-Received: fields can be used. Note, however, that not all connections an MTA makes are necessarily to another MTA." ::= {assocEntry 2}

    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 (4)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.27.2.1.1 assocIndex 0 0 An index to uniquely identify each association for a network
    service application.
    1.3.6.1.2.1.27.2.1.3 assocApplicationProtocol 0 0 An identification of the protocol being used for the
    application. For an OSI Application, this will be the
    Application Context. …
    1.3.6.1.2.1.27.2.1.4 assocApplicationType 0 0 This indicates whether the remote application is some type of
    client making use of this network service (e.g. a User Agent)
    or a …
    1.3.6.1.2.1.27.2.1.5 assocDuration 0 0 The value of sysUpTime at the time this association was
    started. If this association started prior to the last
    initialization of…