Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

 

 

 

Home > Success Center > IP Address Manager (IPAM) > IPAM Administrator Guide > SolarWinds Orion Core Components > Defining pattern limitations

Defining pattern limitations

Table of contents
No headers
Created by Nanette.Neal, last modified by Nanette.Neal on Jul 22, 2016

Views: 303 Votes: 0 Revisions: 2

Pattern limitations may be defined using OR, AND, EXCEPT, and NOT operators with _ and * as wildcard characters. The following examples show how to use available operators and wildcard characters:

Note: Patterns are not case sensitive.

  • foo matches only objects named "foo".
  • foo_ matches all objects with names consisting of the string "foo" followed by only one additional character, like foot or food, but not seafood or football.
  • foo* matches all objects with names starting with the string "foo", like football or food, but not seafood.
  • *foo* matches all objects with names containing the string "foo", like seafood or Bigfoot.
  • *foo* OR *soc* matches all objects containing either the string "foo" or the string "soc", including football, socks, soccer, and food.
  • *foo* AND *ball* matches all objects containing both the string "foo" and the string "ball", including football but excluding food.
  • *foo* NOT * ball * matches all objects containing the string "foo" that do not also contain the string "ball", including food but excluding football.
  • *foo* EXCEPT *ball* matches all objects containing the string "foo" that do not also contain the string "ball", including food but excluding football.

You may also group operators using parentheses, as in the following example.

(*foo* EXCEPT *b*) AND (*all* OR *sea* ) matches seafood and footfall, but not football or Bigfoot.

Last modified
10:34, 22 Jul 2016

Tags

Classifications

Public