CCNA IP Telephony Features Questions

IEEE 802.1X port-based authentication with dynamic VLAN assignment verifies device identity against a RADIUS server before granting network access, then assigns the voice VLAN only after successful authentication. This prevents rogue devices from spoofing LLDP-MED TLVs to obtain voice VLAN membership, satisfying the requirement to block unauthorised masquerading as IP phones.

LLDP-MED's extended power-via-MDI TLV lets the endpoint advertise its precise power requirement, so the switch allocates exact wattage instead of reserving the full IEEE 802.3af class maximum. This granular negotiation avoids over-reserving power budget on EX Series switches.

LLDP-MED voice VLAN information travels in the network policy TLV, which is only emitted when a network policy is defined and mapped to the interface or device profile. LLDP frames transmit regardless, matching the observed symptom of no voice VLAN TLV.

`show poe interface` displays per-interface PoE state, allocated class, and measured power draw for every port on the EX2300, satisfying the requirement to check all connected IP phones across all interfaces simultaneously. It reports the exact operational fields the administrator needs without filtering to a single port.

Consumption mode still reserves power at the class maximum before boot completes, because LLDP-MED or CDP power negotiation has not yet reported actual draw. With the static reservation table full, that initial allocation fails, so the switch denies power.

The voice-vlan statement on an access port makes Junos treat the port as untagged for data in the native VLAN while recognising 802.1Q-tagged frames for the voice VLAN ID, delivering simultaneous segregation without trunk configuration.

The LLDP-MED Capabilities TLV is mandatory for LLDP-MED operation and advertises supported media features, letting the switch classify a device as a media endpoint rather than an infrastructure node. It satisfies the requirement to distinguish endpoints from standard switches and routers.

Link Layer Discovery Protocol – Media Endpoint Discovery extends IEEE 802.1AB LLDP with TIA-1057 TLVs, enabling automatic VLAN assignment, PoE negotiation and E911 location data for IP phones. This satisfies the stem's IP telephony context, where media endpoint discovery beyond standard LLDP is required.

LLDP-MED conveys the voice VLAN through a network policy TLV, so an LLDP-MED network policy defining VLAN 50 must exist and be applied to the interface. Without it, no policy is advertised and the phone cannot discover the voice VLAN, satisfying the stem's discovery requirement.

The phone acts as a Layer 2 pass-through for the attached PC. PC frames remain untagged and are forwarded into the port's native VLAN, while the phone's own voice frames carry an 802.1Q tag, keeping data and voice traffic logically separated.

In 'consumption' mode, the switch allocates power based on the actual power consumption of the device, measured in real time. This allows more efficient use of the power budget, as devices that draw less than their class maximum free up power for other ports. It is ideal for PoE+ phones with varying power needs.

On Junos EX switches, PoE ports default to low priority when no explicit priority is set. Under constrained power budgets, allocation follows port index order, so ge-0/0/0 would need an explicit high priority to be prioritised for the emergency IP phone.

Assigning high PoE priority to critical IP phone ports ensures the switch sheds lower-priority powered devices first when demand exceeds the EX4300's power budget, keeping phones online during the deficit. This directly mitigates the shortfall by controlling which ports lose power, rather than reducing total consumption.

The 'Disabled' status in the PoE output indicates that PoE is administratively disabled on that interface. This can be set with 'set poe interface ge-0/0/10 disable'. Even if the interface is up and LLDP works, PoE will not be supplied until it is enabled. This is a common oversight when PoE is disabled per port for security or power-saving reasons.

The LLDP-MED network policy TLV carries the VLAN ID, identifying the voice VLAN that the endpoint must tag its traffic with. This satisfies the voice application policy requirement by directing the phone to the correct Layer 2 segment.

Port priority (low, high, critical) is configurable per interface under PoE settings, letting administrators rank power allocation when the switch's budget is exhausted. Critical interfaces receive power first, then high, then low, satisfying the stem's requirement for explicitly manageable per-interface PoE parameters on EX Series switches.

Network policy TLVs include Layer 2 priority (802.1p) and DSCP values, enabling the phone to mark voice traffic appropriately for QoS. This ensures that voice packets are prioritized across the network. These parameters are essential for maintaining voice quality in congested networks.

LLDP-MED network policy TLVs let the switch push VLAN ID, 802.1p priority and DSCP values to attached endpoints, so voice, video and guest traffic land in the correct VLAN automatically. This is the policy automation behaviour Junos EX Series implements for media endpoints.

In class-based mode, the switch reserves power for each device according to the PoE class it reports during detection and classification, using the class maximum rather than actual consumption. That makes the budget predictable, but it can leave unused headroom, because many phones in Class 3 draw much less than 15.4 W. 'show poe controller' shows the mode, total budget and power in use.

A 'Hardware error' PoE status indicates the port's power controller or the supplying PSU cannot deliver power, so verifying chassis power and PoE controller health isolates whether the fault is internal hardware rather than the phone or cabling.

LLDP-MED network policy TLVs are only transmitted when a policy is explicitly configured under the lldp-med hierarchy. Enabling lldp-med on the interface alone advertises capabilities and inventory, but no voice VLAN or Layer 2/3 priority data. Creating a network policy with application type voice, the target VLAN ID, and the desired DSCP/CoS mapping gives the phone the exact parameters it needs to tag frames and join the voice VLAN.

To advertise the voice VLAN to LLDP-MED capable phones, you must configure a network policy that specifies the application type as 'voice' and the VLAN ID. This policy is then sent in LLDP-MED TLVs, allowing the phone to automatically tag voice traffic with the correct VLAN. Without this, the phone will not receive the VLAN information and may not function correctly on the voice VLAN.

In class mode the switch reserves power per port based on the advertised class, and if the total reserved power exceeds the available PoE budget, later ports may be powered briefly and then dropped, causing a boot loop. Checking the budget and the sum of reservations identifies this condition, and adding power or reducing powered ports restores stable operation.