JUNIPER EX2300-24T-DC EX2300 Series Ethernet Switches

EX2300-24T-DC Hardware Identity

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

Port and power boundary

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

EX2300 architecture control

EX2300 acceptance should reflect a compact access-switch design. Record the fixed power arrangement, access-port population and the exact number of SFP/SFP+ uplinks on this model. If Virtual Chassis is planned, Juniper documents a maximum of four EX2300 members and requires SFP+ rather than SFP transceivers for VCP links. Preserve member IDs, VCP optics, Junos release and recovery behavior. Do not borrow EX3400 redundant-supply or larger-chassis assumptions.

Order-form control 1

DC power acceptance requires two documented feed paths where redundancy is designed, correct protective devices, conductor sizing, polarity, grounding and terminal hardware. Measure input before connecting the switch, label each feed and test loss of the approved source. Do not install an AC supply or assume an AC cord is part of this order. Preserve the facility drawing and supply labels with the serial record.

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.

SKU-specific acceptance

For the DC twenty-four-port switch, document feed polarity, protective device, grounding and the absence of PoE before site release. Perform DC acceptance before endpoint migration: measure the feed, verify polarity and grounding, confirm no PoE requirement exists and test the four uplinks. Record the switch's fixed access purpose and external endpoint-power dependencies. A powered device appearing in the migration list reopens the design review.

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.

TAA control

Keep the complete TAA-qualified order code on the quote, invoice, carton and asset record. Validate procurement eligibility with the contracting authority rather than a shortened base model.

PoE firmware

For multigigabit PoE platforms, verify Junos and PoE controller firmware before enabling higher-power modes. Test representative endpoints and record negotiated class.

Install base

Register additions and FRU changes under the correct support record. Keep serial, site, power, airflow and module inventory synchronized with the operational asset system.

Optics bill

List each optic, cable type, reach, connector and peer interface. Chassis port count does not include the transceivers needed for an operational link.

Related Juniper EX records

• EX2300-24P-VC switch record
• EX4300-48P-TAA switch record
• EX4300-48T-DC-AFI switch record

Official Juniper evidence

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