NQE

After spending the last 8 weeks as an intern, I’ve learned a lot about network digital twins and how they enhance visibility, maintenance, and security. You can read more about my experience in this post. Over the last few weeks, I’ve created powerful scripts to answer common security and compliance questions that years ago would have taken hours trying to answer in the CLI. The query I created below identifies Arista devices that have a security vulnerability in their configuration.Benefit of this NQEThis query solves similar issues to those I encountered at previous network admin jobs. This query drastically cut the time I would have otherwise spent investigating issues on individual devices. With a little effort in creating this query, I can now answer these questions in seconds with each

Hi all, I am new to NQE and trying to find out a way to list up all the devices with the EOL/S status.Here is the script which the first phase./*** @intent End-of-life data for operating systems** @description If  EoL data is known for the OS of a device,* then that device shows the respected dates, if not EoS related columns shows null.** Data exists for devices running any of these OSes:* ARISTA_EOS, IOS, IOS_XE, IOS_XR, JUNOS, NXOS, and PAN_OS. */ foreach device in network.deviceslet platform = device.platformlet osSupport = platform.osSupport/* where isPresent(osSupport) */select {  Device: device.name,  Vendor: platform.vendor,  Model: platform.model,  OS: platform.os,  "OS Version": platform.osVersion,  "End of OS maintenance": osSupport?.lastMaintenanceDate,  "End o

Hello!    We are trying to write a NQE referencing the State File OSPF PEERS, but we cant find anything related to code or the CommandType, or any data really, in the NQE data model.  Can someone please point me in the right direction.

You can use NQE to examine the firewall rules in all firewalls in a network. However, you will need to use a different approach depending on what you want to audit in your security rules.Forward Enterprise collects and parses the ACLs and security rules from all devices: firewalls, routers, switches, and so on. The data is then parsed and normalized. This data is stored in a database in a custom format that allows the Forward application to perform path analysis.The following NQE query uses the Forward Enterprise aclEntry object to provide consistent output from any vendor Firewall. Note that the scope of device types in the output is limited by using the where statement and filtering to DeviceType.FIREWALL.This query will work for every ACL/security rule on any Firewall in the network. However, because the query is working on normalized data, each security rule in a firewall may be broken

If you’re interested in other ways to identify non-compliant devices, check out this article I wrote: The Hardware and Software Compliance Checker is a powerful script designed to ensure all network devices are authorized and operating on approved OS versions. By providing a detailed view of the network inventory, this query identifies devices that either lack approval to be on the network or are running outdated or incorrect software. With its comprehensive approach, this NQE empowers network administrators to maintain compliance, enhance security, and streamline operational workflows.Benefits of Using the Hardware and Software Compliance Checker:Enhanced Compliance: Ensures all devices on the network are authorized and running approved OS ve

If you’re interested in other ways to identify non-compliant devices, check out this article I wrote:The End-of-Life (EOL) and End-of-Sale (EOS) Checker is a streamlined tool that identifies network devices nearing or past their vendor support lifecycle. By cross-referencing inventory data with a list of outdated devices sourced from vendor sites, such as Cisco’s EOL/EOS database, the query ensures administrators are aware of devices that may pose operational risks. This proactive approach enables organizations to plan replacements, reduce downtime, and ensure ongoing compliance with industry standards.Benefits of Using this NQE:Proactive Replacement Planning: Identifies aging devices before they become liabilities, reducing unplanned downtime. Streamlin

I am trying to find the specific commandType for the information in the device ‘nat v4’ result. For Cisco devices, it looks like a result of ‘show ip nat statistics’ but I cannot find the specific commandType in the data model documentation. Is there somewhere that can be searched?  

Some output from commands has a comma immediately after the output number: nat-limit statistics: max entry: max allowed 0, used 0, missed 0 I can parse the result as a string, but want to grab the data as a number so I can do other operations (math/comparison/etc). I can remove the comma with a replacement function (thanks ​@GaryB )cleanComma(s) = replaceMatches(s, ",", ""); however the output, even while being a number (0) is still considered a string. Looking at toNumber, the documentation gives the warning it is for IPv4 addresses only. Is there a way to convert a string into a number variable type?

I am using the NQE query to retrieve Fortinet Firewall NTP details. However, I am also receiving details for VDOM (Virtual Context ) or virtual contexts, which I do not want. Could you please assist me in refining the NQE query to exclude these VDOM details?   

Hi Team,I need to obtain a list of devices that have syslog enabled as well as those that do not. I have checked the Forward Library and the community but could not find any relevant queries for this purpose. Could you please assist me in generating the list of devices with syslog enabled and those without it? Thank you!

NQE Query for F5 NTP Server details from config, Please help us to collect this data.

Your Regex Toolkit is Here!Starting with Release 24.10, NQE supports regular expressions (or “regex”), one of the most requested features from our community. Regular expressions are an essential toolkit for working with textual data, and networking often requires us to handle plenty of it. Whether you’re parsing the output of commands like show interfaces brief or making sense of complex device naming conventions, regex in NQE can make these tasks faster and more efficient. Why Regular Expressions Matter in NetworkingRegular expressions provide a powerful way to:Identify patterns within strings, such as determining if a device name follows a specific naming convention or verifyi

Do patterns need to be standardized or will blockMatches match when lines are missing? pattern=```line one {main:string}    sub-line1 may or may not be consistently present    sub-line2 may or may not be consistently present    sub-line3 {value1:string} is target and sub-line3 will always be there    sub-line4 may or may not be consistently present    sub-line5 may or may not be consistently present    sub-line6 may or may not be consistently present    sub-line7 may or may not be consistently present    sub-line8 {value2:string} is target and sub-line8 will always be there         sub-sub-line9 {value3:string} is target and sub-sub-line9 will always be there        sub-line10 may or may not be consistently present    sub-line11 may or may not be consistently present    sub-line12 {value4:string} is target and may or may not be present         sub-sub-line13 {value5:string} is target

One of my customers came to me with a problem.Given a list of servers, how to determine if the keys applied are unique.Took some overnight thinking on this but using a simple approach with our group qualifier we can restructure the output in a way we can make the evaluation.The first thing we need to do is provide the input data.You should always have data that will represent a pass and a failure scenario. This way when posting here on the community, others can replicate the query and have a firm understanding of the outcome testpass = """set system ntp server 1.1.1.1 key 1set system ntp server 2.2.2.2 key 2set system ntp server 3.3.3.3 key 3""";testfail = """set system ntp server 1.1.1.1 key 2set sy

I had to change a lot, but this keeps the intent.  This is from a PANOS firewall.  The problem is that I am trying to find the objects in this list.  However, some objects have double quotes to show there are spaces in the name of the object and some do not.  I’m not sure how to clean this since NQE natively does not use double quotes to designate a single object that happens to contain spaces. sampleInput = """policy { shared; panorama { address-group { THE-GRAPE-Subnets { static [ "Green Grapes Are Good" RedGrapes BlackGrapes "Wine Grapes" PurpleGrapes]; tag GRAPES; description "This is a list of Grapes"; }""";pattern01 = ```policy panorama address-group THE-GRAPE-Subnets static "[ {object: (string*)} ```;foreach x in [1]let config = parseConfigBlocks(OS.PAN_OS, sampl

vlan456 is configured with VRRP group 456, for the below query, length of vrrpFhrpGroupsCount is returned as 0configuration snippet:interface vlan456 no shutdown ip address 10.7.0.1/26 ip pim sparse-mode ip igmp version 3 ! vrrp-group 456  priority 110  virtual-address 10.7.0.7!for the below query,@queryget_vrrp_details(host_pattern: String) =    foreach device in network.devices        where matches(device.name, toUpperCase(host_pattern))            foreach interface in device.interfaces            where isPresent(interface.routedVlan)            let routedVlan = interface.routedVlan            let ipv4 = routedVlan.ipv4            let fhrp = ipv4.fhrp            let vrrp = fhrp.vrrp

I am trying to get data out of a Cisco DMVPN hub on the spokes via NHRP database.  Specifically the ARIN addresses and if the spoke has a firewall or other NAT. I was modelling off of this NQE question and it works...except for the 2nd pattern is not detecting the child line.The above question had a parent line that was always present if the new child was present and NHRP has the new child only if there is a NAT in the path while the parent line is always present. The line in question is the “(Claimed NBMA address: <IP address>)” line at the bottom of the 2nd example - it is indented 1 space from the line above ‘NBMA address’ which is always present. I tried both the NHRP data in the data model as well as a custom command ‘show ip nhrp’ with identical results.   //NHRP Database outp

how can i get the Egress and Ingress IP Details by NQE 

Need one NQE Queries for Public IPs only from where outside traffic is coming to my internal network. Also want to get the output of below command on Fortinet Firewall through NQE Queries. “ local route prefix list ”I used one NQE Query that already on Forward Library - “Interfaces Using Public IPv4 Addresses” but this is not fulfilling my requirement. Tried Forward AI Assist also but not useful in this scenario.Can you please help me on this ? 

This article explores NQE's robust pattern matching for extracting and parsing data, simplifying complex tasks with high-level, well-defined types for reporting and evaluation.Table of ContentsApproach 1: Leveraging the “or” pattern as described here Approach 1 Test  Approach 2 : Unifying multiple patterns Approach 2 Test Approach 3: Evaluation via token count

Is there a way to get the pair of switches for the VRRP protocol using NQE?

I am trying to get the output from commandType NHRP_STATE so I can then pull out the tunnel peer IPs with a patternmatch. When the NHRP table was a custom command the command.commandText was able to get this information, now how to do so that NHRP is part of the data model?

foreach device in network.devicesselect {  deviceName: device.name}For the above NQE, if I get the device names in the format “aaa_bbb_ccc”, is there a way to split the output based on the string “_” and have three different fields?

OverviewIn my recent work with Palo Alto firewalls, I noticed that keeping configurations compliant can get complex, especially when administrators need to modify default settings for certain applications. Small changes to session handling or TCP timeouts, while necessary for specific use cases, can introduce inconsistencies and potential compliance issues. I developed straightforward NQEs to create compliance checks that help us monitor and manage these configurations effectively. Key Benefits:Improved Visibility: The compliance checks I set up give us a clear view into any configuration deviations across firewalls, making it easy to spot unauthorized changes.

how can i merger 2 or 3 NQE Query into 1 , so that i can get output in single file.