Solarwind ftp

This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references. You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum. Hello All,We have F5 Devices in NCM for backup. It has stopped taking backup saying error "Connectivity issues". Backup is successful only for two F5 devices out of 12 which are standby. We have checked, Device configuration, all settings & F5 Template is same for all working and non-working devices.Checked with Solarwind and F5 OEM, but received nothing specific which will address the issue.Anyone can suggest, what could be the issue.Thanks in advance...!!! It sounds like it used to work and now doesn't. So you need to check what has changed. Check firewalls, permissions etc. Did you manage to get this to work? Which version of NCM are you running? Yes, it was working previously and nothing has been changed from Device as well from Solarwind end. No, its still not working. We are using NCM 7.8. Today, received revert from support team ", it seems related to the encryption that NCM is using. They need match inoder for NCM to be able to access the device." I am also having this issue. I am running into the same thing. We are also running 7.8. It had been working up until recently. We are also running F5 version 14.0.0.3 build 0.0.4 We are now able to take backup for F5. TAC support given one DLL file to replace with existing one. After changing it, backup is successful.

Switch is valid and does exist in flash. And you have showed us that there is IP connectivity between the switch and 192.168.0.13. My first question would be whether you are sure that the TFTP service was running on 192.168.0.13 at the time that you try the tftp?My second question is whether 192.168.0.13 is a locally connected device or whether it is a remotely connected device? If it is remote connected is there any chance that there is a security policy which does allow ping but does not allow tftp?My third question would be whether there might be any firewall or other security policy on 192.168.0.13 that is preventing tftp?HTHRick Richard,Thank you for the reply!Yes, the tftp server was ruuning on 192.168.0.13.Locally connected device is my PC.I look at firewall setting on PC, and this is okay. Also, I checked setting on a router/modem/wireless router with tftp accepted or better allowed.I tired another tftp server on another PC. I able to ping the switch from the computer and from the switch to the PC not able to ping the adapter to that PC which the tftp server in bound too.Very good step that you gave me, but I have to fixed yet.regards,Deverick Lets Summarize:- PC(TFTP service running(services-tftp-running))----------f0/1---Switch192.168.0.13 -----------------------------------------------------------------192.168.0.xLaptop --- Switch ==> Ping successSwitch ----Laptop ==> Ping success >>>>> this gives us info that our layer 1 is good.2-Now move on nextL-Laptop :- Disabled the Anti-virus ==> DoneIf you are using Solarwind check the tftp server binding x.x.x.x/32 as the mask==>

Integration version: 4.0Use CasesPerform active actions - execute SQL queries to get more information about theendpoint.Configure SolarWinds Orion integration in Google Security Operations SOARFor detailed instructions on how to configure an integration inGoogle Security Operations SOAR, see Configureintegrations.Integration parametersUse the following parameters to configure the integration:Parameter Display NameTypeDefault ValueIs MandatoryDescriptionInstance NameStringN/ANoName of the Instance you intend to configure integration for.DescriptionStringN/ANoDescription of the Instance.IP AddressStringx.x.x.x:17778YesIP address of the SolarWinds Orion instance.UsernameStringN/AYesUsername of the SolarWinds Orion account.PasswordPasswordN/AYesPassword of the SolarWinds Orion account.Verify SSLCheckboxUncheckedNoIf enabled, verify the SSL certificate for the connection to the SolarWinds Orion server is valid.Run RemotelyCheckboxUncheckedNoCheck the field in order to run the configured integration remotely. Once checked, the option appears to select the remote user (agent).ActionsPingDescription‌Test connectivity to the SolarWinds Orion with parameters provided at theintegration configuration page in the Google Security Operations Marketplace tab.Run OnThis action doesn't run on entities, nor has mandatory input parameters.Action ResultsScript ResultScript Result NameValue OptionsExampleis_successTrue/Falseis_succeed:FalseCase WallResult TypeValue / DescriptionTypeOutput message*The action should not fail nor stop a playbook execution:If successful:Print "Successfully connected to the SolarWinds Orion server with the provided connection parameters!"The action should fail and stop a playbook execution:If not successful:Print "Failed to connect to the SolarWinds Orion server! Error is {0}".format(exception.stacktrace)GeneralExecute QueryDescription‌Execute query in SolarWinds Orion.ParametersParameter Display NameTypeDefault ValueIs MandatoryDescriptionQueryStringN/AYesSpecify the query that needs to be executed. Note: SolarWind queries don't support "*" notation.Max Results To ReturnInteger100NoSpecify how many results should be returned.Run OnThis action doesn't run on entities, nor has mandatory input parameters.‌Action ResultsScript ResultScript Result NameValue OptionsExampleis_succeedTrue/Falseis_succeed:FalseJSON Result{ "results": [ { "DisplayName": "orion" } ]}Case WallResult TypeValue / DescriptionTypeOutput message*The action should not fail nor stop a playbook execution:If not status code 400 (is_success = true):Print "Successfully executed query and retrieved results from SolarWinds Orion".If status code 400 (is_success = false):Print "Action wasn't able to successfully execute query and retrieve results from SolarWinds Orion. Reason: {0}".format(message)The action should fail and stop a playbook execution:If fatal error, like wrong credentials, no connection to server, other: Print "Error executing action "Execute Query". Reason: {0}''.format(error.Stacktrace)GeneralCase Wall TableTable Name: "Results"All of the columns from the response will be used as table columns.GeneralExecute

Entity QueryDescriptionExecute query in SolarWinds Orion based on the IP and Hostname entities.How to work with action parametersThis action gives an ability to easily retrieve information about the endpointsbased on the IP and Hostname entities.Imagine a situation where you want to retrieve the uptime of the endpoints.First endpoint has IP '172.30.230.130' and the second endpoint has hostname'DC001'. In this case our query would need to look like this:SELECT IpAddress, DisplayName, SystemUpTime FROM Orion.Nodes WHEREIpAddress='172.30.203.130' OR DisplayName='DC001'In order to create the same query using "Execute Entity Query" action, you needto fill out the action parameters in the following way:QuerySELECT IpAddress, DisplayName, SystemUpTime FROM Orion.NodesIP Entity KeyIpAddressHostname Entity KeyDisplayNameWHERE clause will be prepared automatically.Table Schema Documentation Display NameTypeDefault ValueIs MandatoryDescriptionQueryStringN/AYesSpecify the query that needs to be executed. Note: SolarWind queries don't support "*" notation and you shouldn't have a WHERE clause in the query, because it is added by the action. Please refer to the action documentation for details.IP Entity KeyStringIpAddressNoSpecify what key should be used with IP entities in the WHERE clause of the query. Please refer to the action documentation for details. Default:IpAddressHostname Entity KeyStringHostnameNoSpecify what key should be used with Hostname entities in the WHERE clause of the query. Please refer to the action documentation for details. Default:HostnameMax Results To ReturnInteger100NoSpecify how many results should be returned.Run OnThis action runs on the following entities:IP AddressHostAction ResultsScript ResultScript Result NameValue OptionsExampleis_successTrue/Falseis_success:FalseJSON Result{ "results": [ { "DisplayName": "orion" } ]}Case WallResult TypeValue / DescriptionTypeOutput message*The action should not fail nor stop a playbook execution:If not status code 400 (is_success = true):Print "Successfully executed query and retrieved results from SolarWinds Orion".If status code 400 (is_success = false):Print "Action wasn't able to successfully execute query and retrieve results from SolarWinds Orion. Reason: {0}".format(message)If no entities in the scope (is_success = false)Print "No entities were found in the scope." The action should fail and stop a playbook execution:If fatal error, like wrong credentials, no connection to server, other: Print "Error executing action "Execute Entity Query". Reason: {0}''.format(error.Stacktrace)GeneralCase Wall TableTable Name: "Results"All of the columns from the response will be used as table columns.GeneralEnrich EndpointDescriptionFetch