|
Help for this subject
Expressions
Table of Search Fields
Field Types
Radio Button
Checkbox
Text
Substring
Date
Address
Label
Other Help Topics
Full Search Help
Search Fields
Display Options
Performance
By Record Type
Node
User
Network
Group
Admin Team
Domain
Quick Search
Log Search
Search Help
Main Help Page
|
This page discusses how to form a search.
Expressions
Full Search will support the below wildcards, separators and operators
in certain search fields. See Field Types for
details on what each field will support.
- Wildcards
- * and % are multi-character wildcards
- ? and _ are single character wildcards
- [ ] indicates a range of characters.
- [^] indicates NOT in a range of characters
- For example, [a-c]? means all words beginning with a, b or c
followed by just one character. "am" or "be" would match.
- Separators
- separators are spaces and carriage returns
- trailing and leading spaces are stripped off unless quoted
- Quotes: first double quote must be preceded by separator
or beginning of line
- Boolean Operators- listed in order of precedence
- NOT operators: "NOT" , "not". If there is no preceding operator,
AND is implied (i.e., "A not B" is equivalent to "A and not B")
- AND operators: "AND", "and"
- OR operators: "OR", "or"
- Case- all fields are case-insensitive
Table of Search Fields
Below is a table showing the fields on the full search pages. The first
column lists the field name. The second column, field type, describes how to
search for the information. The field types are
described in detail below.
The third column, Node, is checked if that field is in the Node Full Search.
The fourth column, User, is checked if that field is in User Full Search.
To see explanations of what each field means (not what the field type is),
please see the help pages for each record type.
| Field Name |
Field Type |
Node |
User |
Network |
Group |
Admin Team |
Domain |
| Name |
text |
x |
x |
x |
x |
x |
x |
| Name Type |
checkbox |
x |
|
|
|
|
|
| Receives Mail For(MX) |
text |
x |
|
|
|
|
|
| Node Type |
checkbox |
x |
|
|
|
|
|
| IP address |
address |
x |
|
|
|
|
|
| Address Space |
address |
|
|
x |
|
|
|
| IP Address Status |
radio |
x |
|
x |
|
|
|
| Hardware Address |
address |
x |
|
|
|
|
|
| DHCP |
radio |
x |
|
|
|
|
|
| DHCP Service |
text |
|
|
x |
|
|
|
| DHCP Options |
label |
x |
|
x |
|
|
|
| Roaming |
radio |
x |
|
|
|
|
|
| Groups |
substring |
x |
x |
x |
x |
x |
x |
| Department |
substring |
x |
x |
|
|
x |
|
| Location |
substring |
x |
|
|
|
|
|
| Room |
text |
x |
|
|
|
|
|
| Expiration Date |
date |
x |
|
|
|
|
|
| Make/Model |
text |
x |
|
|
|
|
|
| OS |
text |
x |
|
|
|
|
|
| Administrators |
text |
x |
|
|
|
|
|
| Node User |
text |
x |
|
|
|
|
|
| Custom Fields |
label |
x |
|
|
|
|
|
| Comments |
substring |
x |
x |
x |
x |
x |
x |
| |
|
|
|
|
|
|
|
| Active User |
radio |
|
x |
|
|
|
|
| Member |
Person |
|
|
|
|
x |
|
| Last Login |
date |
|
x |
|
|
|
|
| LNA |
radio |
|
x |
|
|
|
|
| Networking Consultant |
text |
|
x |
|
|
|
|
| |
|
|
|
|
|
|
|
| All Groups |
radio |
|
x |
|
|
|
|
| Record Type Access |
checkbox |
|
|
|
|
|
|
| All Record Types |
radio |
|
x |
|
|
|
|
| |
|
|
|
|
|
|
|
| Created By |
text |
x |
x |
x |
x |
x |
x |
| Created when |
date |
x |
x |
x |
x |
x |
x |
| Modified by |
text |
x |
x |
x |
x |
x |
x |
| Modified when |
date |
x |
x |
x |
x |
x |
x |
| |
|
|
|
|
|
|
|
| Phone |
not searchable |
|
x |
|
|
x |
|
| Email |
not searchable |
|
x |
|
|
x |
|
| Default Domain |
not searchable |
|
x |
|
|
|
|
| Default Address Space |
not searchable |
|
x |
|
|
|
|
| Default Group |
not searchable |
|
x |
|
|
|
|
| Low Reserve |
not searchable |
|
|
x |
|
|
|
| High Reserve |
not searchable |
|
|
x |
|
|
|
| Limited |
not searchable |
|
|
|
|
|
x |
| Allow Names |
not searchable |
|
|
|
|
|
x |
Field Types
Radio Button
With radio buttons, one and only one selection must be made. Radio buttons
are used for simple fields where one and only one choice must be made
(DHCP, Roaming, Active, etc).
Checkbox
Checkboxes are used when a field can be none, one or more values from
a short list.
Text
The text input field allows all the search expressions listed above.
Note that Name fields (Node Name, Alias, MX) assume that the search
is across all domains unless explicitly indicated.
Substring
Substring fields allow all the search expressions listed above but also
searches on substrings. For example, if "eng" is entered, the search
acts as if "*eng*" were entered. So "Mechanical Engineering" and "Electrical
Eng" would match. Substrings are generally used for fields like Department
and Location where the names can be quite long and may be abbreviated
in some way.
Date
Dates must be entered in the following allowed formats. Wildcards are
not allowed. For 2 digit years, the rollover year is 50. In other words,
years '00 to '49 actually mean years 2000 to 2049. Years '40 to '99
are assumed to mean years 1940 to 1999.
- m/d/yyyy, m/dd/yyyy, mm/d/yyyy, mm/dd/yyyy
- m-d-yyyy, m-dd-yyyy, mm-d-yyyy, mm-dd-yyyy
- m/d/yy, m/dd/yy, mm/d/yy, mm/dd/yy
- m-d-yy, m-dd-yy, mm-d-yy, mm-dd-yy
Address (IP and Hardware)
IP Addresses can be searched in two ways- by Address Space or by IP
Address. On the Node search page, searching by IP Address Space will
result in all the Nodes with IP addresses in the specified Address space.
Boolean operators AND and NOT are not supported. Separate search
expressions with the operator OR.
- IP Address Space Input Format
- w.x.y.z/n - existing address space with prefix (171.64.20.0/24)
- w.x.y/n - existing address space without trailing zeroes
(171.64.20/24)
- w.x.y.z - existing address space without prefix (171.64.20.0)
- w.x.y.* - existing address space with trailing zeroes replaced
by "*" (171.64.20.*)
- IP Address Input Format
- x.y.y.y format.
- x must be fully defined (171 or 172 or 128).
- y can be a number or wildcard. If a wildcard, subsequent
octets do not need to be listed. Ex. 171.64.2*
- The wildcards listed under search expressions are allowed.
Hardware Addresses can be searched with any of the above wildcards
listed under Search Expressions.
Punctuation and case are ignored. For example, hardware
addresses may be shown as ABCD.1234.5678 or abcd12:345678. Either
format is fine.
Label
The two label fields are DHCP Options and Custom Fields. Searches should
be in the following format:
- <label or option>=<value> For example, if the DHCP option is
"filename" and the value is "boot.txt", enter filename=boot.txt
or "filename=boot.txt".
- All the search expressions are supported.
- If either label or value has a space in it, quote the entire
expression. For example, if the custom tag is "monitor type" and
the value is "viewsonic 15", search by quoting the entire string
"monitor type=viewsonic 15"
|