Discovered CITs and Relationships

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)`

This section describes SE storage entities in UCMDB:

Fibre Channel Connect. Represents a fibre channel connection between fibre channel ports.

Fibre Channel HBA. Has change monitoring enabled on parameters such as state, status, version, firmware version, driver version, WWN, and serial number. A Fibre Channel HBA inherits from the Node Resource CIT.

Fibre Channel Port. Has change monitoring enabled on parameters such as state, status, WWN, and trunked state. Since a Fibre Channel Port is a physical port on a switch, it inherits from the Physical Port CIT under the NodeElement Resource CIT.

Fibre Channel Switch. Falls under the Node CIT because SE maintains an IP address for each switch. Parameters such as status, state, total/free/available ports, and version are change monitored.

This package retrieves Fibre Channel Switch details from the mvc_switchsummaryvw and mvc_switchconfigvw views. The job retrieves detailed information about Fibre Channel Ports on each switch from the mvc_portsummaryvw view.

Logical Volume. Represents volumes on storage arrays and hosts with change monitoring on availability, total/free/available space, and storage capabilities.

Tape: Represents a tape library.

Storage Array. Represents a storage array with change monitoring on details such as serial number, version, and status. Since a storage array may not have a discoverable IP address, it inherits from the Network Device CIT.

NetApp Filer. This is a specialized storage array from the NetApp application.

Both Storage Array and NetApp Filer CITs retrieve details from the mvc_storagesystemsummaryvw view. DFM retrieves detailed information on Storage Processors and HBAs from the mvc_storageprocessorsummaryvw and mvc_cardsummaryvw tables respectively.

The SE database may possibly not be able to obtain IP address information on storage arrays for a variety of technical and policy related reasons.

Since Fibre Channel Ports may be present on a storage array, Storage Processor, or HBA, DFM uses three separate queries to retrieve Fibre Channel Ports for each storage array. Detailed information about Fibre Channel Ports on each array is retrieved from the mvc_portsummaryvw view. Since this view uses a container ID as the key, DFM queries the view by container ID for each storage array, each Storage Processor on a storage array, and each HBA on a storage array.

DFM retrieves detailed information about Logical Volumes on each storage Array from the mvc_storagevolumesummaryvw view.

DFM retrieves detailed information about Tape Library from the mvc_tapelibrarysummaryvw view.

Results from these queries populate a map as shown below:

Storage Fabric. Inherits from the Network Resource CIT and represents a storage fabric. This CIT has no change monitoring enabled.

Storage Processor. Represents other storage devices such as SCSI controllers, and inherits from the Host Resource CIT. A Storage Processor CIT monitors change on parameters such as state, status, version, WWN, roles, power management, and serial number.

Storage Pool. Storage Pool information is also collected from each storage array using the query below.

Results from this query populate a map as shown below: