Juniper Networks unveiled its next generation, T1600 core router featuring 1.6 Tbps of throughput in a single half-rack chassis. Juniper is aiming the platform at “new, rich-media, experience-based services” which require core routers to feature much higher performance, openness and the ability to support customized service delivery.
Significantly, the T1600 offers 100 Gbps per slot, a capability driven by new, dual 50 Gbps ASICs. This capacity allows two OC-768 (40 Gbps) interfaces per slot today, or 8 x OC-192 per slot, while allowing future 100G interfaces. The T1600 uses compatible with Juniper’s existing PIC/FPC interface cards, including the existing 10GE optical interfaces and 40 Gbps interface cards.
As for optical network integration, the T1600 supports OC-768 over dark fiber; 10GE tunability within C-Band via JUNOS CLI; and OC-768 Inverse Mux capabilities on OC-192 Short reach XFPs. It also delivers MPLS control of end-to-end transport paths and supports an open GMPLS optical control plane.
The T1600 uses the same JUNOS operating as the existing T-series routers. All JUNOS features are supported on the T1600, including recently introduced point-to-multipoint (P2MP) MPLS capabilities for efficient core video distribution.
As with all Juniper routers, the T1600 is fully policy-enabled and managed through the recently announced Session Resource Control (SRC) product family.
On a full-rack basis, two T1600 routers would deliver up to 3.2 Tbps of throughput in a single, standard 7-foot rack. Compared to the competition, this represents 2.5X capacity in the same footprint.
Juniper lists a number of other strategic differentiators, including:
- Energy efficiency — the T1600 consumes 30 percent less power and requires 30 percent less cooling than competitive platforms.
- OS compatibility with its installed base.
- Migrating path for existing T640 routers — the upgrade to a T1600 takes as little as 90 minutes and can be performed without service interruption.
The T1600 core router is expected to be generally available for deployment in Q407.
http://www.juniper.net
