- Introduction to IOx
- IOx Edge Compute Devices
- IC3000-series
- IR 800-series
- IR 1100 Series
- IE 4000-series
- IE3x00 Series
- IE93xx Series
- CGR 1000 Compute Module
- ISR 800-series
- Catalyst 9000-series
- ISR 4000/ASR 1000-series
- Comparison of IOx Devices
- IOx Resource Downloads
- IOx Local Manager
- IOx Development Tools
- ioxclient Reference
- What is ioxclient?
- Profiles
- App management
- App file management
- App console
- Service management
- Platform management
- Getting CAF Metrics
- Manage devices
- Managing logical networks
- Manage platform log files
- Manage package signature validation
- Debuggability and Diagnostics
- Platform Certificates
- Smart License Management
- Cartridge management
- Messaging service
- Docker commands
- Docker Layers
- Docker Toolchain Setup
- ioxclient Reference
- IOx App Tutorials
- Docker Applications
- Overview
- Tutorial: Deploy Dockerhub Image
- Tutorial: Create Custom Package Descriptor for Docker Apps
- Tutorial: Build Sample Docker Type IOx app Using Docker Toolchain
- Tutorial: Build Sample Docker Type Python Simple App
- Tutorial: Build Sample Docker Type C Based Simple App
- Tutorial: Build Sample Docker Type Python with C App
- Tutorial:Build Sample Docker Type C++ Based Simple App
- Tutorial: Build Sample Docker Type nodejs Based HTTP Server Using Alpine Base Image
- Tutorial: Build Sample Docker Type IOx App That Consumes GPS Service
- VM Applications
- Legacy Styles
- Docker Applications
- IOx App Concepts
- Advanced Features
- Application Groups
- Remote Docker workflow
- OVA to IOx VM App Package Deployment
- Debuggability and Diagnostics
- USB Storage and Serial Device
- IOx Services
- Key Value Datastore
- Cisco Local Manager Based App Console Access
- Fog Director API Documentation
- IOx Smart Licensing
- Access GPS data from an IOx App via serial interface on IR1101
- Troubleshooting Guide
- Developer Resources
- Community and Support
Cisco IC3000 Industrial Compute Gateway
The Cisco IC3000 Industrial Compute Gateway delivers a higher level of computational power and storage when compared to other Cisco IOx enabled devices. It enables many applications that demand more processing power for data analytics and real-time critical decision making at the edge of the IoT. For example, it enables smart roadway applications such as traffic pattern detection, hazardous weather warnings, and road condition detection. The IC3000 can also be used in many other industrial use cases where you need more compute and storage offered by IOx on our industrial switches and routers network.
The Cisco IC3000 Industrial Compute Gateway is fully supported by Cisco IoT Field Network Director (FND) for zero-touch deployment, lifecycle management, application management, monitoring, and troubleshooting securely at scale from a single pane of glass.
The Cisco IC3000 has two Ethernet ports and two Small Form-Factor Pluggable (SFP) fiber ports in a DIN rail-mounted, ruggedized appliance that provides the widest range of applications for the harshest and most demanding industrial environments.
Learn more about Cisco IC3000 Industrial Compute Gateway on Cisco.com
Hardware Specifications
- 4-core Intel Atom Rangeley (industrial temperature [I-temp])
- 8-GB DRAM (soldered down)
- 16-GB onboard flash memory
- 128-GB mSATA
- SD card slot
- Mini-USB and RJ-45 connector for serial console
- USB ports for USB mass storage and USB-serial converters
- Dedicated 10/100/1000 management port
- Hardware-based anti-counterfeit, anti-tamper chip
- Factory reset option
- Alarm port on IC3000 is physically present but not supported in IOx
- More information in the data sheet available on Cisco.com
Software Release
Software Version
| IC3000 Release | IOx Version | Release Date | Comment |
|---|---|---|---|
| 1.2.1 | 2.0 | 29-Nov-2019 | |
| 1.1.1 | 1.8 | 04-Sep-2019 |
Software can be downloaded from Cisco.com Software Center
Docker Engine Support
- In IC3000 software release 1.2.1 available on Cisco.com, Docker IOx applications are supported and IC3000 runs docker engine natively. One enhancement that comes along with this change is that now the docker apps can be activated with standard docker runtime options. Check out below diagram on how to pass docker runtime options while activating the app via Local Manager.
List of Unsupported Docker Runtime Options
The following runtime options in Docker are not supported in IOx Application hosting framework.
| Options | Comments |
|---|---|
| --attach | Attach to STDIN, STDOUT or STDERR |
| --blkio-weight-device | Block IO weight (relative device weight) |
| --cgroup-parent | Optional parent cgroup for the container |
| --cidfile | Write the container ID to the file |
| --cpu-count | CPU count (Windows only) |
| --cpu-percent | CPU percent (Windows only) |
| --cpus | API 1.25+ |
| --device-cgroup-rule | Add a rule to the cgroup allowed devices list |
| --device-read-bps | Limit read rate (bytes per second) from a device |
| --device-read-iops | Limit read rate (IO per second) from a device |
| --device-write-bps | Limit write rate (bytes per second) to a device |
| --device-write-iops | Limit write rate (IO per second) to a device |
| --disable-content-trust | Skip image verification |
| --env-file | Read in a file of environment variables |
| --interactive , -i | Keep STDIN open even if not attached |
| --io-maxbandwidth | Maximum IO bandwidth limit for the system drive (Windows only) |
| --io-maxiops | Maximum IOps limit for the system drive (Windows only) |
| --ip | IPv4 address (e.g., 172.30.100.104) |
| --ip6 | IPv6 address (e.g., 2001:db8::33) |
| --isolation | Container isolation technology |
| --link | Add link to another container |
| --name | Assign a name to the container |
| --oomkilldisable | |
| --pid | PID namespace to use |
| --platform | experimental (daemon)API 1.32+ |
| --privileged | Give extended privileges to this container |
| --runtime | Runtime to use for this container |
| --storage-opt | Storage driver options for the container |
| --sysctl | Sysctl options |
| --tty , -t | Allocate a pseudo-TTY |
| --userns | User namespace to use |
| --uts | UTS namespace to use |
| --volume-driver | Optional volume driver for the container |