OID reference

sshdCfgKeepAlives

1.3.6.1.4.1.272.4.44.1.7

Description

Specifies whether the system should send keepalive messages to the other side. If they are sent, death of the connection or crash of one of the machines will be properly noticed. However, this means that connections will die if the route is down tem- porarily, and some people find it annoying. On the other hand, if ke…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.272.4.44.1 (sshDaemonCfg)
Node code
7
Node name
sshdCfgKeepAlives
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.272.4.44.1.7
URN notation
urn:oid:1.3.6.1.4.1.272.4.44.1.7
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 272 4 44 1 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) bintec(272) bibo(4) ssh(44) sshDaemonCfg(1) sshdCfgKeepAlives(7)}
OID-IRI notation
  • /1/3/6/1/4/1/272/4/44/1/7
  • /ISO/Identified-Organization/6/1/4/1/272/4/44/1/7
  • /ISO/3/6/1/4/1/272/4/44/1/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/identified-organization/dod/internet/private/enterprises/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/identified-organization/dod/internet/private/vendor-objects/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/org/dod/internet/private/enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/org/dod/internet/private/enterprises/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/org/dod/internet/private/ldap-enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/org/dod/internet/private/vendor-objects/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-identified-organization/dod/internet/private/enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-identified-organization/dod/internet/private/enterprises/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-organization/dod/internet/private/enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-organization/dod/internet/private/enterprises/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives
  • /iso/iso-organization/dod/internet/private/vendor-objects/bintec/bibo/ssh/sshDaemonCfg/sshdCfgKeepAlives

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory
Default value
yes

Enumerated values

ValueName
1yes
2no

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

The displayed source records contain one distinct definition. Compare its source records.

sshdCfgKeepAlives OBJECT-TYPE
	    SYNTAX  INTEGER {
		yes(1),
		no(2)
	    }
	    ACCESS  read-write
	    STATUS  mandatory
	    DESCRIPTION
		"Specifies whether the system should send keepalive messages to
		 the other side. If they are sent, death of the connection or
		 crash of one of the machines will be properly noticed. However,
		 this means that connections will die if the route is down tem-
		 porarily, and some people find it annoying. On the other hand,
		 if keepalives are not sent, sessions may hang indefinitely on
		 the server, leaving 'ghost' users and consuming server
		 resources.

		 The default is 'yes' (to send keepalives), and the server will
		 notice if the network goes down or the client host reboots.
		 This avoids infinitely hanging sessions.

		 To disable keepalives, the value should be set to 'no' in both
		 the server and the client configuration files."
	    DEFVAL { yes }
	::= { sshDaemonCfg 7 }

Meaning

Descriptions

1 unique

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

Specifies whether the system should send keepalive messages to the other side. If they are sent, death of the connection or crash of one of the machines will be properly noticed. However, this means that connections will die if the route is down tem- porarily, and some people find it annoying. On the other hand, if keepalives are not sent, sessions may hang indefinitely on the server, leaving 'ghost' users and consuming server resources. The default is 'yes' (to send keepalives), and the server will notice if the network goes down or the client host reboots. This avoids infinitely hanging sessions. To disable keepalives, the value should be set to 'no' in both the server and the client configuration files.

Sources for this description

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

See 1 matching source record

Evidence

Source records

1 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)1 record · 1 source

Description 1

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

Status in source: mandatory.

Names: sshdCfgKeepAlives

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sshdCfgKeepAlives",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "yes",
    "(",
    "1",
    ")",
    ",",
    "no",
    "(",
    "2",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Specifies whether the system should send keepalive messages to the other side. If they are sent, death of the connection or crash of one of the machines will be properly noticed. However, this means that connections will die if the route is down tem- porarily, and some people find it annoying. On the other hand, if keepalives are not sent, sessions may hang indefinitely on the server, leaving 'ghost' users and consuming server resources. The default is 'yes' (to send keepalives), and the server will notice if the network goes down or the client host reboots. This avoids infinitely hanging sessions. To disable keepalives, the value should be set to 'no' in both the server and the client configuration files.\"",
    "DEFVAL",
    "{",
    "yes",
    "}",
    "::=",
    "{",
    "sshDaemonCfg",
    "7",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "yes",
            1
          ],
          [
            "no",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Specifies whether the system should send keepalive messages to the other side. If they are sent, death of the connection or crash of one of the machines will be properly noticed. However, this means that connections will die if the route is down tem- porarily, and some people find it annoying. On the other hand, if keepalives are not sent, sessions may hang indefinitely on the server, leaving 'ghost' users and consuming server resources. The default is 'yes' (to send keepalives), and the server will notice if the network goes down or the client host reboots. This avoids infinitely hanging sessions. To disable keepalives, the value should be set to 'no' in both the server and the client configuration files."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "yes"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.272)

Hertlein Elisabeth

Siblings (26)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.272.4.44.1.1 sshdCfgPort00
1.3.6.1.4.1.272.4.44.1.2 sshdCfgLoginGraceTime00
1.3.6.1.4.1.272.4.44.1.3 sshdCfgHostbasedAuthentication00
1.3.6.1.4.1.272.4.44.1.4 sshdCfgPubkeyAuthentication00
1.3.6.1.4.1.272.4.44.1.5 sshdCfgPasswordAuthentication00
1.3.6.1.4.1.272.4.44.1.6 sshdCfgChallengeResponseAuthentication00
1.3.6.1.4.1.272.4.44.1.8 sshdCfgPermitEmptyPasswd00
1.3.6.1.4.1.272.4.44.1.9 sshdCfgCompression00
1.3.6.1.4.1.272.4.44.1.10 sshdCfgVerifyReverseMapping00
1.3.6.1.4.1.272.4.44.1.11 sshdCfgLogFacility00
1.3.6.1.4.1.272.4.44.1.12 sshdCfgLogLevel00
1.3.6.1.4.1.272.4.44.1.13 sshdCfgCiphers00
1.3.6.1.4.1.272.4.44.1.14 sshdCfgMacs00
1.3.6.1.4.1.272.4.44.1.15 sshdCfgProtocol00
1.3.6.1.4.1.272.4.44.1.16 sshdCfgMaxClients00
1.3.6.1.4.1.272.4.44.1.17 sshdCfgClientAliveInterval00
1.3.6.1.4.1.272.4.44.1.18 sshdCfgClientAliveCountMax00
1.3.6.1.4.1.272.4.44.1.19 sshdCfgAllowTcpForwarding00
1.3.6.1.4.1.272.4.44.1.20 sshdCfgGatewayPorts00
1.3.6.1.4.1.272.4.44.1.21 sshdCfgUseLogin00
1.3.6.1.4.1.272.4.44.1.22 sshdCfgX11Forwarding00
1.3.6.1.4.1.272.4.44.1.23 sshdCfgX11DisplayOffset00
1.3.6.1.4.1.272.4.44.1.32 sshdCfgPrintMotd00
1.3.6.1.4.1.272.4.44.1.33 sshdCfgBanner00
1.3.6.1.4.1.272.4.44.1.34 sshdCfgPrintLastLog00
1.3.6.1.4.1.272.4.44.1.35 sshdCfgLastLogin00