Allied Telesis 5 YEAR OPENFLOW V1.3 LICENSE FOR AT-X230 SERIES SWITCHES - AT-FL-X230-OF13-5YR

Allied Telesis AT-FL-X230-OF13-5YR OpenFlow v1.3 5-Year Software License

Overview

The AT-FL-X230-OF13-5YR is a five-year term software license that activates OpenFlow v1.3 functionality on Allied Telesis AT-X230 series switches. OpenFlow v1.3 hands control-plane decisions to a centralized SDN controller, allowing network administrators to define forwarding rules programmatically rather than relying solely on distributed switch logic. This is the deployment path for organizations integrating AT-X230 switches into software-defined network architectures — campus edge SDN rollouts, research networks, or enterprise environments where centralized traffic policy management is operationally required. The license key is delivered as a software entitlement tied to the specific switch; without it, OpenFlow v1.3 remains inactive on the platform regardless of firmware version.

Compatibility

This license is designed exclusively for the Allied Telesis AT-X230 series managed switches. The AT-X230 family includes compact and stackable GbE switch models in the AT-X230-10GP, AT-X230-18GP, AT-X230-28GP, and AT-X230-28GT lines. The OpenFlow v1.3 protocol supported by this license is compatible with any RFC-compliant SDN controller that implements the OpenFlow 1.3 specification — including OpenDaylight, ONOS, and Floodlight. Verify your specific AT-X230 model's software feature matrix against Allied Telesis release notes before purchasing, as feature licensing availability may vary by hardware revision or firmware stream. This license does not apply to AT-X230L, AT-X510, or any other Allied Telesis switch series outside the AT-X230 product line.

Installation Notes

License activation requires access to the switch CLI or AlliedWare Plus GUI. Apply the license key using the license certificate command in AlliedWare Plus; the switch must be reachable and running a firmware version that supports OpenFlow v1.3 for the license to register correctly. After activation, configure the OpenFlow controller IP and port via the openflow configuration context. Note that enabling OpenFlow v1.3 on a switch changes forwarding behavior — traffic that does not match an installed flow rule defaults to the controller or is dropped depending on your fail-secure/fail-open policy. Plan controller connectivity and failover before cutting over production traffic.