All MIBs › RFC1286-MIB › dot1dSrPortLargestFrame
dot1dSrPortLargestFrame
Module: RFC1286-MIB
OID (symbolic): RFC1286-MIB::dot1dSrPortLargestFrame
OID (numeric): 1.3.6.1.2.1.17.3.1.1.6
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The maximum size of the INFO field (LLC and above) that this port can send/receive. It does not include any MAC level (framing) octets. The value of this object is used by this bridge to determine whether a modification of the LargestFrame (LF, see [14]) field of the Routing Control field of the Routing Information Field is necessary. Valid values as defined by the 802.5 source routing bridging specification[14] are 516, 1500, 2052, 4472, 8144, 11407, 17800, and 65535 octets. Behavior of the port when an illegal value is written is implementation specific. It is recommended that a reasonable legal value be chosen.
What is dot1dSrPortLargestFrame?
This object sets the maximum INFO field size, in octets, that this port can send or receive, chosen from standard 802.5 source routing values such as 516, 1500, 4472, or 65535. Admins configure it to match the largest frame the attached ring segment can handle, and the bridge uses it to decide whether to update the Largest Frame field in the Routing Information Field of passing frames. Setting it to dot1dSrMtu4472 would cap frames at 4472 octets for that port.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.17.3.1.1.6 snmpwalk -v2c -c public <target> RFC1286-MIB::dot1dSrPortLargestFrame
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.17.3.1.1.6.1 snmpget -v2c -c public <target> RFC1286-MIB::dot1dSrPortLargestFrame.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.2.1.17.3.1.1.6.1 i <value>
Start monitoring vendor-neutral, standards-based MIB, Ethernet/Token Ring transparent bridges and early Layer 2 switches with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1286-MIB::dot1dSrPortLargestFrame OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, Ethernet/Token Ring transparent bridges and early Layer 2 switches from a single console.
OID Breakdown
Upper-level ancestors (8 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.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.17 | dot1dBridge | BRIDGE-MIB |
| 1.3.6.1.2.1.17.3 | dot1dSr | BRIDGE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.17.3.1 | dot1dSrPortTable | RFC1286-MIB |
| 1.3.6.1.2.1.17.3.1.1 | dot1dSrPortEntry | RFC1286-MIB |
| 1.3.6.1.2.1.17.3.1.1.6 | dot1dSrPortLargestFrame | RFC1286-MIB |