Author: Tom Oakes

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories

Installing storcli on a Cloudvue Gateway

Description

In order to interact with the RAID controller on a Cloudvue Gateway you must first install storcli.

Products

  • Cloudvue Gateway with RAID Controllers

Steps

Verification

Confirm RAID Controller Present

Use lshw to determine if a RAID Controller is present. If no results are returned then there is no RAID controller detected, thus no reason to proceed.

sudo lshw | grep -i RAID

Verify storcli is Not Installed

The following commands can be used to determine if storcli has already been installed.

which storcli
sudo find / -name storcli

Install storcli

Prep and Download Package

Update Ubunutu and download storcli

sudo apt update
mkdir Downloads
cd Downloads/
wget https://docs.broadcom.com/docs-and-downloads/raid-controllers/raid-controllers-common-files/1.23.02_StorCLI.zip

Install unzip

Install unzip and unzip storcli

sudo apt install unzip
unzip 1.23.02_StorCLI.zip
unzip storcli_All_OS.zip
cd storcli_All_OS/

Install Alien and storcli

Alien is a command line package converter. It is used to convert the storcli rpm package downloaded earlier to a deb package allowing us to install storcli using dpkg.

sudo apt install alien
cd Linux
sudo alien --scripts storcli-1.23.02-1.noarch.rpm
sudo dpkg -i storcli_1.23.02-2_all.deb

Setup Symbolic Link

For ease of use find the storcli install and then create symbolic linking allowing the storcli to be launched from any folder.

sudo find / -name storcli
cd /opt/MegaRAID/storcli
sudo ln -s /opt/MegaRAID/storcli/storcli64 /usr/local/sbin/storcli

Verify Installation

Use the which and find commands to confirm that storcli is installed.

which storcli
/usr/local/sbin/storcli

sudo find / -name storcli
/usr/share/doc/storcli
/usr/local/sbin/storcli
/opt/MegaRAID/storcli

Common storcli Commands

While there are many storcli command the following are typically the most useful when analyzing the current state of the array and physical drives

Silencing the Alarm

sudo storcli /c0 set alarm=silence

Show an Overview

sudo storcli show all

Show Detailed info for a specific controller

sudo storcli /c0 show

Show Details For All Physical Drives

sudo storcli /c0 /eall /sall show all

Additional StorCLI Controller Commands can be found on Broadcoms website at https://techdocs.broadcom.com/us/en/storage-and-ethernet-connectivity/enterprise-storage-solutions/12gbs-megaraid-tri-mode-software/1-0/v11673309/v11673749.html

Categories
Knowledge Support Cloudvue Cloudvue Cameras Support Categories Products

Adding SCP to Illustra Essentials C2C Cameras

Description 

Illustra Essential cameras were manufactured by Topview and do not include scp (Secure Copy Protocol).  As a result, files cannot be easily transferred to or from the device.  The debug.sh script can be used to temporarily install scp onto the device enabling up/downloading of files.  While scp will not survive a reboot the debug script, debug.sh does and can be used to quickly add scp as needed.

Product 

  • Illustra Essential
  • Cloudvue C2C

Prerequisites

  • Confirm the device is a Topview manufactured camera
  • Verify that debug.sh does not already exist in /home/smartvue
  • Download the debug.sh script from the support portal HERE
  • Open the debug script in Notepad++ on your machine
  • Establish an ssh session via the Cloudvue Tunneling server to the camera

Solution

Identifying a Topview Camera

The  most common ways to identify Topview manufactured cameras are: 

  • In Cloudvue Manager (Device Details > Firmware Version) look for “Essentials”
  • Check the architecture, Topview  cameras use the MIPS architecture which can be found using the uname command on the device. 
  • </code># uname -a<br>Linux Essentials4-T10A212700003131 4.1.0 #6 PREEMPT Thu Nov 24 09:54:36 CST 2022 mips GNU/Linux</code>

Creating the Debug Script

Since there is no way to initially transfer the debug script to the device it will need to be manually created.  This is done by cutting and pasting the contents of the script from your machine to a new debug script file on the camera.  Please note the only text editor available on these devices is vi.

  • On the camera launch vi with the name of the script
  • <code># vi debug.sh</code>
  • Paste from Notepad++
    • Within vi
    • Press lowercase letter “o” to insert a line below the current line and go into edit mode
    • Press the up arrow key to move to the 1st line
    • Paste the entire contents of the debug.sh file from notepad++ on your machine to vi
    • Note: It will take some time for the paste to complete and it will occasionally pause.
  • Verify Accuracy
    • When the paste has completed verify that the last lines from Notepad++ match those pasted in vi
    • Failure – Last Line Does Not Match
      • Press the “esc” Escape key to exit “insert Mode”
      • Type “:q!” and press enter to force quit without saving any changes ‘
      • Attempt creating the debug script again
    • Success – Last Lines Match
      • Press the “esc” Escape key to exit “insert Mode”
      • Type “:wq” and press enter to open a vi command prompt, write the changes to file and quit vi

Running debug.sh

Before running the first time debug.sh must be made executable using the chmod command.

<code># chmod +x debug.sh</code>

  • Now Launch the script by proceeding the file name with “./”.  If all went well with the creation process debug.sh will run and a menu of choices will be displayed.
  • <code> # ./debug.sh <br>CHOICES:<br>0. print [h]elp<br>1. debug <br>[m]essaging<br>2. debug [r]ecorder<br>3. [R]estart camera or services<br>4. [i]nstall scp on Essentials<br>5. [q]uery iAPI<br>6. print/update [e]nvironment<br>7. [o]pen firmware logs<br>8. run [v]ideo sync<br>9. pretty-print [j]son<br>10. query camera re[b]oots<br>11. query local [d]atabase<br>12. bundle [l]ogs<br>Please select an option: 4<br>#</code>
  • Select option 4 and press enter to install scp on Essentials.
  • When successful no message is returned and debug.sh will terminate.
  • If scp is already installed the message “”scp already exists in path. Cancelling scp install…”” will be displayed and debug.sh will terminate.
  • Installation of scp can be confirmed using the which command.
  • <code># which scp<br>/bin/scp</code>

scp has now been successfully installed and files can be transferred using scp or other tools such as MobaXterm.

Categories
Knowledge Support Cloudvue Cloudvue Cameras Cloudvue Gateway Support Categories

Correcting Error: Cannot find module ‘@jci-Internal/acvs-cloudvue-onvif

Description

Prior  to the release of Cloudvue version 23.9 the error message “”Error:  Cannot find module ‘@jci-Internal/acvs-cloudvue-onvif’” could appear  when trying to add cameras to a Cloudvue Gateway.

This will be fixed with the release of 23.9.x.

Products 

  • Cloudvue Gateway v 22.9.x and older
  • Hikvision
  • Illustra
  • ONVIF

Steps to Reproduce 

Add a new camera either by scanning or by IP.

Expected Results 

Camera adds to the system.

Actual Results 

Camera does not add and displays the error “Error: Cannot find module ‘@jci-Internal/acvs-cloudvue-onvif”.

Solution

  • gain ssh access to the Cloudvue Gateway
  • replace “jci-internal” with “jci-products” in the files /opt/smartvue/services/nvr-cameras/onvif/index.js and /opt/smartvue/services/nvr-cameras/probe.js
  • This can be done by manually editing the files or with the following commands:
  • <code>sed -i ‘s/@jci-internal/@jci-products/g’ /opt/smartvue/services/nvr-cameras/onvif/index.js</code>
  • <code>sed -i ‘s/@jci-internal/@jci-products/g’ /opt/smartvue/services/nvr-cameras/probe.js</code>

Related to AES-711 “CV – Illustra IFS16-M10-BT03 fails to add to GW with error – cannot find module ‘@jci-internal/acvs-cloudvue-onvif'”

Categories
Knowledge Support Cloudvue Cloudvue Cameras Cloudvue Gateway Support Categories Products

Error: Cannot find module ‘@jci-Internal/acvs-cloudvue-onvif

Description

Prior to the release of Cloudvue version 23.9 the error message “”Error: Cannot find module ‘@jci-Internal/acvs-cloudvue-onvif'” could appear when trying to add cameras to a Cloudvue Gateway.

This will be fixed with the release of 23.9.

Products 

  • Cloudvue Gateway v 22.9.x and older
  • Hikvision
  • Illustra
  • ONVIF

Steps to Reproduce 

Add a new camera either by scanning or by IP.

Expected Results 

Camera adds to the system.

Actual Results 

Camera does not add and displays the error “Error: Cannot find module ‘@jci-Internal/acvs-cloudvue-onvif”.

Solution

  • Use Cloudvue Manager to Update the Device
  • If the version is 23.9.x or higher then try to add the camera again
  • Otherwise, contact Cloudvue Support, they will help you in getting a support case started which will be escalated to L3 support who can remotely resolve the issue. 
Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories

Manually Updating Smartvue Software on a Cloudvue Gateway

Description 

At times it may be advantageous to manually apply production versions of Smartvue on a Cloudvue Gateway.  Here are the instructions for obtaining, transferring, deploying, and verifying that software.

Product

  • Cloudvue Gateway

Solution

  • Download the latest smartvue production software version from the support portal HERE
  • Transfer  the file to the Cloudvue Gateway
    • Note: Typically MobaXterm is used to transfer the smartvue software package to a Cloudvue Gateway but rsync can also be used, see KB #18254 for more details.
  • Rename the file to SmartvueCurrent.tar.bz2
  • Extract the tar ball to root using the command sudo tar -xf SmartvueCurrent.tar.bz2 -C /
  • Change directory to /smartvue and run the update script ./update.sh
  • Reboot
  • Verify version

Example

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories Products

Cloudvue Gateway Camera Integrations

Description 

Traditionally Cloudvue has focused on individual API integrations for cameras connecting to the Cloudvue Gateway. However, there are just too many camera manufactures to integrate with each. So, except for Illustra and Axis we rely on integrating with ONVIF Profile-S compliant cameras.

Customers that would like a specific API camera integration should submit their requests online at https://www.cloudvue.io/support-camera-integrations.  The request will be reviewed, and feedback provided.

Categories
Knowledge Support Cloudvue Cloudvue Cameras Cloudvue Gateway Cloudvue Access Control Support Categories Products

Cloudvue Release Process

Description 

The Cloudvue release process involves multiple components and regions.  In addition to the cloud software there are C2C, Cloudvue Manager, Cloudvue Mobile and Cloudvue Access.  Generally, software will release to NA first and if no issues are detected to EMEA and AU a few days later.  This pattern is followed for each component with C2C and Cloudvue Manager released together.   The complete release cycle can take several weeks before all components to be completed.

Cloud

Engineering must  supply a cab file containing all the cloud components such as OS, Database, anything that runs in the cloud to the SRE team for approval.  Once approved it is then implemented by region, replacing all current Cloud components. 

You can view the release summaries outlining what enhancements, fixes and integrations have been made by logging into Cloudvue Manager and going to https://dashboard.cloudvue.com/releases

Cloudvue Gateways

When available software updates can be manually applied to individual Cloudvue Gateways via Cloudvue Manager.  In addition, Engineering can automatically push update to Cloudvue Gateways using the release manager.    https://dashboard.cloudvue.com/releases/manage

C2C

Software updates for C2C devices are like Cloudvue Gateways with the exception that the updates are not automatically pushed.  C2C devices must be manually updated.

Cloudvue Mobile

Software updates for Cloudvue Mobile are made available through the appropriate play store.

Cloudvue Access

Cloudvue Access consists of the mobile application which can be updated through the appropriate play store and the KT-1 controller software and firmware which can manually be updated from the devices page in Cloudvue Manager.

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories Products

Using Rsync to Transfer Files to a Cloudvue Gateway

Description 

At times it may be necessary to move files to a Cloudvue Gateway and while other tools such as SCP or MobaXterm can usually manage the job, rsync can track progress and resume after an interruption which can be particularly useful when transferring large files like the latest Cloudvue software or on slow or unstable connections.

Product

  • Cloudvue Gateway

Solution

The command structure is:

rsync -p -e ‘ssh -p [PORT]’ [PATH/FILENAME] smartvue@[IPADDRESS]:/home/smartvue
  • -P  option will force rsync to show a progress bar and keep partially transferred files. 
  • -e  option allows you to specify a different listening port on the remote host
  • ‘ssh – p [PORT]’  Specifies that ssh be used through a specific port number, use 7627 if local or whatever port was assigned in Cloudvue Manager when setting up the tunnel
  • [PATH/FILENAME]  The local path and  file name to be transferred
  • [IPADDRESS]  The IP address of the Cloudvue Gateway, the LAN IP if local or localhost when tunneling
  • :/home/smartvue  The smartvue home folder on Cloudvue Gateways

Note: When tunneling you must first establish the tunnel. You will then need to open a 2nd instance of WSL or terminal to run the rsync commands.

Examples

In the following examples a file named “22.9.2-smartvue-x64-production.tar.bz2” located in “/home/joakest/tunneling/” is transferred to the gateways smartvue users home folder.

Local Connection 

$ rsync -P -e 'ssh -p 7627' /home/joakest/tunneling/22.9.2-smartvue-x64-production.tar.bz2 smartvue@192.168.1.180:/home/smartvue
smartvue@localhost's password:
22.9.2-smartvue-x64-production.tar.bz2
     200,493,957 100%  390.99MB/s    0:00:00 (xfr#1, to-chk=0/1)
  • When prompted enter the SSH password found in Cloudvue Manager.
  • The progress of the file transfer will display, and the prompt will return when completed.

Tunnel Connection 

$ rsync -P -e 'ssh -p 8346' 22.9.2-smartvue-x64-production.tar.bz2 smartvue@localhost:/home/smartvue
The authenticity of host '[localhost]:8346 ([127.0.0.1]:8346)' can't be established.
ED25519 key fingerprint is SHA256:nw6P03KIwsjiKfy2fkJJjRUSi4dJA6gwLyd7/+0Fz0Y.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes

Warning: Permanently added '[localhost]:8346' (ED25519) to the list of known hosts.

smartvue@localhost's password:
22.9.2-smartvue-x64-production.tar.bz2
    200,493,957 100%  249.79kB/s    0:13:03 (xfr#1, to-chk=0/1)
  • Since this is the first time a ssh connection has been established to this NVR from the local machine the authenticity warning will appear.
  • Continue by typing in “yes” and pressing enter.

Categories
Cloudvue Knowledge Support Cloudvue Gateway Support Products

Cloudvue Video File Formats

Description 

Both Cloudvue Gateways and C2C devices store video in 30 second increments.  Cloudvue Gateways use MP4 and C2C uses MKV container formwats.  The MKV video files on C2C devices are encrypted and cannot simply be copied and played.   The MP4 video files on Cloudvue Gateways are NOT encrypted and can be copied and played.

Product

  • C2C
  • Cloudvue Gateway

Reference

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Products

Amcrest Cameras Fail to Add as ONVIF

Description 

Adding an Amcrest camera as ONVIF to a Cloudvue Gateway fails with an error message “Invalid Username / Password”. This is true even if the credentials being used work to login to the cameras web interface.

Product

  • Cloudvue Gateway
  • Cloudvue Software v22.9.2

Steps to Reproduce 

  • From the Devices tab in Cloudvue Local (Settings > Devices)
  • Scan For devices , select and add an Amcrest Camera
  • When prompted enter username, password and add as ONVIF

Expected Results 

  • Camera adds

Actual Results

  • Camera fails to add with an error message “Camera Save Failed … Invalid Username / Password”

Solution

  • Create a user in the camera called “onvif” and use those credentials when adding the camera in Cloudvue Local.

Reference: https://amcrest.com/forum/ip-cameras-f18/onvif-authentication-not-working-in-newer-cameras-t13723.html

Re: ONVIF authentication not working in newer cameras

Post by ckchessmaster » Wed Jan 18, 2023 12:58 pm