RAPID-CITY :: rcCfmTransmitL2PingDataSize

MIB Reference — IPNetwork Monitor

All MIBsRAPID-CITYrcCfmTransmitL2PingDataSize

rcCfmTransmitL2PingDataSize

Module: RAPID-CITY

OID (symbolic): RAPID-CITY::rcCfmTransmitL2PingDataSize

OID (numeric): 1.3.6.1.4.1.2272.1.69.34.1.9

Node type: OBJECT-TYPE

Type: Integer32

Access: read-write

Description:

An arbitrary amount of data to be included in the data TLV, if the Data Size is selected to be sent.

What is rcCfmTransmitL2PingDataSize?

This object allows an operator to specify the size (0 to 400 bytes) of optional data to include in the data TLV (Type-Length-Value) field of Connectivity Fault Management (CFM) Level 2 ping frames. Variable payload sizes help test how the network handles different frame sizes and can expose MTU or fragmentation issues. Operators use this parameter when troubleshooting Ethernet connectivity and validating end-to-end path availability.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2272.1.69.34.1.9
snmpwalk -v2c -c public <target> RAPID-CITY::rcCfmTransmitL2PingDataSize

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2272.1.69.34.1.9.1
snmpget -v2c -c public <target> RAPID-CITY::rcCfmTransmitL2PingDataSize.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.2272.1.69.34.1.9.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.2272rapidCityRAPID-CITY
1.3.6.1.4.1.2272.1rcMgmtRAPID-CITY
1.3.6.1.4.1.2272.1.69rcCfmRAPID-CITY
1.3.6.1.4.1.2272.1.69.34rcCfmTransmitL2PingTableRAPID-CITY
1.3.6.1.4.1.2272.1.69.34.1rcCfmTransmitL2PingEntryRAPID-CITY
1.3.6.1.4.1.2272.1.69.34.1.9rcCfmTransmitL2PingDataSizeRAPID-CITY