Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Integrate NNMi Elsewhere with URLs > Launch a View (showView) > Monitoring Workspace Views

Launch a Monitoring Workspace View

Note If you copy/paste this URL, remove the spaces that were added for line-ending purposes in the documentation.

http://<serverName>:<portNumber>/nnm/launch?cmd= showView & view = <x>

Note If the NNMi Web server uses the https protocol, use https instead of http.

<serverName> = the fully-qualified domain name of the NNMi management server (values allowed here are determined by the Enable URL Redirect setting in User Interface Configuration, see Configure the NNMi User Interface)

<portNumber> = the NNMi HTTP port number

For a quick-reference list of all URL choices for launching NNMi, see Help → Documentation Library → Integrate NNMi Elsewhere with URLs. The Integrate NNMi Elsewhere with URLs page also contains a link to a list of sample URLs that you can copy/paste as a starting point.

Monitoring Workspace Views and Available Filters
View Name	x = View ID	Node Filter	Interface Filter
Non-Normal Node Sensors	`nonNormalNodeSensorTableView`	Yes	No
Non-Normal Physical Sensors	`nonNormalPhysSensorTableView`	Yes	No
Non-Normal Chassis	`nonNormalChassisTableView`	No	No
Non-Normal Cards	`nonNormalCardTableView`	No	No
+Critical Component Health	`criticalComponentHealthTableView`	No	No
+Critical Interfaces	`criticalInterfaceTableView`	Yes	Yes
+Critical Nodes	`criticalNodeTableView`	Yes	No
Non-Normal Interfaces	`nonNormalInterfaceTableView`	Yes	Yes
Non-Normal Nodes	`nonNormalNodeTableView`	Yes	No
Non-Normal SNMP Agents	`nonNormalSnmpAgentsTableView`	No	No
Not Responding Addresses	`notRespondingIPAddressTableView`	Yes	Yes
+Nodes by Status	`nodesByStatusTableView`	Yes	No
+Component Health by Status	`componentHealthByStatusTableView`	No	No
+Interfaces by Status	`interfacesByStatusTableView`	Yes	Yes
+Interfaces by Administrative State	`interfacesByAdministrativeStateTableView`	Yes	Yes
+Interfaces by Operational State	`interfacesByOperationalStateTableView`	Yes	Yes
IP Addresses by State	`IP AddressesByStateTableView`	Yes	Yes
Interface Performance	`interfacePerformanceTableView`	Yes	Yes
Card Redundancy Groups	`cardRedundancyGroupsTableView`	No	No
Router Redundancy Groups	`routerRedundancyGroupsStatusTableView`	No	No
Node Groups	`nodeGroupsStatusTableView`	No	No
Custom Node Collections	`customPollerNodeCollectionsTableView`	No	No
Custom Polled Instances	`customPollerPolledInstancesTableView`	No	No

The following are optional filter parameters:

http://<serverName>:<portNumber>/nnm/launch?cmd= showView&view= <x>&nodegroup= <Name>

http://<serverName>:<portNumber>/nnm/launch?cmd= showView&view= <x>&ifgroup= <Name>

Note If you copy/paste this URL, remove the spaces that were added for line-ending purposes in the documentation.

Filter by Node Group (launched Incident, Node, Interface, and IP Address views)
Attribute	Values
nodegroup	The case-sensitive Name attribute value of the Node Group to use as a filter for this view. Note The Node Group name is translated. If your team shares NNMi within multiple locales, use nodegroupid or nodegroupuuid. If the Name value includes space characters, consider replacing the space character in your URL statement (see W3C Rules for URLs).
nodegroupid	The `id` is the Unique Object Identifier (unique across the entire NNMi database). Provide the `id` of the Node Group to use as a filter for this view. This attribute value is not visible on any form within the console. To find this value, use the nnmconfigexport.ovpl command-line tool to export an XML file that includes the `id` attribute value for each object instance.
nodegroupuuid	The `uuid` is the Universally Unique Object Identifier (unique across all databases). Provide the `uuid` of the Node Group to use as a filter for this view. This attribute value is not visible on any form within the console. To find this value, use the nnmconfigexport.ovpl command-line tool to export an XML file that includes the `uuid` attribute value for each object instance.

Filter by Interface Group (launched Interface and IP Address views)
Attribute	Values
ifgroup	The case-sensitive Name attribute value of the Interface Group to use as a filter for this view. Note The Interface Group name is translated. If your team shares NNMi within multiple locales, use ifgroupid or ifgroupuuid. If the Name value includes space characters, consider replacing the space character in your URL statement (see W3C Rules for URLs).
ifgroupid	The `id` is the Unique Object Identifier (unique across the entire NNMi database). Provide the `id` of the Interface Group to use as a filter for this view. This attribute value is not visible on any form within the console. To find this value, use the nnmconfigexport.ovpl command-line tool to export an XML file that includes the `id` attribute value for each object instance.
ifgroupuuid	The `uuid` is the Universally Unique Object Identifier (unique across all databases). Provide the `uuid` of the Interface Group to use as a filter for this view. This attribute value is not visible on any form within the console. To find this value, use the nnmconfigexport.ovpl command-line tool to export an XML file that includes the `uuid` attribute value for each object instance.

The following are optional parameters:

http://<serverName>:<portNumber>/nnm/launch?cmd= showView&view= <x>&menus= <true|false>&newWindow= <true|false>&envattrs= <name1= value>;<name2= value>

Note If you copy/paste this URL, remove the spaces that were added for line-ending purposes in the documentation.

Attributes for Launched Views
Attribute	Values
menus	true = Show the view's button bar. If not specified, the default is true. false = Hide the view's button bar to save space in the view.
newWindow	true = Display the view in a new browser window. This new window does not display the browser-specific menu bars. The browser-specific menu bars are hidden to provide the maximum amount of room for the requested view. false = Display the view within the current browser window (if not specified, the default is false).
readonly	true = Prevents the user from doing either of the following: Open any forms from the view Manipulate any objects in the view (for example, delete an object) false = Enables the user to do either of the following: Open any forms from the view Manipulate any objects in the view (for example, delete an object)
envattrs	Use Environment Attributes (`envattrs`) to pass `<name=value>` pairs from an external application to NNMi. Environment Attributes are session-specific and stored in memory (not in the NNMi database). The name-value pairs can be any arbitrary string (as required by the external program). For example, let’s assume that NNMi was launched from an application that wants to preserve a session ID (123) and object attribute (node25) as follows: `http://<yourServerName/nnm?cmd= showView&objtype= Node&envattrs= com.my.sessionId= 123;com.my.objectName= node25` Note See Pass Environment Attributes for information about how to retrieve these Environment Attributes (`envattrs`) `<name=value>` pairs from NNMi, and pass them back to the originating external application.

Send Help Center feedback