Troubleshooting Trellix DSB cluster issues

Recover a Trellix DSB VM

To recover a Trellix DSB VM, create a Trellix DSB device VM.

Log on into Trellix DSB device VM and follow the steps:
1. Deactivate FIPS Mode.
```
# SetFipsMode no
```
2. Configure IP address. You can get IP address from Node Settings → Network Interface.
```
# vi /etc/NitroGuard/network.conf
```
3. Restart network service.
```
# service network restart 
```
4. Verify if network configuration is OK.
```
# ifconfig
```
  Note
  If IP address is configured different, you get a message EC360 Error: SSH Connection failed and If it is configured correctly you get a message EC122 Error: Could not execute command on device.
Open Data Streaming Bus Configuration page.
Right-click DSB node and select Settings.
The Node Settings page opens.
Click Key Device under Key Management.
The keying process starts. A copy of keys and certificates on the DSB device is created.
The process triggers cluster configuration, start databus services, topics creation, EFS configuration and restart all services.

Verify if all topics are created and process are running on DSB Device.

Verify topics

# export KAFKA_HEAP_OPTS="-Dzookeeper.serverCnxnFactory=org.apache.zookeeper.server.NettyServerCnxnFactory \
-Dzookeeper.clientCnxnSocket=org.apache.zookeeper.ClientCnxnSocketNetty \
-Dzookeeper.ssl.keyStore.location=/etc/NitroGuard/pki/databus/kafka.keystore \
-Dzookeeper.ssl.keyStore.password=NGCP_Q@Change1t \
-Dzookeeper.ssl.trustStore.location=/etc/NitroGuard/pki/databus/kafka.truststore \
-Dzookeeper.ssl.trustStore.type=PKCS12 \
-Dzookeeper.ssl.keyStore.type=PKCS12 \
-Dzookeeper.ssl.trustStore.password=NGCP_Q@Change1t \
-Dzookeeper.client.secure=true \
-Djava.security.properties=/usr/java/crypto-j/crypto-j.security.fips"
# /opt/kafka/bin/kafka-topics.sh --zookeeper localhost:2181 --list

Verify process running

# ps auxf | grep ctl   OR  # NitroStarted

Use the DSB Node and Cluster shown in green.
(Optional) If DSB Cluster remains in yellow or red, perform steps 6–8.
Note
Red indicates critical status and yellow indicates that the DSB cluster or node is being created.