|
| 1 | +... Getting Started |
| 2 | + |
| 3 | +Getting Started |
| 4 | +=================================================== |
| 5 | + |
| 6 | +Requirements (Splunk Enterprise/Enterprise Cloud) |
| 7 | +--------------------------------------------------- |
| 8 | + |
| 9 | +1. Splunk index for events "netops" |
| 10 | +2. Splunk index for metrics "net_metrics" |
| 11 | +3. Splunk hec token with no index restriction *OR* Splunk hec token with access to _internal, netops and net_metrics |
| 12 | +4. Known Splunk URL with trusted certificate (must be trusted by standard red hat trusted chain) |
| 13 | +5. Physical or virtual linux host (Prefer Ubuntu or RHEL 8.1) RHEL hosts must have snap support enabled see https://snapcraft.io/docs/installing-snapd |
| 14 | +6. One IP allocation in addition to the ip allocated to the host. *Note: In the future clustering (scale out) will use this IP as a shared resource |
| 15 | +
|
| 16 | +Setup Micro K8s |
| 17 | +--------------------------------------------------- |
| 18 | + |
| 19 | +The following setup instructions are validated for release 1.20x but are subject to change. |
| 20 | + |
| 21 | +1. Install MicroK8s ``sudo snap install microk8s --classic`` |
| 22 | +2. Check completion status ``sudo microk8s status --wait-ready`` |
| 23 | +3. Install optional modules ``sudo microk8s enable dashboard dns registry metallb`` |
| 24 | +4. Alias kubectl ``alias kubectl="microk8s kubectl"`` |
| 25 | + |
| 26 | +Setup Secrets |
| 27 | +--------------------------------------------------- |
| 28 | + |
| 29 | +Execute the following commands, use the correct values for your env: |
| 30 | + |
| 31 | +* Setup URL and token secret |
| 32 | + |
| 33 | +.. code-block:: bash |
| 34 | +
|
| 35 | + kubectl create secret generic remote-splunk \ |
| 36 | + --from-literal=SPLUNK_HEC_URL=https://fqdn:8088/services/collector \ |
| 37 | + --from-literal=SPLUNK_HEC_TLS_VERIFY=yes \ |
| 38 | + --from-literal=SPLUNK_HEC_TOKEN=sometoken |
| 39 | + |
| 40 | +
|
| 41 | +* Get the manifests |
| 42 | + |
| 43 | +.. code-block:: bash |
| 44 | +
|
| 45 | + git clone https://github.com/splunk/splunk-connect-for-snmp.git |
| 46 | +
|
| 47 | +* Apply the manifests, replace the ip ``10.0.101.22`` with the shared IP noted above |
| 48 | + |
| 49 | +.. code-block:: bash |
| 50 | +
|
| 51 | + cat splunk-connect-for-snmp/deploy/k8s/*.yaml | sed 's/loadBalancerIP: replace-me/loadBalancerIP: 10.0.101.22/' | kubectl apply -f - |
| 52 | +
|
| 53 | +* Confirm deployment using ``kubectl get pods`` two(2) instances of mib-server and one (1) instance of traps example |
| 54 | + |
| 55 | +.. code-block:: bash |
| 56 | +
|
| 57 | + NAME READY STATUS RESTARTS AGE |
| 58 | + mib-server-54557f5846-rzg9q 1/1 Running 0 1m |
| 59 | + mib-server-54557f5846-pbt2h 1/1 Running 0 1m |
| 60 | + traps-676859cb8d-tnc7v 1/1 Running 0 1m |
| 61 | +
|
| 62 | +* Test the trap from a linux system with snmp installed replace the ip ``10.0.101.22`` with the shared ip above |
| 63 | + |
| 64 | +.. code-block:: bash |
| 65 | +
|
| 66 | + snmptrap -v2c -c public 10.0.101.22 123 1.3.6.1.6.3.1.1.5.1 1.3.6.1.2.1.1.5.0 s test |
0 commit comments