- Support Portal
- Troubleshooting
- Common Issues
-
Getting Started
-
Docs
-
Product Overview Videos
-
Alerts
-
Product Tutorials
-
Features
- Getting started
- User Interface
- Discovery
- Monitoring
- Topology
- Configuration Management - Backup Restore, Firmware Deploy
- Alarms Events and Syslogs
- Automation and Event processing Rules
- Traffic Flow
- Reporting
- Server Management
- Systems Administration
- Actions
- Installation and Upgrade
- Hyper Converged Infrastructure
- Video Archive
- Cruz Edge Orchestrator
- Compliance
- Hierarchy Views
- User Roles and Permissions
-
Troubleshooting
-
Integration
-
Discovery
-
Performance Monitoring
-
System Administration
-
Services
-
Fabric
How to create CLI trace file
At times, backup restore or deploy or other command line operations will finish with errors for unknown reason. To figure out what went wrong, a CLI trace will need to be turned on.
Following steps are needed to enable CLI trace:
1. Navigate to ..\owareapps\installprops\lib directory
2. Edit installed.properties file
3. Add following lines to the end of the file
a. oware.ezmediation.enable.debug=true
b. oware.ezmediation.enable.packet.level.trace=true
4. Save file
5. Restart appserver/webserver for the change to take effect
To create a cli file, a backup, restore or deploy needs to be executed and once executed, the cli file will be located in ..\oware\temp directory