Skip to main content

Recently active topics

10 Topics
Tyson Henrie
Employee
Tyson HenrieEmployee
posted in Koan Challenges
Play our NQE Koan Challenge - Calculate Centuries

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.

232
davetee
Community Manager
peyman.kazemian
Employee
peyman.kazemianEmployee
published in Path Search
Path Search - Understanding the Difference Between Destination IP and To

In Forward Networks' path search feature, the two queries “from IP with Destination IP” and “from IP To IP” may look similar, but perform very different kinds of searches with possibly different results. Here's a breakdown of their differences:1. From IP A with Destination IP BPurpose: shows path results that start from location of A, and the packet’s destination IP is set to B, at source (i.e. at location of A). Shows both dropped (e.g. by firewall) and delivered traffic. Behavior: The path search begins from the source and considers the destination IP as part of the packet header. It does not explicitly locate the destination as a physical or logical endpoint; instead, it treats the destination IP as an attribute of the packet. Use Case: Ideal when you want to trace how a packet with a specific source and destination IP address moves through the network, even if the destination location is unknown or incomplete in the model. Also useful when troubleshooting an issue from the point of

913
H
T
Employee
TimFEmployee
published in On-Prem Deployment
Extend an LVM with a blocking partition

Expanding an LVM (Logical Volume Manager) when it is not the last partition on a disk requires a structured approach to ensure data integrity and successful volume extension. The outlined procedure provides step-by-step instructions to allocate additional storage by creating a new partition, adding it to the volume group, extending the logical volume, and finally resizing the filesystem. By following these steps, users can efficiently expand their storage capacity without disrupting the existing partitions. The key benefits of using these instructions include preventing partition overlap, ensuring proper allocation of free space, and maintaining the stability of the filesystem. Additionally, the process leverages built-in Linux commands such as lsblk, fdisk, pvcreate, vgextend, and lvextend, making it accessible to system administrators managing LVM environments. This method is particularly valuable in virtualized environments where disk sizes are adjusted dynamically, enabling seamles

70
T
Employee
Tyson Henrie
Employee
Tyson HenrieEmployee
posted in NQE
Check whether the interface Description field contains the name of the connected device

This is to discuss a common practice with the use of the interface Description field.It is really common to look at CDP or LLDP and find the neighbor device name, then put that remote device name into the interface Description of the interface that connects these two devices together.  It is also common to add the remote device interface as well./** * @intent Verify if the interface description includes the device name of the linked device * @description Use the Link element of the data model to determine the device name and interface * of a networking device that is connected to this interface. * Verify that the remote device name and remote interface an included in the interface Description. */export getL3Interfaces(device: Device) =  foreach iface in device.interfaces  where length(iface.links) > 0  foreach ifaceIpInfo in getSvis(iface) + getSubIfaces(iface)  select {    name: ifaceIpInfo.name,    adminStatus: ifaceIpInfo.adminStatus,    operStatus: ifaceIpInfo.operStatus,    ipv

150
Tyson Henrie
Employee
peyman.kazemian
Employee
peyman.kazemianEmployee
published in Path Search
Path Search - What to Do When Your Search Query Returns an Unexpected Result

Running a path search query in Forward Networks and getting zero results or unexpected results can be frustrating, especially when you're confident the query is correctly structured. Zero results typically indicate a mismatch between the query and the network model, incomplete data, or overly restrictive filters. Here’s a practical guide to troubleshooting and resolving these scenarios.1. Investigate the Starting PointA common reason for zero results is an issue locating the source IP:Check if the source IP was resolved correctly: Hover over the source IP to see if it was mapped to a host, device, or interface. If the system couldn’t locate the source: Search for the address used in the “from” clause. Do you see a subnet containing the source? If the gateway on which this address resides is missing from the snapshot, add it to the snapshot. If the source gateway cannot be added, consider using Edge Node and connect it to the right entry point for the subnet it represents. This will

240
peyman.kazemian
Employee
elyor_khakimov
Employee
elyor_khakimov
published in Path Search
Unlocking the Power of Network Path Search: A Quick Reference Guide

The Path Search Cheat Sheet (🔽 attached below 🔽) is a powerful resource designed to help network engineers efficiently query and analyze complex network paths with the Forward Platform. Rather than detailing every possible function, this guide gives you the tools to resolve network issues and optimize performance. This reference is more than just a list of commands—it’s a blueprint for turning raw network data into actionable intelligence. Whether you’re troubleshooting an immediate problem or planning for future growth, this cheat sheet is your guide to making the most of Forward Networks’ powerful path search capabilities.Driving Value with Path SearchBy leveraging the cheat sheet, you can:Quickly Diagnose Issues: Identify traffic bottlenecks, policy enforcement problems, or unreachable destinations. Validate Configurations: Confirm that routing, firewall policies, and other configurations align with intended network behavior. Optimize Network Performance: Gain actionable insights

370
elyor_khakimov
Employee
G
Spotter
gbaronSpotter
asked in NQE
configuration search within Network Devices

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.

816
G
Spotter
AricaFN
Employee
AricaFNEmployee
published in NQE
Unlocking Efficiency with Forward Networks Helper Functions

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

310
AricaFN
Employee
AricaFN
Employee
AricaFNEmployee
published in NQE
Using the WHEN statement for clean, efficient NQEs

When I first started working with Network Query Engine (NQE), I didn’t have a traditional software engineering background and was learning Python and NQE at the same time. I needed to create a custom solution for handling certificate expiration dates across different network devices. The Python part of my brain was hoping to find a traditional for loop capability, and was a bit lost when that didn’t exist. As you may know, you can solve any given problem 10 different ways with NQE. I wanted to write a solution that would be clean, readable, easy to maintain, and share with others without having to provide too much explanation .That’s where the WHEN statement came into play.What is a WHEN Statement?Within the NQE Data Model, there are some data types that have a fixed list of options.The WHEN statement in NQE allows you to evaluate different conditions based on those options. WHEN is like switch or case statements in other programming languages, but it’s more tailored to pattern matchin

1222
davetee
Community Manager
R
Spotter
Rohit_809 KumarSpotter
asked in NQE
How can i get the config register value for cisco devices ?

How can i get the config register value for cisco devices ?

642
R
Spotter
  • Community Champ Award
    Vladi Bhas earned the badge Community Champ Award
  • Community Champ Award
    dakotagloryhas earned the badge Community Champ Award
  • NQE Contributor
    CarlBhas earned the badge NQE Contributor
  • NQE Contributor
    gbaronhas earned the badge NQE Contributor
  • Community Contributor
    Rohit_809 Kumarhas earned the badge Community Contributor
Show all badges
Terms of UseCookie settings