LBHUB-FMS-MIB :: configV24FlowControl

MIB Reference — IPNetwork Monitor

All MIBsLBHUB-FMS-MIBconfigV24FlowControl

configV24FlowControl

Module: LBHUB-FMS-MIB

OID (symbolic): LBHUB-FMS-MIB::configV24FlowControl

OID (numeric): 1.3.6.1.4.1.43.10.7.2.1.10

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description:

This determines the flow control protocol to be used, either no flow control, xon-xoff, rts-cts full duplex or rts-cts. Full duplex rts/cts uses the rts and cts lines as two independent signals. The DTE signals to the DCE that it is prepared to accept more data by asserting RTS, the DCE signals to the DTE that is is prepared to accept more data by asserting CTS. Half duplex rts/cts (the conventional way) uses CTS as a response to RTS, the DCE flow controls the DTE by only returning CTS is response to a RTS from the DTE when the DCE can accept more data. The DTE can flow control the DCE by raising RTS when it does not want to receive any more input and dropping it when it is ready to receive more.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.10.7.2.1.10
snmpwalk -v2c -c public <target> LBHUB-FMS-MIB::configV24FlowControl

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.43.10.7.2.1.10.1
snmpget -v2c -c public <target> LBHUB-FMS-MIB::configV24FlowControl.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.43.10.7.2.1.10.1 i <value>

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.43a3ComA3COM-HUAWEI-OID-MIB
1.3.6.1.4.1.43.10genericA3Com-products-MIB
1.3.6.1.4.1.43.10.7serialIfA3COM0004-GENERIC
1.3.6.1.4.1.43.10.7.2configV24TableLBHUB-BOOM-MIB
1.3.6.1.4.1.43.10.7.2.1configV24EntryLBHUB-BOOM-MIB
1.3.6.1.4.1.43.10.7.2.1.10configV24FlowControlLBHUB-FMS-MIB