ContributionsMost RecentMost LikesSolutionsRe: Handling Self-Signed Certificates for PowerVault Devices Can you please confirm? Re: Handling Self-Signed Certificates for PowerVault Devices I checked the device, and it displays the message: "Device uses an invalid security certificate. The certificate is not trusted because it is self-signed." This indicates that the self-signed certificate is the reason the browser—and likely LogicMonitor—is not trusting the connection. Is there a way to configure the Collector to trust this certificate? We plan to configure the LogicMonitor Collector to trust this host by adding the following JVM options to the wrapper.conf file: wrapper.java.additional.<n>=-Dtrust.unsecure.ssl=true wrapper.java.additional.<n+1>=-Dtrust.unsecure.ssl.hosts="Device IP" <n> means "properties, incrementing" 1) I don't know. Is this the correct and recommended way to handle this specific error for a single host in LogicMonitor? 2) Are there any potential downsides or security considerations we should be aware of when using these JVM options? 3) After making this change and restarting the Collector, should LogicMonitor's webpage check (or other relevant monitors) now be able to connect successfully to the Device on port 443? Handling Self-Signed Certificates for PowerVault Devices We are experiencing issues connecting to the PowerVault devices on port 443, likely due to the use of self-signed certificates. Is there a way to configure the specific collector to trust the target host? The DS HTTPS 443 port has been showing status code 5 (Network Error) since September 29th 2024, and from that date, we have stopped receiving data for the PowerVault DS, which is now returning "No Data." Could you please recommend an approach for handling self-signed certificates to trust the host? Re: Monitoring Gateway SIP Trunk Status via SSH through Command line After of changing this i am getting IO Exceptional Java Error Re: Monitoring Gateway SIP Trunk Status via SSH through Command line I tried this, I am getting an error " Connection Refused Connect" Re: Monitoring Gateway SIP Trunk Status via SSH through Command line Mike Moniz, Can you suggest how to achieve this? Re: Monitoring Gateway SIP Trunk Status via SSH through Command line I have attached the snapshot for reference , please let me know any other info Re: Monitoring Gateway SIP Trunk Status via SSH through Command line Model - ISR4431/K9 Router firmware_version 17.6.1 hardware_version V07 Vendor - Cisco Monitoring Gateway SIP Trunk Status via SSH through Command line Hi, I am trying to monitor the status of the Gateway SIP trunk using the command "show sip-ua register status" via SSH. However, I am encountering issues while running a custom script provide by the support team. Initially, when I ran the script a few times, I received an error: "Unable to establish the SSH Connection". After some time, the error changed to "No Signature Method." I have verified the SSH connection from the collector server to the end device, and it works fine when I manually establish the SSH session. I also tested my own script , but it returned a similar error: "Error: Unable to establish SSH session/channel." I have attached the error snapshot and the script I am using for reference. Please guide me on how to monitor the SIP status via the command line using SSH. When running the command "show sip-ua register status", the output is either Yes (registered) or No (unregistered) from the device end. In LogicMonitor, the expected output should be: Yes = 0 No = 1 I tried to attach the Script but it will not support Txt Format, Sorry for the inconvenience Below is the script Provided by the support team import com.santaba.agent.groovyapi.expect.Expect; // Get the hostname and credentials from the device property table hostname = hostProps.get("system.hostname"); userid = hostProps.get("ssh.user"); passwd = hostProps.get("ssh.pass"); // Ensure required properties are not null if (!hostname || !userid || !passwd) { throw new Exception("Missing required device properties: hostname, ssh.user, or ssh.pass."); } // Initiate an SSH connection to the host using the provided credentials def ssh_connection = Expect.open(hostname, userid, passwd); // Wait for the CLI prompt to confirm connection ssh_connection.expect("# "); // Adjust prompt based on your device // Send the `show sip-ua register status` command ssh_connection.send("show sip-ua register status\n"); // Wait for the response to complete ssh_connection.expect("#"); // Replace with your device's prompt // Print the output of the command println "Command Output: " + ssh_connection.getLastOutput(); // Logout ssh_connection.send("exit\n"); // Close the SSH connection handle ssh_connection.expectClose(); return 0; This is another script Created by Me import com.santaba.agent.groovyapi.expect.Expect // Device credentials and details def deviceIP = hostProps.get("system.ip") // IP address of the device def username = hostProps.get("ssh.user") // SSH username from LogicMonitor def password = hostProps.get("ssh.pass") // SSH password from LogicMonitor // Command to execute def command = "show sip-ua register status" // Initialize result def resultCode = 1 // Default to 1 (Unregistered) // Start SSH session try { def session = Expect.open(deviceIP, username, password) // Send the command session.send(command + "\n") // Wait for the output def output = session.expect(10, ".*") // Adjust timeout (10 seconds) as needed println("Command output: ${output}") // Check the output for 'Yes' or 'No' if (output.toLowerCase().contains("yes")) { resultCode = 0 // Registered } else if (output.toLowerCase().contains("no")) { resultCode = 1 // Unregistered } else { throw new Exception("Unexpected output: ${output}") } // Close the session session.close() } catch (Exception e) { println("Error: ${e.message}") // Optionally log additional details for debugging } // Print the result for LogicMonitor println(resultCode) return resultCode Re: Email Ingestion Hey Stuart, The JSON Format isn't the problem. We've identified the cause of the error. Earlier today, we updated the email password and successfully tested the script, yielding the expected output. However, the password is inexplicably becoming locked within moments. I'm uncertain as to why this is occurring, but it's resulting in a JSON error. If you have any insights into why the password might be getting locked, I'd appreciate your input.
Top ContributionsMeraki MonitoringMonitoring Gateway SIP Trunk Status via SSH through Command lineMonitoring DAS Environment and Creating Custom Data Sources in Logic MonitorEmail IngestionCore Dump File MonitoringRe: Monitoring Gateway SIP Trunk Status via SSH through Command lineRe: Monitoring Gateway SIP Trunk Status via SSH through Command lineRe: Monitoring Gateway SIP Trunk Status via SSH through Command lineRe: Monitoring Gateway SIP Trunk Status via SSH through Command lineRe: Meraki Monitoring