LLDP (Link Layer Discovery Protocol, IEEE 802.1AB) lets one network device tell its direct neighbor who it is — chassis ID, port ID, system name — every 30 seconds, with no IP address and no management software. Rayin managed industrial switches and OLTs run LLDP natively, so a multi-vendor access network draws its own topology. Rayin's managed industrial switches advertise the LLDP neighbor table to the NMS over SNMP, which means a factory floor maps itself without a single site visit.
LLDP runs on Layer 2, Ethertype 0x88CC, sending an LLDPDU every 30 seconds; the neighbor ages out after TTL 120 s.
Each frame carries TLVs (type-length-value) for chassis ID, port ID, system name, capabilities, and management address.
It discovers neighbors with zero configuration and works across vendors — unlike a private discovery protocol that only sees its own brand.
Pair LLDP with SNMP polling: LLDP draws the connection map, SNMP reports health and traffic.
In a plant or campus, nobody remembers which port plugs into which switch. When a link drops, you log into boxes one by one and hope the labels are right. LLDP removes that guessing: every device announces itself to the device on the other end of the cable, so the network knows its own shape. For an industrial network with dozens of switches spread across a noisy floor, that self-awareness is the difference between a five-minute fix and a half-day hunt.
LLDP lives on the data-link layer. A device sends an LLDPDU (LLDP data unit) to the multicast address every 30 seconds. The frame is built from TLVs — chassis ID, port ID, system name, system description, system capabilities (bridge/router), and management address. The neighbor stores them in its local MIB. A network management system reads those MIBs and reconstructs who connects to whom.
The default TTL is 120 seconds: if a neighbor stops advertising, the entry is dropped after two missed intervals, so a dead link shows up fast instead of lingering as a "ghost" neighbor.
1. Zero-config auto-discovery. A new switch goes in, the peer learns it immediately — no manual MAC registration, no logging into every box to find neighbors. Commissioning and expansion both get simpler.
2. Cross-vendor interoperability. LLDP is an open IEEE standard, so a Rayin switch and another brand's device discover each other. Against a vendor's private link-discovery protocol, LLDP never leaves a multi-vendor mix "blind" to one side.
3. Works without IP. If a device has no address yet, or the management network is down, LLDP still finds the neighbor as long as the cable is up. It is the last line of "who is on the other end" when everything else is dark.
4. Real-time link state, instant fault location. When TTL expires, the neighbor vanishes from the table — a device offline or a port loose turns the topology map red at once. You stop comparing boxes one by one and go straight to the broken segment.
Automatic network topology. An SNMP-based NMS reads each switch's LLDP neighbor table and draws the whole map. For a campus with hundreds of switches, you see who connects to whom at a glance, and asset inventory stops being a hand-typed Excel sheet.
Fast fault location. A service goes down — check the LLDP neighbor table for that link. Neighbor gone means a physical port or fiber problem; neighbor still there but uplink empty means the fault is upstream. The search shrinks to one segment.
Plug-and-play IP phones and APs (LLDP-MED). LLDP-MED, the media-endpoint extension, lets a switch push voice VLAN, QoS, and PoE priority to an IP phone or wireless AP automatically. The phone lands in the right VLAN the moment it is plugged in — no per-device setup. LLDP-MED is why a new handset "just works."
Compliance and change audit. Who connected to which switch, and when? The LLDP table plus logs is a living network ledger — pull it straight out for security grading or audit reviews.
Multi-vendor cutover check. During a cutover or a new vendor's entry, LLDP confirms both ends negotiated the same port, speed, and VLAN — no more "my side is trunk, your side is access" mismatches.
Step 1 — Enable LLDP globally. Rayin managed industrial switches and OLTs support LLDP (IEEE 802.1AB). Turn it on and the device starts advertising its identity and reading neighbors; the neighbor table feeds the NMS for link visualization.
Step 2 — Read the neighbor table via SNMP. In a factory or mine — many devices, harsh environment — poll the LLDP neighbors over SNMP. You see the full connection relationship without frequent site trips, which is exactly where LLDP pays off most.
Step 3 — Tighten untrusted ports. LLDP is on by default globally; ports that should not expose information can be disabled individually. Remember the 120-second TTL before calling a just-unplugged link "stable," and confirm both sides run LLDP (not one private protocol and one LLDP) on a cross-vendor link.
What is the relationship between LLDP and a vendor's private discovery protocol? Some gear carries a vendor-private link-discovery protocol that only recognizes its own brand. LLDP is the IEEE open standard and discovers across all vendors. On a mixed network, standardize on LLDP; do not expect a private protocol to see a foreign device.
Does LLDP need an IP address? No. It runs on Layer 2 using MAC and multicast, so devices with no address still discover each other. That is also why it keeps working when the management network is unhealthy.
Will enabling LLDP leak network information? It broadcasts device name, port, and management address. On an untrusted or public-facing port, disable LLDP or keep it only inside the trusted internal domain; shut it off on sensitive ports individually.
Can LLDP replace SNMP? No. LLDP only answers "who is my neighbor." Performance, traffic, and alarms still come from SNMP or telemetry. Use both: LLDP draws connections, SNMP shows running state.
The neighbor table shows a device but the service is down — why? LLDP only proves the Layer-2 link is up. If VLAN, IP, routing, or ACL is wrong above it, the service still fails. LLDP confirms the physical connection; the rest is configuration.
Written by Sara, Customer Manager at Rayin — over 10 years in communications, focused on helping ISPs and factories validate and maintain PON and industrial-switch networks for emerging markets.
About Rayin → https://www.szrayin.com/Profile/
