Home » Dell Manuals » Hubs & Switches » Dell OpenManage Network Manager » Manual Viewer

Dell OpenManage Network Manager Web Client Guide 5.2 - Page 351

Attribute Appearance and Validation, Attribute Name, Parse Algorithm, Parse Expression

View all Dell OpenManage Network Manager manuals

Add to My Manuals
Save this manual to your list of manuals

Page 351 highlights

Attributes Extraction To support Adaptive Service and Active Monitor functions, Adaptive CLI provides a way for the user to define output schema attributes. This tab is active only if you have selected schema attributes previously in the Attributes portion of this editor. This lets you Add, Edit or Delete extracted attributes, like Error Conditions's editor, and configure them with the following fields: Attribute Name-This field specifies the name of the extracted attribute. To specify the output value of an attribute, select it from the provided list. Attribute Type-The data type of the attribute extracted. Only schema attributes of simple type String, Integer, Long, Float, Double, and Boolean are available to choose from. Parse Algorithm-Select from the pick list (Extract, Match). For match algorithm, the result is either true or false for the Boolean attribute type, 0 or 1 for numeric types, or "true" or "false" for String type. NOTE: Currently, Active Performance Monitor supports only numeric types. Parse Expression-Enter a regular expression for Parse Expression and the Parse Algorithm (Extract or Match) used when evaluating the device output on a given script execution. Click Apply to accept your edits, or Cancel to abandon them. Click Add new attribute extraction to add more such patterns to your script. Attribute Appearance and Validation Invalid schema attribute names appear in the script in red italics. This indicates that you cannot use such attributes in the script. Valid attribute names contain alphanumeric characters and underscore (_). They must begin with either an underscore or a letter [A-Za-z]. All blank space characters in the schema attribute name are converted to underscore (_) by default. A schema attribute name that is invalid in Adaptive CLI may still be valid in other entities, so you can specify them in the schema but they are not usable by Adaptive CLI. Click Apply to accept your edits for the script, or Cancel to abandon them. Actions Portlet | Actions and Adaptive CLI 351

Section	Page
Preface	9
Why Dell OpenManage Network Manager?	9
Key Features	9
Networks with Dell OpenManage Network Manager	11
Additional Products	11
Updating Your License	12
Online Help / Filter	12
Feedback	13
A Note About Performance	13
Getting Started with Dell OpenManage Network Manager	15
Overview	15
System Basics	15
Upgrading from a Previous Version	16
Supported Operating System Versions	16
Supported Web Browsers	19
Single Server Sizing	20
Sizing for Standalone Installations	21
64-bit	22
Tablets, phones and iPads	22
Network Basics	22
Name Resolution	23
Protocols	23
Overriding Properties	23
Fixed IP Address	24
Authentication	24
Supported PowerConnect Models	24
Windows Management Interface	24
Prerequisites	25
Firewall Issues	25
Web-Based Enterprise Management (WBEM) Driver	26
WBEM Prerequisites	27
Getting Started	27
Installation and Startup	28
Linux Prerequisites	30
Perl	32
Starting Web Client	32
Changing the Session Timeout Period	33
Control Panel	33
Search Indexes	34
[My Account]	34
RCSynergy / [Domain]	35
Portal > Users and Organizations	35
Public / Private Page Behavior	40
Portal > Roles	41
Portal > Portal Settings	41
Portal > [Other]	42
Redcell > Permission Manager	42
Redcell > Data Configuration	45
Redcell > Mediation	45
Redcell > Filter Management	48
Server	49
Redcell > Database Aging Policies (DAP)	50
Aging Policies Editor	52
Editing Tips	53
Aging Policies Options	54
Sub-Policies	55
Repositories	57
Portlet Level Permissions	58
Database Backup	61
Restoring Databases	61
Portal Database Backup / Restore	62
Quick Navigation	62
License Viewer	63
Discovery Profiles	65
Managed Resources	67
Common Setup Tasks	68
SMTP Configuration	68
Netrestore File Servers	70
Portal Conventions	71
Portal Overview	71
Tooltips	72
Refresh	72
The Back Button	72
Show Versions	72
The Dock	73
Status Bar Alerts	75
Chat / Conferencing	76
Menu Bar	77
Site Map	77
Graphs	77
Portlets	78
Portlet Instances	81
Mandatory Fields	81
Sorting Portlet Lists	82
Expanded Portlets	82
Common Menu Items	86
Import / Export	86
Sharing	87
Edit Custom Attributes	89
View as PDF	90
Tag	90
Audit Trail / Jobs Screen	91
Audit Trail Viewer	92
Audit Trail Portlet	93
Schedules	95
Schedules Portlet	95
Key Portlets	99
Overview of Key Portlets	99
Alarms	100
Expanded Alarm Portlet	102
Alarm Email	105
Event History	106
Event Processing Rules	108
Rule Editor	111
General	111
Filtering / Settings	112
Syslog Escalation Criteria	115
Actions	116
Trap Forwarding Process	118
Email Action Variables	122
Event Definitions	128
Event Definition Editor	128
General	129
Message Template	131
Correlations	132
Contacts	133
Locations	135
Tag	138
Vendors	139
Expanded Vendor Portlet	140
Resource Management	143
Introduction	143
Authentication	143
Container Manager	146
Container Manager Expanded	146
Container View	147
Container Editor	148
Map Context	151
Resource Discovery	152
Discovery Profiles	153
Discovery Profile Editor	154
Discovery Profiles Expanded	161
Managed Resource Groups	162
Static Group	164
Dynamic Group	165
Managed Resources	166
Managed Resources Expanded	173
New Link	175
Link Discovery	176
Link Discovery Prerequisites	177
Equipment Details	178
Performance Indicators	179
Interfaces	180
Interfaces > Details	180
Alarms	181
Ports	181
Ports > Links	182
Ports > Details	183
Details	185
Direct Access	188
MIB Browser	188
Terminal	190
Ping (ICMP)	191
HTTP / HTTPS	191
Ports	191
Ports Expanded	193
Port Editor	194
Report Templates	195
Report Template Editors	196
General	197
Inventory	198
Layout	199
Reports	200
Report Editor	204
General	205
Filter	205
Branding Reports	206
Visualize	207
Visualize My Network	207
Configuring Views	208
Actions	209
Control and Styles	210
ZOOM	210
DISPLAYED LEVELS	210
STYLE OPTIONS	211
VIEW DETAILS	213
Data / Node Finder	213
Layout	216
OVERVIEW	219
Alarms in Visualizations / Topologies	219
Links in Visualization	220
File Server / File Management	221
File Servers	221
File Server Editor	222
File Management	223
Configuration Files	229
Configuration File Editor	231
Image Repository	233
Firmware Image Editor	235
Configuration Image Editor	236
General Parameters	236
Configuration	237
Deploy Firmware	238
Deploy Configuration	240
Monitoring	243
How to’s	243
OpenManage Network Manager Server Statistics	244
Resource Monitors	245
Retention Policies	248
Monitor Editor	251
General	251
Monitor Options	254
Calculated Metrics	254
Thresholds	256
Inventory Mappings	259
Conditions	260
Monitor Options Type-Specific Panels	266
ICMP	267
Key Metrics	268
Proscan	269
SNMP	270
SNMP Interfaces	273
SNMP Table Monitor	274
Scheduling Refresh Monitor Targets	276
Top [Asset] Monitors	276
Top Configuration Backups	277
Dashboard Views	277
Performance Dashboard	279
Dashboard View Selection	280
Dashboard Editor	281
Convert Simple Dashboards to Custom Dashboards	286
Show Performance Templates	286
Key Metric Editor	289
Traffic Flow Analyzer	293
How does it work?	293
Setup	294
Exporter Registration	295
Traffic Flow Portlet	295
Drill Down	298
Search	300
Traffic Flow Analyzer - Example	300
Change Management / ProScan	303
Introducing ProScan and Change Management	303
ProScan Portlet	306
Compliance Policy Summary	308
Creating or Modifying a ProScan Policy	310
General	310
Targets	312
Criteria	313
Regular Expressions	320
Perl / Java (Groovy) Language Policies	322
Compliance Policy Job Status	324
Creating or Modifying ProScan Policy Groups	325
Change Determination Process	326
Change Determination Process Workflow	327
Change Determination Defaults	329
Compliance and Change Reporting	329
Actions and Adaptive CLI	333
Introducing Actions and Adaptive CLI	333
Using Adaptive CLI	334
Using Perl in Adaptive CLI	334
Actions Portlet	335
Adaptive CLI Editor	340
General	341
Attributes	342
Do not use Parameter Schema	342
Create a new Parameter Schema	342
Use an existing Parameter Schema for this Adaptive CLI	346
Validating IP Address Variables	346
Scripts	347
Script Settings	348
Attribute Appearance and Validation	351
Comparison	352
External Commands	352
Seeded Scripts	354
Adaptive CLI Script Language Syntax	358
Attributes	358
Conditional Blocks	359
Perl Scripts	360
Scheduling Actions	361
General	362
Parameters	363
Schedule	363
Active Performance Monitor Support	363
Adaptive CLI Records Archiving Policy	365

Match case Limit results 1 per page

Actions Portlet | Actions and Adaptive CLI

351

Attributes Extraction

To support Adaptive Service and Active Monitor functions, Adaptive CLI provides a way for the

user to define output schema attributes. This tab is active only if you have selected schema

attributes previously in the Attributes portion of this editor.

This lets you

Add, Edit

Delete

extracted attributes, like Error Conditions’s editor, and configure

them with the following fields:

Attribute Name—

This field specifies the name of the extracted attribute. To specify the output

value of an attribute, select it from the provided list.

Attribute Type—

The data type of the attribute extracted. Only schema attributes of simple type

String, Integer, Long, Float, Double, and Boolean are available to choose from.

Parse Algorithm—

Select from the pick list (

Extract, Match

). For match algorithm, the result is

either

true

false

for the Boolean attribute type, 0 or 1 for numeric types, or

“true”

“false”

for String type.

NOTE:

Currently, Active Performance Monitor supports only numeric types.

Parse Expression—

Enter a regular expression for Parse Expression and the Parse Algorithm

(Extract or Match) used when evaluating the device output on a given script execution.

Click

Apply

to accept your edits, or

Cancel

to abandon them. Click

Add new attribute extraction

add more such patterns to your script.

Attribute Appearance and Validation

Invalid schema attribute names appear in the script in red italics. This indicates that you cannot

use such attributes in the script.

Valid attribute names contain alphanumeric characters and underscore (_). They must begin with

either an underscore or a letter [A-Za-z].

All blank space characters in the schema attribute name are converted to underscore (_) by default.

A schema attribute name that is invalid in Adaptive CLI may still be valid in other entities, so you

can specify them in the schema but they are not usable by Adaptive CLI.

Click

Apply

to accept your edits for the script, or

Cancel

to abandon them.