EX3400-48T-TAA Juniper EX3400 Series Ethernet Switches

EX3400-48T-TAA Hardware Identity

EX3400-48T-TAA is a Juniper EX3400 fixed-configuration Ethernet switch. Its verified hardware profile is 48 10/100/1000BASE-T access ports; no PoE on access ports. The complete code carries TAA procurement-qualified order suffix. Preserve every suffix on the quote, carton and asset record.

Port and power boundary

no PoE budget. The uplink configuration is four SFP+ uplinks. Optics, optional uplink modules, cables and any separately ordered power or mounting items must be reconciled in the final bill of materials.

EX3400 architecture control

EX3400 acceptance should cover its access role, four fixed SFP+ uplinks and field-replaceable power design. For PoE models, compare the one-supply and two-supply budgets and test powered-device continuity under the approved redundancy state. Keep the selected Junos release, power-supply identities, uplink optics and Virtual Chassis plan with the chassis record. Evidence from a similar EX2300 port count does not prove EX3400 power or recovery behavior.

Order-form control 1

AC power acceptance requires the supported input range, regional cord, receptacle, circuit capacity and selected supply wattage to be documented. Where redundant supplies are used, place them on the intended independent circuits and test loss of one feed. Do not substitute a DC chassis or mix supply wattage or airflow. Retain supply serials, cord type and circuit labels with commissioning evidence.

Order-form control 2

Where the PID has no explicit AFI or AFO suffix, use the Juniper model table and actual FRU labels to establish the shipped airflow. Record intake and exhaust orientation before rack placement, and reject any replacement fan or supply whose airflow differs. The absence of a suffix is not permission to mix directions or to infer the pattern from another chassis.

Order-form control 3

The TAA suffix is part of the procurement identity. Keep the full PID unchanged through quote, purchase order, invoice, carton inspection and asset registration, and let the contracting authority decide eligibility. A base model, VC line or non-TAA substitute requires a new compliance review; technical equivalence alone does not preserve the purchasing requirement.

SKU-specific acceptance

For the EX3400 non-PoE TAA order, verify access-port inventory and uplink optics while documenting that no powered-device budget applies. Use a 48-port non-PoE acceptance matrix covering speed, VLAN, authentication and uplink path. The TAA file must retain supplier, invoice, chassis label and asset identity, while technical evidence proves no PoE budget was expected. Any proposed 48P replacement requires a new power and contract review.

Exact-SKU deployment record

This EX3400-48T-TAA record must explicitly show that forty-eight access ports are non-PoE while the chassis still uses a field-replaceable power architecture. Inventory both power-supply bays, installed 150 W supply identity, circuit assignment and the approved redundancy state. Stage the four fixed SFP+ uplinks with exact optics and peer links, then test one feed or supply loss without adding powered-device expectations. The contracting file retains the complete TAA code separately from technical evidence. During migration, compare VLAN, authentication, LAG, routing and monitoring behavior with the old switch, and keep temperature, fan, power and interface alarms through the first production cycle. This workflow distinguishes the EX3400 from a fixed-power EX2300 with the same copper port count.

Junos baseline

Record the approved Junos release and hardware support evidence before staging. Preserve the initial configuration, rescue state and post-upgrade validation.

Uplink plan

Map every uplink speed, optic, breakout, LAG member and peer. Optional uplink modules and transceivers must appear as separate bill-of-material lines where required.

Capacity test

Measure representative access, uplink and control-plane load after staging. Preserve errors, drops, temperature and latency rather than accepting link-up alone.

Failure domain

Define what remains online after loss of one feed, supply, fan, uplink or VC member. Test the approved failure case and retain recovery timing.

PoE load

Build a port-by-port powered-device budget with startup draw, redundancy state and spare margin. Do not equate a PoE-capable port count with enough available watts.

Virtual Chassis

Document member role, Junos release, VCP media, topology and rollback. A VC order qualifier or physical VCP does not remove software and compatibility checks.

Related Juniper EX records

• EX4300-48P-TAA switch record
• EX4300-48T-TAA switch record
• EX4300-32F-TAA switch record

Official Juniper evidence

EX3400 system overview and model table. Verify the current hardware guide, supported Junos release and lifecycle notice at the final design date.