Foundry AccessIron: Access Routers for Branch and WAN Edge

01 /What AccessIron was

AccessIron was the Foundry Networks entry into access routing around 2001. Where NetIron sat in the core, AccessIron was meant for the branch office and the WAN edge: a compact router with Ethernet on the LAN side and T1/E1, fractional T1, serial or ISDN interfaces toward the carrier, running a CLI in the IronWare style so that a Foundry-trained engineer could manage the WAN without learning a second command language. The routing hub covers the protocols involved.

The AR1200 series is the model name most often cited in forum posts and resale listings. Specific model numbers, interface counts and software versions are hedged here because surviving documentation is sparse and inconsistent.

02 /Role in the network

An access router terminates a carrier circuit, encapsulates IP in PPP, HDLC or Frame Relay on the WAN side, and routes to the branch LAN. It usually adds NAT, access lists, a DHCP server and static or RIP routing toward headquarters, with OSPF on larger sites. AccessIron did those things. The intended buyer already ran FastIron switches in the branch and BigIron or NetIron at headquarters, and wanted one vendor and one CLI end to end.

03 /Why it did not last

Foundry built its reputation on Ethernet switching ASICs, where it could beat larger vendors on price per port and forwarding rate. Branch routing rewarded different things: a huge catalogue of WAN interface cards, mature support for every carrier encapsulation, voice integration, and a global reseller channel that already sold one dominant brand. AccessIron offered none of those advantages, and the branch router market was consolidating around incumbents. Foundry withdrew the line around 2004 and concentrated on switching, load balancing and core routing, as described on the company history page.

04 /The command reference that outlived the product

The most durable trace of AccessIron is a URL. The Foundry command reference PDF was hosted under the AccessIron documentation path, and because it covered the IronWare command set broadly, forum posts and course notes linked to it as a general Foundry CLI reference for years after the routers themselves disappeared. Many visitors who follow those links are looking for switch commands, not WAN configuration. The CLI command reference page on this site is the place to go for that.

show version
show interfaces brief
show ip route
show ip interface
show running-config

05 /AccessIron today

The line is purely historical. T1 and E1 circuits have largely been replaced by Ethernet handoffs and broadband, so the WAN interfaces have no modern use, and there is no software or documentation support from any successor vendor. A surviving unit is a collector item. Its only practical role is as a small IronWare-style CLI trainer if the Ethernet side still works, and even then a FastIron switch is a better and more common choice.