thangaselvi ✭✭✭✭✭

For BGP the variable ${N=SwisEntity;M=Node.Caption} is not available , so i need to use ${N=SwisEntity;M=Router.Caption} or ${N=SwisEntity;M=Router.Nodes.Caption} . Now in Same SNOW action in the CI field i can pass two variables ? I tested but not working .. Else for BGP again i need to create new action with its variable…

Hi @vinay.by @naveensingh43 , I have added the variable ${N=SwisEntity;M=Node.Caption} in alert and passed this variable in CI field in SNOW action and it fixed the missing CI for Interface alerts checking for BGP alert.

Hi @vinay.by , Its direct integration with ServiceNow. Right now i have only one action for SNOW where i am passing ${N=SwisEntity;M=Caption} for CI field for node based alert it is working . For interface and BGP it is not . Can we add multiple variables or for interface i need to creation new action with variable…

Thanks @naveensingh43 , yes i have created groups but dont find the option to select the group in OOB reports

Yes looks like there is limitation which is really timing consuming to update the speed

Thanks All , yes i found an way and testing got the below error 226] WARN SolarWinds.Orion.Core.Common.MacroParsing.SwisEntityMacroParserPlugin - (null) The following variables are not available in Swis Entity macro parser plugin - CustomProperties.SNOW

Thanks , but how the email with be sent to customer A based on there device with help of custom property value .. i dont see anywhere the variable to be added.

https://thwack.solarwinds.com/discussion/152927/auto-alignment-of-ncm-device-template-should-work-for-api-based-discovery

Hi @mr.castaneda, Thanks for confirming .. Right now doing it manually. But concerned on new devices every time someone needs assign it.

Yes Vinay it supprts only API + ICMP and if i assign manually it works .. But concern for new devices every time some one need to add this

The custom properly is applied to Node only .or i need to update to interface as well.Will it work ?

This idea is from 2015 .. Is there is any plan from Product team on this ?

Yes , This is working using SNMP+API for meraki

Created an idea to do these centrally like how hardware sensors are managed

Thanks can we do a auto clear of alerts when the BGP is established again in trap method ?

Yes , looks like the device is not supporting i have disabled it manfully .. But expecting some automatic process

I am using 2026.2.2 version

Yes i agree but the unsupported ones are discovered by SolarWinds ? Any idea

Did you managed to setup these alerts ?

Any updates further on this ?

Hi @naveensingh43 , Thanks , I have fixed the issue last week missed to update here . The issue was when we try to discover from the root meraki device the WAP are added in the discovery window with hostname and Ip address where the discovery failed and some was stuck in between

That is much needed one which is missing … Does any one have that script ? i hope re-discover process does not revert it ?

Thanks i will go with UTC

Thanks

Hi Team, Can someone update on best practices on below. "We are planning to monitor Silver peak and Meraki in SolarWinds , If we discover the nodes via api and SNMP as well will the nodes will be consolidated as single node ? There are any best practices for adding in both ways"

I am not sure on exact parameters ,but there will be many group policy which will be enforced as per organization standards

Even in the DB servers we can do right ?

Hi @B.Rathinavel , We are planning to monitor Silver peak and Meraki in SolarWinds , If we discover the nodes via api and SNMP as well will the nodes will be consolidated as single node ? There are any best practices for adding in both ways?

Hi @vinay.by , Yes its new location . Thanks for your inputs.

Can you share some documents on building the SQL DB ?