MIB Discovery
1926 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 6 (tcp). 2 (tcpRtoMin)
OID : 1.3.6.1.2.1.6.2
TXT : iso. org. dod. internet. mgmt. mib-2. tcp. tcpRtoMin
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.2.1.6.2
Module TCP-MIB (CISCO)
NomtcpRtoMin
Accesreadonly
Statuscurrent
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend on the algorithm used to determine the retransmission timeout; in particular, the IETF standard algorithm rfc2988(5) provides a minimum value.
Unitemilliseconds
SyntaxeInteger32 (0...2147483647)
Module RFC1213-MIB (DELL)
NomtcpRtoMin
Accesreadonly
Statusmandatory
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
SyntaxeInteger32
Module RFC1213-MIB (ietf)
NomtcpRtoMin
Accesreadonly
Statusmandatory
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
SyntaxeInteger32
Module TCP-MIB (ietf)
NomtcpRtoMin
Accesreadonly
Statuscurrent
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend on the algorithm used to determine the retransmission timeout; in particular, the IETF standard algorithm rfc2988(5) provides a minimum value.
Unitemilliseconds
SyntaxeInteger32 (0...2147483647)
Module TCP-MIB (DELL)
NomtcpRtoMin
Accesreadonly
Statuscurrent
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
Unitemilliseconds
SyntaxeInteger32
Module TCP-MIB (Alcatel)
NomtcpRtoMin
Accesreadonly
Statuscurrent
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend on the algorithm used to determine the retransmission timeout; in particular, the IETF standard algorithm rfc2988(5) provides a minimum value.
Unitemilliseconds
SyntaxeInteger32 (0...2147483647)
Module RFC1213-MIB (Force10-9.14.2.1)
NomtcpRtoMin
Accesreadonly
Statusmandatory
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
SyntaxeInteger32
Module TCP-MIB (Force10-9.14.2.1)
NomtcpRtoMin
Accesreadonly
Statuscurrent
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend on the algorithm used to determine the retransmission timeout; in particular, the IETF standard algorithm rfc2988(5) provides a minimum value.
Unitemilliseconds
SyntaxeInteger32 (0...2147483647)
Module RFC1213-MIB (FS)
NomtcpRtoMin
Accesreadonly
Statusmandatory
DescriptionThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793.
SyntaxeInteger32