Community

need to get api nodes url

we are using below NQE Query to get the NTP Server details , i need to remove some static value in  server coloum, ciscontppattern=``` ntp server {server:string}```;getServers(device) =  foreach match in blockMatches(device.files.config, ciscontppattern)   select { serverIP: match.data.server}; foreach device in network.deviceslet platform = device.platformwhere device.platform.vendor == Vendor.CISCO  select {  device: device.name,   vendor: device.platform.vendor,    tags: device.tagNames,    os: device.platform.os,    OSVersion :platform.osVersion,  servers: (foreach server in getServers(device)            select server.serverIP)}  Example : i dont want to show entry those have server value - “Inte”

Hi allHas anyone onboarded Arista WIFI yet, the models we have are managed centrally via CV-CUE the Wifi version of cloudvision, although you can extract some commands via SSH.Had a quick look around and couldn’t find anything, I will in the meantime dig around about custom devices 😀Thanks

This NQE will validate that only the SSID’s in allowedSSID’s can be used, if it does not exists in the list it will fail the query.Taking advice from an earlier post I have used blockMatches this time, there is some tuning required to remove the duplicates as a result of the table have the entry for each /** * @intent Validate that the arista AP's have only the approved SSID's configured * @description This will check each arista AP for the approved SSIDs and violate when ther SSID does not match * the allowedSSID list. * * You will get multiple entries due to the VAPS list having an entry for each frequency. This will be a future * fix to show only once when the unauthoirised SSID exists */pattern = ```VAP-ID : {VAPId:string} ESSID : {SSID:string}```;// Replace the SSID's with your own.allowedSSID = ["ssid1","ssid2","ssid3"];foreach endpoint in network.endpointswhere endpoint.profileName == "Arista Wireless AP's"foreach command in endpoint.cliCommandRespons

Following on from  I thought I would share this NQE if others are using Arista AP’s and want to maintain version numbers across their estate. /** * @intent List all Arista AP's and there software version. * @description List all Arista AP End Points and there software version. */allowedVersion = "18.0.0";foreach endpoint in network.endpointswhere endpoint.profileName == "Arista Wireless AP's"foreach command in endpoint.cliCommandResponseswhere command.command == "show device info"let ParsedResponse = parseConfigBlocks(OS.UNKNOWN,command.response)foreach line in ParsedResponselet modelNo = patternMatch(line.text,`Device Model : {string}`)foreach line in ParsedResponselet software = patternMatch(line.text, `Device Version : {string}`)foreach line in ParsedResponselet serialNo = patternMatch(line.text,`Serial Number : {string}`)where isPresent(modelNo)where isPresent(software)where isPresent(serialNo)select { violation: software != allowedVersion, name: endpoint.name, location

I have put together a query to enhance inventory by adding LDoS dates and ‘approved software’. It has greatly improved our Life Cycle Mgmt. conversations.  The CSV Files reside separately in a ‘standards’ folder. (there are just too many fields to keep in the same script).The resulting output provides:Vendor | Hostname | Model | Location | Vendor LDoS Date | HW Compliance Date | Current OS | Approved OS | Compliance to OS | Replacement Mode | And more /** * @intent Inventory of all devices in FN * @description Take inventory and then cross check them against the CSV Files for SW/HW info**/ import "Home/Network Standards/01_NetworkVars/99_Support_Detailed";foreach device in network.deviceslet platform = device.platformlet snapshotInfo = device.snapshotInfoforeach entry in deviceSupportDetailwhere entry.Model == platform.modellet LDOS = entry.HW_LDoSlet STATUS = entry.LCMlet comma = ", "let ApprovedSW = entry.SW_N + comma + entry.SW_N1 + comma + entry.SW_N2let Replacement = entry.HW_Repl

Hello NQE Enthusiasts, I’ll try to post a new Koan Challenge every two months.  ChallengeThis task is to take the following table and group people by age. Input [{ Name: "Bob", Age: 21 },  { Name: "Sam", Age: 19 },  { Name: "Jill", Age: 18 },  { Name: "Jim", Age: 21 },  { Name: "Sally", Age: 19 } ]; Example Result[{Age: 21, Count: 2}...] Hinthttps://fwd.app/docs/nqe/guides/comprehensions/#group-by-qualifier Contributions: Unclaimed

It is possible to compare the output of an NQE query using the Diffs feature by first adding the NQE query to Inventory+.Consider the following NQE query, which lists all the static routes on all devices. (Note that the next hop is listed in this example provided that the next hop is an IP address. The query could be expanded to handle other types of next hops). getStaticRoutes(routingTable) = foreach ipEntry in routingTable.ipEntries foreach nextHop in ipEntry.nextHops where nextHop.originProtocol == OriginProtocol.STATIC select { prefix: ipEntry.prefix, nextHopType: nextHop.nextHopType, nextHop: ipEntry.nextHops };foreach device in network.devicesforeach networkInstance in device.networkInstanceslet afts = networkInstance.aftswhere isPresent(afts.ipv4Unicast)let ipv4Unicast = afts.ipv4Unicastlet staticRouteCount = length(getStaticRoutes(ipv4Unicast))where staticRouteCount > 0foreach entry in getStaticRoutes(ipv4Unicast)select { Device: device.name, "Network Instanc

I provided a query for doing this some time ago.  However, it was written for running where the Data Model did not have as many BGP elements as the current Data Model.  Now that there are more BGP elements in the data model it makes this query much simpler.  Which also means it runs faster.The inspiration for this query was a customer that run BGP between pretty much all devices. This is why it is only based on BGP peers./** * @intent Input the device under maintenance. get the list of BGP peers and outbound interfaces * @description This is a Parameterized Query. You input the devicename string. * it will look for the BGP peers of that devices, plus determine the interfaces that connect the * devices together. This way you can mute the alarms for the BGP peers and links before a maintenance window. */import "@fwd/L3/Interface Utilities"; //getL3Interfaces(device: Device)getPeerInfo(neighbor, sourceRouterId) = max(foreach device in network.devices where device.name == neighbor.

When working with STIG compliance checks, a common challenge is that many checks only verify the existence of a control—not whether the configured values align with site-specific requirements. This can be a problem when compliance policies vary across different data centers and locations.With a little work, it is easy to customize the queries. Benefits are apparent. You get: more precision to verify your specific ACL and group names Verifying differing configuration policies across multiple data centers or locations Improved compliance and governance across a variety of configurations and regionsThere are two approaches you can use to customize queries.Copy the query and modify the block match to include the value of your parameter Parametrize the query and use your location-specific string value as a query parameter. Parameterized queries are slightly more complex but make existing STIG checks - and other NQEs - more flexible.Let’s use an example of a library STIG query /Forward Libra

we are using 4 different query to get some information in FWD , is their any way to merge these queries into one and get the output in single file.Query 1 for NTP Fortinet :-  pattern_fmg = ```config system ntp    config ntpserver        edit 1            set server {ntp1:string}```;pattern_servers =  ```config system ntp    config ntpserver        edit 2            set server {ntp2:string}       ```;pattern_servers2 =  ```config system ntp    config ntpserver        edit 3            set server {ntp3:string}```;// Loop through list of devices finding those that are Fortinet// and store outputs of commands in the 'outputs' variable// Loop through list of devices finding those that are Fortinetforeach device in network.devices/* where device.platform.vendor == Vendor.FORTINET */let outputs = device.outputs// Loop through the commands in the outputs var, looking for custom// commands that are from 'show system ntp' and store in a variable called central_mgmtforeach command in outputs.com

Team ,we are using belong NQE to get the information about Fortinet Firewall SNMP config and server white list information , however NQE provide the result , but devices are repeating ,ex, 1 devices we can see approx. 44 entry , can you please have a look on this and help us to fix .  NQE Query   // Patterns to match pattern_community= ```config system snmp community    edit {string}        set name {community:string}        config hosts            edit {string}                set ip {ip:string} {netmask:string}            next ```;  foreach device in network.deviceslet outputs = device.outputs foreach command in outputs.commandswhere command.commandType == CommandType.CUSTOMwhere command.commandText == "show system snmp community"let central_mgmt = parseConfigBlocks(OS.FORTINET, command.response) // Search for the ""pattern_fmg" pattern looking for a matchforeach match in blockMatches(central_mgmt, pattern_community)//loop through the all server-address IP's and store them in variable

Continuing scripts to pull more information from Cisco WLC’s. Find my original Cisco WAP post here: Pre-requisites:Add Custom Command to IOS-XE for collection “show ap image | inc None” Add Tag of “WLC” on your Wireless Controllers WLC’s are on c9800 running IOS-XE IOS-XE version is 17.x.x/*** @intent - pull Name & OS Versions from Cisco AP's via Cisco WLC's* @description Log into Cisco WLC's "C9800" and pull AP information from the controllers with "show ap image | inc None"**/// Pattern of output//AP_INFO = ```{APName:string} {PrimaryOS:string} {BackupOS:string}```;foreach device in network.deviceslet platform = device.platformforeach Tag in device.tagNameswhere Tag == "WLC"foreach Command in device.outputs.commandswhere Command.commandText == "show ap image | inc None"let parsed = parseConfigBlocks(OS.IOS_XE, Command.response) //parses text into lineslet matchData = blockMatches(parsed, AP_INFO) //applies pattern to linesforeach x in matchDataselect { name: device.name, Loca

We continue to rely almost exclusively on Forward Networks for our lifecycle management and planning (purchasing).  One of the big gaps, however, was I couldn’t get the Wireless Access Points on the network, and had to go to other devices and export it into excel. Not terrible, but time consuming. You can also check out my related post: I threw together simple script to collect the Cisco AP’s “Name/Location/AP-Model/IP-Address/Country-Code. ​@AhmedKhedr Pre-requisites: Add Custom Command to IOS-XE for collection “show ap sum” Add Tag of “WLC” on your Wireless Controllers WLC’s are on c9800 running IOS-XE IOS-XE version is 17.9.6It appears older versions of OS (<17.9.6) don’t align nicely, but i’m sure you can adjust for it using the core of this script. I’m adding one more table to this, to pull the LDoS date from the model that is pulled from the custom command… which I will update when I get it to work ;-)/*** @intent - pull Name & Model & IP address* @description Log into

how can i convert OS EOL query into basis of vendor and version ? as of now in OS Support query showing output via device wise , i want to see this in to vendor os wise.

Hello NQE Enthusiasts, Here is another Koan challenge. The task is to take a list of years and calculate the centuriesInput:[1776, 2001, 1643, 1969];Result[{“Year”: 1776, “Century”: 18}...]Hints:Use string conversions like toString Create a toNumber functionTry not to look at the replies until you have tried the challenge yourself.

I was asked to do pull all the password encryption methods for Cisco (route-switch) devices from our security team.Here are a couple of NQE that I wrote to send off to the security team, hopefully it might be of use to someone else. They are pretty simple but if anyone has recommendations to enhance or combine into a single script, lemme know!Results: Showing IOS/IOS_XE DevicesNexus - ** Add custom command to collection for NX-OS Devicesshow run | grep admin password/** * @intent Show encryption level and method on Cisco NX-OS devices * Test * @description Use CSV table below to match Encryption Level to Method * add custom command for NXOS devices: show run | grep admin password**/Encrpytion = """csvEncryLvl,EncryMeth9,SCRYPT-Hash5,MD54,SHA25610,SHA5127,Cisco_Type7-Algorithm0,No-Encryption""";pattern1 = ```{username:string} {admin:string} {PW:string} {Level:number} {str:string} {role:string} {NA:string}```;foreach device in network.deviceslet platform = device.platformwhere platform

It may be useful to compare the output of a traceroute against the Path Search output from Forward Networks.The following NQE query takes a list of IP addresses as a parameter, and returns a list of devices based on interface IPs.This query could be used while onboarding sources into Forward Networks. If there is no device entry for an interface IP address from this NQE, it could mean that the device with that IP address needs to be added to the collection (to Sources).If there is overlapping IP space in the network - for example, if private IP space for network interface IPs at difference locations is the same - this query will return ALL the devices with a given interface IP.Note that Forward Networks’ Path Search is superior to traceroute in that Path Search will shows layer-2 hops and cloud network objects that don’t respond to traceroute. import "@fwd/Interfaces/Interface IPs";deviceIps = foreach device in network.devices select { device: device.name, ips: (foreach record

how can i get information about device uptime ?

This NQE can be a quick way for you to identify interfaces and subinterfaces with configured ACLs. This could be invaluable from a couple angles: path analysis/troubleshooting and audit.Check it out! Let me know what you think!*I put both where length(acls.inboundAclNames) > 0 && length(acls.outboundAclNames) > 0andwhere length(acls.inboundAclNames) > 0 || length(acls.outboundAclNames) > 0because I feel both can have benefit in their own circumstances.foreach device in network.devicesforeach interface in device.interfacesforeach subinterface in interface.subinterfaceslet acls = subinterface.aclswhere length(acls.inboundAclNames) > 0 && length(acls.outboundAclNames) > 0// where length(acls.inboundAclNames) > 0 || length(acls.outboundAclNames) > 0select { deviceName: device.name, asset: device.tagNames, interfaceName: interface.name, subinterfaceName: subinterface.name, inboundAclNames: acls.inboundAclNames, outboundAclNames: acls.outboundAcl

Team, i am collecting frtianazlyer data from fortinet firewall via custom command , however i tried below query to get the data . pattern_faz =  ```config log fortianalyzer setting  set status enable    set server {faz:string}    ```;foreach device in network.devices/* where device.platform.vendor == Vendor.FORTINET */  let outputs = device.outputsforeach command in outputs.commands   where command.commandType == CommandType.CUSTOM   where command.commandText == "show  log fortianalyzer setting"  let configurations = parseConfigBlocks(OS.FORTINET, command.response) foreach match in blockMatches(configurations, pattern_faz)/* where !matches(device.name, "*_*") */ select {  deviceName: device.name,  SiteName: device.locationName,  "Primary DNS": match.data.faz,}   but unfortunatelly i m getting zero result. can anyone help on this

Discover insightful network performance metrics—without having to write a single character of code. In this article, you'll learn how to quickly check the uptime of your network devices using the Forward Platform. It’s an easy introduction to show you how to extract network insights using Forward’s built-in capabilities.Log in to your Forward Platform In the left navigation, scroll down to the NQE section and click Library. At the top of the query window, click the New query icon When prompted, provide a unique name for your query.  Save time finding scripts - create a folder to store you new scripts in one place Your query is now open and ready to edit. Remember, you’re not writing one character of code.  On the far right side of the window, click the Data Model tab. Type uptime in the search field. This displays elements in the Forward data model that pertain to uptime.    Hover your cursor over the first result - uptime:Duration. A dialogue displays a description of this dat

We currently use Ansible playbooks to add or delete network devices to our various NMS tools. I want to add Forward Networks to this job so newly added devices or old devices being removed are part of this automation. When FN discovers a device it appears to use sysName for the “Name” of the device. The API however requires me to provide the name value. Is there anyway to just use the management IP to add it to FN and have FN set the name like it does during its own discovery?

I have a requirement to look for an IP anywhere in the configurations files that pertain to devices with a specific name.  I tried to use the built in NQE under Forward Library>Device>Config Search, but when I enter the IP in the bottom box of the Parameters section, “Config_Pattern”, the results come back blank.  Yet when I look at the device config, the IP I copied and pasted appears in the actual configuration.  Also, the built in NQE seems picky...as in it wont pick of tacacs+ or acl, will pickup tacacs...and case sensitive as well apparently. For now, im looking for help with the IP search, I just wanted to not other issues with it.

Helper Functions are readily available queries in the Forward Library that you can use to streamline NQEs and save valuable coding time. These pre-built utilities empower users to accomplish intricate tasks without needing to reinvent the wheel.What Are Helper Functions?Helper functions simplify common networking queries. They reduce the need to manually generate code, enabling users to:Extract data with greater ease, including IP addresses and VLAN associations. Identify device types, configurations, or compliance based on standards. Handle complex calculations and data parsing. Combine multiple functions for advanced queries.These functions are continuously maintained by the Forward Networks engineering team, ensuring compatibility with the latest standards and device updates. Key Helper FunctionsSTIG Device Identification:Description: Identifies Cisco and Juniper switches and routers that match the Security Technical Implementation Guide (STIGs), saving time on pattern matching and