CORIANT-GROOVE-MIB :: lldpRemoteSystemRemoteSysCapSupported

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCORIANT-GROOVE-MIBlldpRemoteSystemRemoteSysCapSupported

lldpRemoteSystemRemoteSysCapSupported

Module: CORIANT-GROOVE-MIB

OID (symbolic): CORIANT-GROOVE-MIB::lldpRemoteSystemRemoteSysCapSupported

OID (numeric): 1.3.6.1.4.1.42229.1.2.4.1.3.1.1.9

Node type: OBJECT-TYPE

Type: LldpLldpSysCap

Access: read-only

Description: This attribute describes the system capabilities. The bit 'other(0)' indicates that the system has capabilities other than those listed below. The bit 'repeater(1)' indicates that the system has repeater capability. The bit 'bridge(2)' indicates that the system has bridge capability. The bit 'wlanAccessPoint(3)' indicates that the system has WLAN access point capability. The bit 'router(4)' indicates that the system has router capability. The bit 'telephone(5)' indicates that the system has telephone capability. The bit 'docsisCableDevice(6)' indicates that the system has DOCSIS Cable Device capability (IETF RFC 2669 & 2670). The bit 'stationOnly(7)' indicates that the system has only station capability and nothing else. The bit 'cVLANComponent(8)' indicates that the system has C-VLAN component functionality. The bit 'sVLANComponent(9)' indicates that the system has S-VLAN component functionality. The bit 'twoPortMACRelay(10)' indicates that the system has Two-port MAC Relay (TPMR) functionality. sys-cap-supported: supported system capability

What is lldpRemoteSystemRemoteSysCapSupported?

This read-only bitmap reports which system capabilities the LLDP neighbor supports overall, such as repeater, bridge, wlanAccessPoint, router, or telephone, per the standard LLDP capability bits. This helps an operator understand what kind of device (a switch versus a router versus an access point, for example) is attached to a given port at a glance. For example, a neighbor reporting the 'router' bit set here tells the operator the connected device is capable of routing, which is useful context when a link is unexpectedly seeing routed rather than switched traffic.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.42229.1.2.4.1.3.1.1.9
snmpwalk -v2c -c public <target> CORIANT-GROOVE-MIB::lldpRemoteSystemRemoteSysCapSupported

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.42229.1.2.4.1.3.1.1.9.1
snmpget -v2c -c public <target> CORIANT-GROOVE-MIB::lldpRemoteSystemRemoteSysCapSupported.1

Start monitoring Coriant Groove optical transport platform with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CORIANT-GROOVE-MIB::lldpRemoteSystemRemoteSysCapSupported OID value, configure state conditions and alerts, and monitor any Coriant Groove optical transport platform from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.42229coriantCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1productsCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1.2grooveCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1.2.4servicesCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1.2.4.1otnCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1.2.4.1.3lldpRemoteSystemCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1.2.4.1.3.1lldpRemoteSystemTableCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1.2.4.1.3.1.1lldpRemoteSystemEntryCORIANT-GROOVE-MIB
1.3.6.1.4.1.42229.1.2.4.1.3.1.1.9lldpRemoteSystemRemoteSysCapSupportedCORIANT-GROOVE-MIB