Replies: 1 comment 2 replies
-
|
Yes, results from CDP are translated to LLDP. You should be able to see the values in |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have implemented a service that listens to lldpd and fetches info about allocated POE power from lldpd using the MDI API.
However now we have seen a case in which it seems like the parameters via the API thinks that the switch does not support LLDP MDI power negotiation, while we can see that lldpd sends out this print
**lldpd[<x>]: for eth0, PSE told us allocated is now 160 instead of 0**so it seems like lldpd has received info that the switch has allocated more than 13W to our device, but we do not see it when decoding the Power-via-MDI parameters.
So, can we access the value above (160, or 16.0W) using some API, other than the Power-via-MDI API, or is that the only place where this information is available?
Also, another, related question:
Does lldpd translate between LLDP power negotiation and CDP power negotiation?
It seems like if the PSE switch has disabled LLDP but enabled CDP (and its a Cisco switch), even though we have not implemented any CDP power negotiation, our LLDP request for power does reach the switch, andit it does actually allocate power to us. In some cases it also seems like we do get an LLDP message back that tells us about it (even though that does not seem to happen always).
So, does lldpd translate between LLDP and CDP power negotiation protocols?
If so, is this described anywhere?
Beta Was this translation helpful? Give feedback.
All reactions