An administrator notices that an EX4300 switch is supplying power using LLDP-MED power negotiation, but the IP phone is drawing more power than the initial hardware class allows. Where would you check the advertised LLDP-MED TLV power value received from the phone?
Trap 1: show system lldp-med power-statistics
system lldp-med power-statistics is not a valid operational command.
Trap 2: show poe interface ge-0/0/10 lldp-negotiation
This command syntax does not exist in Junos OS.
Trap 3: show ethernet-switching interfaces lldp ge-0/0/10
Ethernet-switching does not house LLDP operational command outputs.
- A
show system lldp-med power-statistics
Why it fails: system lldp-med power-statistics is not a valid operational command.
- B
show poe interface ge-0/0/10 lldp-negotiation
Why it fails: This command syntax does not exist in Junos OS.
- C
show lldp neighbor interface ge-0/0/10 detail
The detail variant of 'show lldp neighbor interface' decodes received LLDP-MED TLVs, including the extended power-via-MDI value the phone advertises. This exposes the actual requested wattage, revealing why the device draws more than its initial hardware class permits.
- D
show ethernet-switching interfaces lldp ge-0/0/10
Why it fails: Ethernet-switching does not house LLDP operational command outputs.