Adding VNM Model in TopOrg View

book

Article ID: 126343

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

Using TopOrg views and then to add application models (like VNM, ArchiveManager or OnlineBackup or Locallscpe) to see the Spectrum internal alarming is not possible.
When adding model or container to the TopOrg view this is limited to those which are shown in the TopOrg -> Contents -> Topology Tab :: Here to select "Create Model by Type".

When trying to cut&paste from Universe or via Locater search "any" model into a TopOrg Container this will show a message box reporting:

The following models cannot be added to this view:
<model-name> of type <model-type-name> 
     <<< OK >>>

<Please see attached file for image>

Copy to TopOrg fails with Message-Box

 

We are using Toporg and now we do not see the Alarms on the VNM and Locallscpe. I've tried to copy the VNM model to the TopOrg but that seems not to be possible. How is it possible to also see all the VNM alarms when the TopOrg is selected?

Environment

This applies to all supported CA Spectrum platforms.

 

Resolution

This is functioning as designed - not any model could be copied into TopOrg View.
 Workaround via manual setup / using CLI to create "association"

Sample: 
./create association rel=Owns lmh=<mh_org_container> rmh=<mh_application>

Additional Information

The CLI tool is a utility to directly manipulate the SpectroSERVER database and any action could become critical. 
When starting CLI this message is shown:

WARNING:  CLI is a powerful tool that allows a user to make changes
directly to the SPECTRUM knowledge-base without the error checking
provided by OneClick.  Please read the accompanying CLI user
documentation before using the create, destroy, or update commands.


CA strongly recommends to create a SpectroSERVER database savefile (OnlineBackup file) before using CLI 
accessing and modifying the Spectrum database.

Finding the TopOrg Container MH - i.e. via OC-Console view:

<Please see attached file for image>

finding model-handle per model

Then finding the models in question - i.e. via CLI:
[[email protected] vnmsh]$ ./show models | grep VNM
0x11000000  grdalabspec02                             0x10003     VNM           
[[email protected] vnmsh]$ ./show models | grep OnLineBackup
0x11000008  OnLineBackup                              0x10403     OnLineBackup  
[[email protected] vnmsh]$ ./show models | grep FaultIso
0x1100000b  Fault Isolation                           0x10413     FaultIsolation
[[email protected] vnmsh]$ ./show models | grep Arch
0x1100005a  ArchMgr                                   0x10417     ClientApp    

Then create the "association" / sample for one: 
./create association rel=Owns lmh=0x1102f117 rmh=0x1100005a

Attachments

1558690517581000126343_sktwi1f5rjvs16ga8.png get_app
1558690514632000126343_sktwi1f5rjvs16ga7.png get_app