Install Orb Using IOx Local Manager
- Introduction
- Prerequisites
- Building Your IOx Package
- Step 1: Enable IOx on Your Device
- Step 2: Access IOx Local Manager
- Step 3: Upload the Orb Application
- Step 4: Activate the Application
- Step 5: Start the Application
- Step 6: Verify Installation
- Step 7: Configure Persistent Storage (Optional)
- Network Configuration Options
- Troubleshooting
- Updating the Orb Sensor
- Additional Resources
This documentation is in beta and intended for advanced users. If you encounter issues or have questions, please reach out to [email protected] or join our Discord community.
Introduction
This guide walks you through deploying the Orb sensor using IOx Local Manager, a web-based interface for managing IOx applications on Cisco devices. This method is ideal for Catalyst switches, ISR routers, and industrial IoT gateways where you prefer a GUI-based workflow.
Prerequisites
Before you begin, ensure you have:
- A compatible Cisco device with IOx enabled (see compatibility list)
- IOS XE 16.12.1 or later
- Web browser access to the device's IOx Local Manager interface
- An IOx package (
package.tar) containing the Orb sensor and your deployment token - An Orb deployment token
Building Your IOx Package
Pre-built packages are coming soon. In the meantime, you must build your own package.tar that includes your deployment token. Follow the Building the IOx Package section in the ioxclient guide to create your package using the IOx SDE.
Once you have your package.tar, return here to deploy it via IOx Local Manager.
Step 1: Enable IOx on Your Device
Before accessing IOx Local Manager, enable IOx on your Cisco device via CLI.
Enable IOx Framework
Connect to your device via SSH or console and enter configuration mode:
configure terminal
iox
endVerify IOx Services
Wait a few minutes for IOx services to initialize, then verify:
show iox-serviceAll services should show as Running:
IOx Infrastructure Summary:
---------------------------
IOx service (CAF) : Running
IOx service (HA) : Not Supported
IOx service (IOxman) : Running
Libvirtd : Running
Dockerd : RunningStep 2: Access IOx Local Manager
Open a web browser and navigate to the IOx Local Manager interface:
- IR1101, IE3x00 series:
https://<device-ip>/iox/login - Other devices:
https://<device-ip>:8443
Log in using your IOS XE credentials.
Step 3: Upload the Orb Application
- Navigate to Applications in the left menu.
- Click Add New.
- Enter an Application ID:
orb - Click Choose File and select your
package.tarfile. - Click OK to upload.
Wait for the upload to complete. The application will appear in the list with status DEPLOYED.
Step 4: Activate the Application
- Select the orb application from the list.
- Click Activate.
Configure Resources
On the Resources tab:
- CPU: 400 units (or as specified in your package)
- Memory: 80 MB
- Disk: 10 MB
Configure Network
On the Network Configuration tab:
- Click eth0 to configure the network interface.
- Select Network Name:
iox-nat0(or your configured network) - For IP assignment, select either:
- DHCP: For automatic IP assignment
- Static: Enter a specific IP address, netmask, and gateway
- Click OK.
Apply Activation
Click Activate App to complete the activation process.
The application status will change to ACTIVATED.
Step 5: Start the Application
- Select the orb application.
- Click Start.
The status will change to RUNNING.
Step 6: Verify Installation
Check Application Status
- Select the orb application.
- Click Manage.
- Review the App Info tab to confirm the application is running.
View Logs
- In the Manage view, click the Logs tab.
- Select the log file to view Orb sensor output.
- Verify the sensor has connected to the Orb service.
Your Orb sensor will automatically register with your account using the deployment token embedded in the package.
Step 7: Configure Persistent Storage (Optional)
To preserve data across reboots, configure a data volume:
- In the Manage view, click App-DataDir.
- The
/datadirectory contains Orb configuration and measurement data. - This directory persists across application restarts.
Network Configuration Options
IOx supports several network configurations depending on your deployment needs:
NAT Mode (Default)
The container uses the device's management IP with network address translation. This is the simplest configuration and works for most deployments.
Bridge Mode
For direct Layer 2 connectivity:
- Create a dedicated VLAN on the device
- Configure an AppGigabitEthernet interface as a trunk
- Assign the VLAN to the container network
Static IP
For deployments requiring a specific IP address:
- During activation, select Static for IP assignment
- Enter the desired IP address, netmask, and gateway
- Ensure the IP is routable from the device
Troubleshooting
Cannot Access IOx Local Manager
If you cannot reach the Local Manager interface:
- Verify IOx services are running:
show iox-service - Check the management interface has connectivity
- Ensure HTTPS (port 8443) is not blocked by ACLs
- Try accessing via HTTP if HTTPS fails:
http://<device-ip>:8080
Application Won't Start
If the application fails to start:
- Check resource allocation doesn't exceed device limits
- Verify the network configuration is correct
- Review application logs for error messages
- Ensure the package was built for the correct architecture
Network Connectivity Issues
If the Orb sensor cannot reach the internet:
- Verify NAT is configured on the device for the container network
- Check DNS resolution is available to the container
- Ensure firewall rules allow outbound HTTPS traffic
- Test connectivity from the device management interface first
Out of Disk Space
If you see disk space errors:
- Check available storage:
show platform software iox-service storage - Remove unused applications to free space
- Consider using external USB storage for data-intensive deployments
Updating the Orb Sensor
To update to a newer version:
- Stop the running application: Click Stop
- Deactivate the application: Click Deactivate
- Delete the application: Click Delete
- Upload the new package following the installation steps
Your deployment token and configuration are embedded in the package, so you'll need to rebuild the package with your token before uploading.