Pica8 Operating System PicOSTM

Leverage Tools Multiprocess OS The first Open Switch for open customize, optimize networks leveraging unique hardware-agnostic operating system Two powerful modes of operation to suit your needs Linux Routing Security Switching OpenFlow Open vSwitch (OVS) Mode: providing Mangement Industry leading OpenFlow support & Linux integration with CloudStack or OpenStack

Process traffic Layer-2/Layer-3 Mode: enabling seamless Hardware Abstraction Layer abstracted from integration into existing networks underlying hardware Single OS Drives Operational Efficiencies Overview Pica8 is the first to offer hardware-independent open switches. Physical "white box" switch hardware run PicOS™, an open network operating system that supports standards-based Layer 2/Layer 3 protocols with OpenFlow support. What makes PicOS open?  PicOS is hardware independent: the operating system is not tightly coupled to switching ASICs, CPU or memory hardware.  We expose Debian Linux, so you can use your existing tools for programming and optimizing Pica8 open switches to support your network.  PicOS has the most complete OpenFlow support, through Open vSwitch (OVS) integration

Leverage Pica8’s operating system - PicOS - with two powerful modes of operation

Layer-2 / Layer-3 Mode Open vSwitch (OVS) Mode

 Switching platform with Debian  Industry-leading OpenFlow 1.3 OPEN Linux on board and accessible support through Open vSwitch  Programmable and customize by (OvS) 1.9 integration leveraging vast high-quality  Leverage production ready OVS Linux tools switches for your CloudStack / OpenStack projects

FLEXIBLE  High-performance Layer 2 / Layer 3  Interoperable with multiple switching platform for both IPv4 open-source OpenFlow controllers and IPv6 networks, seamlessly (Ryu, Floodlight, NOX, Trema) integrating into existing architectures  Leverage different controllers and  Tune the fabric to meet your appli- reference architectures cation needs, selectable store-for- ward or cut-through switching modes for ultra-low latency

ADAPTIVE  PicOS a multiprocess OS, ensures  Seamlessly add new protocols to each process has independent PicOS, a multiprocess OS memory space, thread control, and  Investment protection as your interrupt handling for improved application needs change feature scaling PROTOCOLS & STANDARDS SUPPORTED

Layer 2 Features IPv6 Layer 3 Routing Features • 802.3ab 1000Base-T • Jumbo frames up to 9,216 bytes • RIPng • 802.3z Gigabit Ethernet • Provide non-blocking wire speed • OSPFv3 • 802.3ae L2 switching • IPv6 Routing • 802.3ba 40 Gigabit Ethernet

• 128K MAC address entries (32K for the P-3290 and P-3295) Security RFCs & MIBs • Flow Control • User/Password protected • RFC-1157 SNMPv1 system management − IEEE802.3x for full duplex mode • RFC-1212 Concise MIB definition • L2/L3/L4 ACL − Back-Pressure flow control in • RFC-1213 MIB II half duplex mode • TACACS+ AAA • RFC-1215 SNMP traps • Provide Broadcast, Unicast, • SSH v1/v2 • RFC-1256 ICMP discovery Multicast storm protection • SSL v3/TLS v1 • RFC-1493 Bridge MIB • IGMP snooping, up to 1K groups • Denial of Service • RFC-1573 Interface Evolution MIB • VLAN Support Quality of Service • RFC-1643 Etherlike MIB − IEEE 802.1Q VLAN • 802.1p based CoS • RFC-1757 RMON1 MIB − 4094 VLANs • 8 priority queues per port • RFC-1901 Community based − Port-based VLAN SNMPv2 • DSCP based CoS − VLAN Trunking Protocol • RFC-1905 Protocol Operations for • Policy based Diffserv • Spanning Tree SNMPv2 • IPFIX/sFlow − STP, IEEE 802.1d • RFC-1906 Transport Mappings for SNMPv2 − RSTP, IEEE 802.1w Network Management • RFC-1907 Management Informa- − MSTP, IEEE 802.1s • Command Line Interface (CLI) tion Base for SNMPv2 • Link Aggregation via console port • RFC-1908 Coexistence between − Up to 24 trunk groups • Telnet remote login through IP management port SNMPv1 and SNMPv2 − Up to 8 ports per trunk group • SNMP v1/v2c • RFC 1997 BGP Communities − 802.3ad Link Aggregation & LACP Attribute • Provide Port Mirror (many-to-1) Open vSwitch (OVS) 1.9 • RFC-2021 RMON2 probes • LLDP • Compatible with OpenFlow 1.3 • RFC-2096 IP Forwarding table MIB • Q-in-Q specification • RFC-2233 The Interface Group MIB

• Interoperate with RYU, using SNMPv2 Layer 3 Routing Features Floodlight, Trema and NOX • RFC 2439 BGP Route Flap Damping • Maximum Routes (IPv4, IPv6): • Support GRE/MPLS/OpenFlow • RFC 2545 Use of BGP-4 Multipro- 12,000 (MPLS support on P-3780 & tocol Extensions for IPv6 Inter-Do- P-3920 only) • ECMP: 32 main Routing • RIP v2 Standards Compliance • RFC-2665 Ethernet-like Interfaces • OSPF v2 • 802.1d Bridging and Spanning • RFC 2796 BGP Route Reflection - • OSPF/ECMP Tree Protocol An Alternative to Full Mesh IBGP • VLAN routing • 802.1s Multiple Spanning • RFC 3065 Autonomous System • VRRP Tree Protocol Confederations for BGP • IP routing • 802.1w Rapid Spanning • RFC 3392 Capabilities Advertise- Tree Protocol ment with BGP-4 • DHCP-Relay • 802.1p QOS/COS • RFC 4893 BGP Support for Four-octet AS Number Space Layer 3 Multicast • 802.1Q VLAN Tagging • Pica8 private MIB • PIM-SM • 802.3ad Link Aggregation • IGMP v1/v2 with LACP

Pica8, Inc. Pica8 and PicOS are trademarks of Pic8, Inc. Corporate Headquarters Pica8 and PicOS trademarks are intended and authorized for use only in countries 1032 Elwell Court, Suite 105 and jurisdictions in which Pica8, Inc. has obtained the rights to use, market and Palo Alto, California 94303, USA advertise the brand. Pica8, Inc. shall not be liable to third parties for unauthorized 650-614-5838 | www.pica8.com use of this document or unauthorized use of its trademarks. References in this publication to Pica8, Inc. products or services do not imply that Pica8, Inc. intends © Pica8, Inc., 2013. All rights reserved. to make these available in all countries in which it operates. Contact Pica8, Inc. for Produced in the United States 08/13. additional information.