All MIBs › CM-SYSTEM-MIB › f3SystemLldpV2PortConfigADVAExtAdminStatus
f3SystemLldpV2PortConfigADVAExtAdminStatus
Module: CM-SYSTEM-MIB
OID (symbolic): CM-SYSTEM-MIB::f3SystemLldpV2PortConfigADVAExtAdminStatus
OID (numeric): 1.3.6.1.4.1.2544.1.12.2.1.16.2.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: The administratively desired status of the local LLDP agent.
If the associated f3SystemLldpV2PortConfigADVAExtAdminStatus object is set to a value of 'txOnly(1)', then LLDP agent transmits LLDPframes on this port and it does not store any information about the remote systems connected.
If the associated f3SystemLldpV2PortConfigADVAExtAdminStatus object is set to a value of 'rxOnly(2)', then the LLDP agent receives, but it does not transmit LLDP frames on this port.
If the associated f3SystemLldpV2PortConfigADVAExtAdminStatus object is set to a value of 'txAndRx(3)', then the LLDP agent transmits and receives LLDP frames on this port.
If the associated f3SystemLldpV2PortConfigADVAExtAdminStatus object is set to a value of 'disabled(4)', then LLDP agent does not transmit or receive LLDP frames on this port. If there is remote systems information which is received on this port and stored in other tables, before the port's f3SystemLldpV2PortConfigADVAExtAdminStatus becomes disabled, then that information is deleted.
What is f3SystemLldpV2PortConfigADVAExtAdminStatus?
This INTEGER sets the administratively desired LLDP mode on a port: txOnly(1) transmits LLDP frames without storing neighbor info, rxOnly(2) only listens for and stores neighbor info, txAndRx(3) does both, and disabled(4) turns LLDP off on that port. An admin sets this per port depending on whether they want the device to advertise itself, discover neighbors, both, or neither via LLDP. For example, an operator on a port facing an untrusted third-party device might set f3SystemLldpV2PortConfigADVAExtAdminStatus to rxOnly(2) so the device learns about its neighbor without advertising its own details.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2544.1.12.2.1.16.2.1.3 snmpwalk -v2c -c public <target> CM-SYSTEM-MIB::f3SystemLldpV2PortConfigADVAExtAdminStatus
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2544.1.12.2.1.16.2.1.3.1 snmpget -v2c -c public <target> CM-SYSTEM-MIB::f3SystemLldpV2PortConfigADVAExtAdminStatus.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.2544.1.12.2.1.16.2.1.3.1 i <value>
Start monitoring ADVA/Ceragon FSP150 CM/CC (F3) microwave & Carrier Ethernet transport platform with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CM-SYSTEM-MIB::f3SystemLldpV2PortConfigADVAExtAdminStatus OID value, configure state conditions and alerts, and monitor any ADVA/Ceragon FSP150 CM/CC (F3) microwave & Carrier Ethernet transport platform from a single console.
OID Breakdown
Upper-level ancestors (9 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 |
| 1.3.6.1.4.1.2544 | advaMIB | ADVA-MIB |
| 1.3.6.1.4.1.2544.1 | products | ADVA-MIB |
| 1.3.6.1.4.1.2544.1.12 | fsp150cm | ADVA-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2544.1.12.2 | cmSystemMIB | CM-SYSTEM-MIB |
| 1.3.6.1.4.1.2544.1.12.2.1 | cmSystemObjects | CM-SYSTEM-MIB |
| 1.3.6.1.4.1.2544.1.12.2.1.16 | cmLldpV2DestAdressADVAExtObjects | CM-SYSTEM-MIB |
| 1.3.6.1.4.1.2544.1.12.2.1.16.2 | f3SystemLldpV2PortConfigADVAExtTable | CM-SYSTEM-MIB |
| 1.3.6.1.4.1.2544.1.12.2.1.16.2.1 | f3SystemLldpV2PortConfigADVAExtEntry | CM-SYSTEM-MIB |
| 1.3.6.1.4.1.2544.1.12.2.1.16.2.1.3 | f3SystemLldpV2PortConfigADVAExtAdminStatus | CM-SYSTEM-MIB |