Skip to content

Offline SC4SNMP installation

Local machine with internet access

To install the SC4SNMP offline, first, some packages must be downloaded from the Github release and then moved to the SC4SNMP installation server. Those packages are:

  • dependencies-images.tar
  • splunk-connect-for-snmp-chart.tar

Additionally, you’ll need

  • pull_mibserver.sh script

to easily pull and export mibserver image.

Moreover, SC4SNMP Docker image must be pulled, saved as a .tar package, and then moved to the server as well. This process requires Docker to be installed locally.

Images can be pulled from the following repository: ghcr.io/splunk/splunk-connect-for-snmp/container:<tag>. The latest tag can be found here under the Releases section with the label latest.

Example of docker pull command:

docker pull ghcr.io/splunk/splunk-connect-for-snmp/container:<tag>

Then save the image. Directory where this image will be saved can be specified after the > sign:

docker save ghcr.io/splunk/splunk-connect-for-snmp/container:<tag> > snmp_image.tar

Another package you have to pull is the mibserver image. You can do it by executing pull_mibserver.sh script from the Release section, or copy-pasting its content.

chmod a+x pull_mibserver.sh # you'll probably need to make file executable
./pull_mibserver.sh

This script should produce mibserver.tar with the image of the mibserver inside.

All four packages, mibserver.tar, snmp_image.tar, dependencies-images.tar, and splunk-connect-for-snmp-chart.tar, must be moved to the SC4SNMP installation server.

Installation on the server

On the server, all the images must be imported to the microk8s cluster. This can be done with the following command:

microk8s ctr image import <name_of_tar_image>

In case of this installation the following commands must be run:

microk8s ctr image import dependencies-images.tar
microk8s ctr image import snmp_image.tar
microk8s ctr image import mibserver.tar

Then create values.yaml. It’s a little different from values.yaml used in an online installation. The difference between the two files is the following, which is used for automatic image pulling:

image:
  pullPolicy: "Never"

Example values.yaml file can be found here.

The next step is to unpack the chart package splunk-connect-for-snmp-chart.tar. It will result in creating the splunk-connect-for-snmp directory:

tar -xvf splunk-connect-for-snmp-chart.tar --exclude='._*'

Finally, run the helm install command in the directory where both the values.yaml and splunk-connect-for-snmp directories are located:

microk8s helm3 install snmp -f values.yaml splunk-connect-for-snmp --namespace=sc4snmp --create-namespace