Cruz Operation Center Quick Start Guide

The Cruz Operations Center (CruzOC) Quick Start Guide outlines the steps to install the standard standalone CruzOC system and its subsequent first use. This  guide is suitable to get most users up and running quickly. 

This guide does not describe all the details of available installations. Refer to the installation guide for detail on other installation options. 

A typical installation includes the following: 

  • Installing and System Startup (10-20 minutes depending on the Server) 
  • Getting Started 
  • Explore the Software 
CruzOC is shipped in one of three configurations: 
    • Windows OS - self-extracting .exe file 
    • Linux OS (Redhat/Centos) - self-extracting .bin file 
    • Virtual Appliance - A single ova file, which is a VM for VMware platforms. It comes with CruzOC pre-installed on Linux. Refer to the Virtual Appliance Installation Guide. 

    Installation 

    Steps for Windows and Linux Deployments: 

    Download the appropriate self-extracting file onto your host server.
      • On Windows, log in with administrator privileges. 
      • On Linux: 
        • Make sure that the installation executable has permission to execute. 
        • Do not install as the root user.  Although the root credentials will be required at one step where you'll open a new terminal session and execute a command with root access. 
      • Virtual Appliance Linux: 
        • Refer to the Virtual Appliance install guide for instruction on deploying the pre-installed software with the Linux OVA (link ). If already installed You can skip to the Getting started section of this doc.
    Execute the .exe or .bin file to install 
    • Follow the prompts.
      • When asked to select the number of devices, choose the number of devices that represent the devices you will manage in your production network. This selection is used to tune various system settings and to auto-size the installation for best performance. The amount of RAM shown in parenthesis is the expected RAM resources required to support the selected number of devices on the host machine. Make sure the system has enough resources.  Refer to the the deployment sizing guide.
      • Follow the additional prompts to complete the installation. When complete you will see a screen that says Install Completed Successfully along with a Server Status Console
        that shows the startup status for the  Application, Web and DB servers. 
      • When all three are green you may access the system using the Launch Web Portal  button or go to http:// [hostname or host IP address]:8080 (example http://10.10.10.10:8080). 
      • The default login credentials are username=admin /  password = admin 
      • Web UI Screen resolution should equal or exceed 1280 x 1080 pixels. 
      • The Application and Wed Server Status (service) icons are also auto installed in the windows tray.    
      • Right-click the appserver tool in the system tray to Start or Stop the Service. 
      • Right-lick the network management tool for the Web server in the system tray and select Start or Stop the Service. 
      • On Linux, the status is available from the command line.  On Linux, servers are set up to auto start as a service after reboot. You can stop, start or check status with these commands:
        • Application server: sudo service oware start | stop | status
        • Web server: sudo service synergy start | stop | status
        • Database Server: sudo service owaredb start | stop | status 

        Getting Started (Post installation) 

        The best place to start is at the Getting Started portlet on the Home Page. Once you have completed the steps, you will have a fully  operational system and you will be ready to explore more advanced features and configuration. If help is needed along the way, look for this (Need ICON) icon to link to online help. Getting started video 

        Best practices 

        One of the Getting Started tasks is to discover your network. 

        • It is not uncommon to encounter discovery obstacles due to firewall or network issues that  prevent CruzOC from contacting the target devices. Verify firewalls have the required open ports between devices and your server. An easy way to confirm whether your firewall is completely configured is to take down the firewall, install the application and interact with the devices, then put the firewall back up. If the application functions while the firewall is down, but does not when it is up, then you have missed some port(s). 
        • Common protocols for CruzOC include SNMP, Telnet, SSH, FTP, TFTP, WMI, WBEM. These should  not be blocked in the network. There is a complete list on the KB 
        • To speed up the Getting Started tasks, create a list of devices, IP addresses, ranges that  you want to bring under management. Record their authentications (login[s]/password[s]). Typically, these include both SNMP communities and command line (Telnet/SSH) authentications. If discovering servers, WMI or WBEM, OS administrator credentials are required. 
        • Discovery option "Attempt to enable Auto configure SNMP" which will attempt to configure SNMP on common vendor equipment if the option is checked. This feature is designed to new environments where no snmp has been configured. It will apply snmpv2 configuration to the devices. The community set will correspond to the SNMP Authentication you provide in the discovery profile.    This is located on the Resources  -> Discovery menu  > Discovery profile -> right click -> New > General Tab > Configure SNMP 
        Other Post-Install Checks 

        Reports 

        Reports can be created as HTML, CSV, and PDF. Since PDF is the default format, Adobe must be enabled in the browser. If PDFs are to be viewed outside a browser,  Adobe will need to be installed on the OS. 


        Register or Import License 

        • Register License via GUI interface 
        • Click on Settings > License Management > Register License Tab > select License > select license.xml 


        What is features are ready to use? 

        • Once you have completed the Getting Started tasks go to the Resource menu.  Here you should see your devices. Select a row, left click, and then right click to see the options. 
        • If devices have been configured to send traps to CruzOC, you can manage alarms and events. 
        • The Performance tab should now have data. You can create dashboards. 
        • If devices have been configured to send CruzOC flow data, the Traffic Flow portlets will show flow information. 
        • Topology will show your devices and links and any alarms. Play with layout and saved views. 
        • Configuration Management will show file backups, schedules and alarms, and firmware images that are ready to deploy. 
        • Compliance Menu will show compliance policies, but you can also create your own. 
        • Automation/Action Menu - Actions (CLI scripts) can be executed against target equipment or you can easily create your own. Here, you can also create your own event-based automation or set up syslog escalation, correlation, and event override automation. 
        • Report Menu - click the search link and enter Inventory. Right click > Execute Report to run a report. See My Alerts bottom left for the report. 
        • Go to Help and Support, upper right and explore the options. 
        • Create new users (see the User Guide

        Additional Setup Quick Tips 

        Explore the Software (videos). Or refer to the User Guide for each of these areas

        • Getting Started 
        • Portal Configuration 
        • Resources Management 
        • Presentation Capabilities 
        • Generating Reports 
        • Alarms, Events, and Automation 
        • Performance Monitoring 
        • Managing File Servers/Files 
        • Change Management/ProScan 
        • Traffic Flow Analyzer 
        • Actions and Adaptive CLI 
        • Serving Multiple Customer Accounts 
        • Troubleshooting Your Application 
        • Integrating with Other Products and Services 
        • Localization 
        • Configuring Virtualization 
        • Virtualization Management 
        • Ports Used 
        • RESTful Web Services