All MIBs › ODSLANBlazer7000-MIB › lanBlazer7000PortFlowControlMode
lanBlazer7000PortFlowControlMode
Module: ODSLANBlazer7000-MIB
OID (symbolic): ODSLANBlazer7000-MIB::lanBlazer7000PortFlowControlMode
OID (numeric): 1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1.21
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: Flow control is used to prevent or reduce the dropping of frames due to the lack of buffer space. Overall, networks are more efficient when a sending station is asked to pause in its sending process, rather than having the transmitted frames dropped.
Flow control is not as efficient when used in conjunction with a shared ports, i.e. when used with a repeater. Therefore, flow control is not recommended for a port connected to shared topologies.
Flow control is most effective when the port is directly connected to an end-station, especially when connected to a server. Flow control is recommended for ports connected directly to end-stations.
When the port is in half-duplex mode, back pressure is used to control the incoming flow. Back pressure essentially forces collisions for short periods of time.
When the port is in full-duplex mode, IEEE 802.3 standard pause frames are used to control the incoming flow.
Note that setting an ether-gigabit(4) port to enable-with-aggressive-backoff(3) results in an error.
What is lanBlazer7000PortFlowControlMode?
Controls 802.3 flow control on this port: enable(1) lets the switch send pause frames (full-duplex) or use back-pressure (half-duplex) to ask an overwhelmed sender to slow down rather than dropping frames, disable(2) turns this off, and enable-with-aggressive-backoff(3) applies a more assertive back-pressure variant (not settable on ether-gigabit(4) ports, which rejects that mode). An admin enables flow control on a port connected directly to a server to avoid frame loss under burst traffic, but leaves it disabled on a port feeding a shared repeater segment where it is less effective.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1.21 snmpwalk -v2c -c public <target> ODSLANBlazer7000-MIB::lanBlazer7000PortFlowControlMode
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1.21.1 snmpget -v2c -c public <target> ODSLANBlazer7000-MIB::lanBlazer7000PortFlowControlMode.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1.21.1 i <value>
Start monitoring ODS LANBlazer 7000 WAN test/analysis instrument with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ODSLANBlazer7000-MIB::lanBlazer7000PortFlowControlMode OID value, configure state conditions and alerts, and monitor any ODS LANBlazer 7000 WAN test/analysis instrument from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.50 | ods | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8 | odsTPS | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1 | odsLANBlazer | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2 | odsLANBlazerMibs | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2.1 | odsLANBlazer7000Mib | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2.1.3 | lanBlazer7000Chassis | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2.1.3.6 | lanBlazer7000Ports | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2.1.3.6.2 | lanBlazer7000PortFlowControlMgt | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2.1.3.6.2.1 | lanBlazer7000PortFlowControlTable | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1 | lanBlazer7000PortFlowControlEntry | ODSLANBlazer7000-MIB |
| 1.3.6.1.4.1.50.8.1.2.1.3.6.2.1.1.21 | lanBlazer7000PortFlowControlMode | ODSLANBlazer7000-MIB |