MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 46 (dlsw). 1 (dlswMIB). 2 (dlswTConn). 3 (dlswTConnOperTable). 1 (dlswTConnOperEntry). 8 (dlswTConnOperFlowCntlMode)
OID : 1.3.6.1.2.1.46.1.2.3.1.8
TXT : iso. org. dod. internet. mgmt. mib-2. dlsw. dlswMIB. dlswTConn. dlswTConnOperTable. dlswTConnOperEntry. dlswTConnOperFlowCntlMode
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.46.1.2.3.1.8
Module DLSW-MIB (CISCO)
NomdlswTConnOperFlowCntlMode
Accesreadonly
Statuscurrent
DescriptionThe flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control can be established on a new transport connection (i.e., after CapEx is sent but before Capex or other SSP control messages have been received). Pacing (2) indicates that the standard RFC 1795 pacing mechanism is in use. Other (3) may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be inferred from dlswTConnOperPartnerVersion.
SyntaxeEnumeration (1-undetermined, 2-pacing, 3-other)
Module DLSW-MIB (ietf)
NomdlswTConnOperFlowCntlMode
Accesreadonly
Statuscurrent
DescriptionThe flow control mechanism in use on this transport connection. This value is undetermined (1) before the mode of flow control can be established on a new transport connection (i.e., after CapEx is sent but before Capex or other SSP control messages have been received). Pacing (2) indicates that the standard RFC 1795 pacing mechanism is in use. Other (3) may be either the RFC 1434+ xBusy mechanism operating to a back-level DLSw, or a vendor-specific flow control method. Whether it is xBusy or not can be inferred from dlswTConnOperPartnerVersion.
SyntaxeEnumeration (1-undetermined, 2-pacing, 3-other)