Question 470
At a new office connecting VoIP phones to EX access switches, a Junos specialist investigates this scenario: A new IP phone requests a higher supported power class but is limited to a default allocation and fails to start. The rollout must support phones and connected workstations securely. Which precaution should be checked before committing the change?
Explanation
Correct Answer
For a new office connecting VoIP phones to EX access switches, the relevant safeguard is: Verify the negotiated class and switch feature support before overriding port power limits. It matters while implementing: Enable appropriate PoE class handling and compatible power negotiation for the phone. The fault involves: PoE power classification informs the power source of the powered device's required allocation. The required acceptance result remains: Switch power telemetry shows the correct allocated class and the phone operates stably.
Incorrect Answers
Voice VLAN tagging and QoS classification must be mapped to the correct switch forwarding treatment. The appropriate correction for the reported case is: Verify the negotiated class and switch feature support before overriding port power limits.
PoE availability depends on available switch power budget and each attached device's negotiated consumption. Fixing that different mechanism would not address the current root cause: poE power classification informs the power source of the powered device's required allocation.
Supported LLDP-MED or LLDP power TLVs can negotiate endpoint power requirements beyond static class assumptions. Its verification is distinct from the reported condition: A new IP phone requests a higher supported power class but is limited to a default allocation and fails to start. The rollout must support phones and connected workstations securely.