LLDP chassis name is being ignored in nebula-managed switches

Options
matteosaitta
matteosaitta Posts: 33
First Comment Friend Collector Seventh Anniversary
image  Freshman Member

Hello,

I am testing using the native windows LLDP agent to provide basic data to switches and routers but I am seeing a logic issue on my Zyxel switches.

Devices with both system and chassis name populated are shown while devices with just chassis name are being ignored. Windows sadly only sends chassis name and interface MAC for each active interface.

If there is LLDP data but no system name, it should make sense for the chassis name to be used as a neighbor name.

Is this a bug? My netgear switches populate their neighbors table correctly with the same kind of data.

Accepted Solution

All Replies

  • XiLeiHaLo
    XiLeiHaLo Posts: 24
    First Comment First Answer Friend Collector Fifth Anniversary
    image  Freshman Member
    Options

    I guess you are claiming that the switch web cannot see device with only sending chassis name in LLDP pakcet since there is no such a column called "Chassis name", but you can check the chassis name in the switch CLI by typing show lldp info remote

  • Zyxel_Judy
    Zyxel_Judy Posts: 2,850
    Zyxel Certified Network Engineer Level 2 - Nebula Zyxel Certified Network Engineer Level 2 - Switch Zyxel Certified Network Engineer Level 2 - Security Zyxel Certified Network Engineer Level 1 - Nebula
    image  Zyxel Employee
    Answer ✓
    Options

    Hi @matteosaitta ,

    This is expected behavior, not a bug: the Neighbor Table currently shows the System Name only when present, with no fallback to Chassis ID. To check the chassis name in the switch, please use the CLI as show lldp info remote

    A fallback to Chassis ID when System Name is missing would be a useful improvement, so we submitted this as an Idea Post here:

    Support Chassis ID Fallback in LLDP Neighbor Table When System Name Is Absent — Zyxel Community

    Zyxel_Judy