HPE Software Products: Storage Essentials
Share |

(SOM) Support Tip: SOM with OBR 10.01 command "somdatatransfercertconfig.ovpl -shrdbconfig" failsOpen in a New Window

Hello SOM Community,

Here's some information that will help you if you have OBR 10.01 installed prior to performing the Post-Installation Steps for OBR.

When attempting to configure Storage Operations Manager (SOM) to obtain Dashboard Analytics from Operations Bridge Reporter (OBR), using the somdatatransfercertconfig.ovpl -shrdbconfig command an error is encountered.

Steps to reproduce the error and issue.

Install OBR 10.00 and the OBR 10.01 Patch. After that, do all of the OBR post-install configurations. and then try to run the somdatatransfercertconfig.ovpl -shrdbconfig command.

C:\Program Files (x86)\HP\HP BTO Software\bin>somdatatransfercertconfig.ovpl -shrdbconfig <IP Address> 5433 verticadba <passwd>

Configuring the SHR Database details...
   SHR Database Server : <IP Address>
   SHR Database Port   : 5433
   SHR Username       : verticadba
   SHR Password       : <passwd>

args : 15.218.122.43 5433 verticadba <passwd>
Oct 04, 2016 11:10:03 AM com.hp.se.disco.common.analytics.CreateSHRDbConfig writeToConfigFile
INFO: SHR DB configuration written to C:\ProgramData\HP\HP BTO Software\se\conf\sdkConfig.cfg
Successfully created the SHR db configuration
Oct 04, 2016 11:10:03 AM com.hp.se.disco.common.analytics.CreateSHRDbConfig main
INFO: Successfully created the SHR db configuration
Oct 04, 2016 11:10:04 AM com.hp.se.disco.common.analytics.SHRSDK executeQuery
WARNING: Exception on query execution: [Vertica][VJDBC](4566) ERROR: Relation "md_fact_table" does not exist
Oct 04, 2016 11:10:04 AM com.hp.se.disco.common.analytics.SHRSDK executeQuery
WARNING: Submitted query: select count(*) from md_fact_table
Failed while testing the connection to the SHR DB!!!
Oct 04, 2016 11:10:04 AM com.hp.se.disco.common.analytics.CreateSHRDbConfig main
WARNING: Failed while testing the connection to the SHR DB!!!

With the installation of the OBR 10.01 Patch, the Post-Installation steps for the Vertica Database configuration are different.  One significant change is that there is a Vertica User (verticausr) specified as well as the Vertica Administrator (verticadba) during the Vertica Database configuration step.  The Vertica User, created during the OBR Post-Installation steps needs to be used instead of the Vertica Administrator with the somdatatransfercertconfig.ovpl -shrdbconfig command.

Please refer to the following knowledge document for more information and details.

KM02624620 - Storage Operations Manager command "somdatatransfercertconfig.ovpl -shrdbconfig" fails with "ERROR: Relation "md_fact_table" does not exist".
https://softwaresupport.hpe.com/km/KM02624620

I hope that this information is helpful.

Good Luck with your SOM environments.

Regards,

Mark

 

 

(SOM) Support Tip: Discovery process doesn't kick off.Open in a New Window

Hi SOM Community,

just a hint if the Discovery doesn't kick off and the log context might show old or no data (if logs rolled over) -
Main purpose seen for this issue so far, is that the you might have exceeded the number of licensed MAPs (Managed Access Points),
which prevents that a Discovery starts.
Before you raise a support case, please check in SOM the Consumed and License Capacity (MAPs).

To verify the License Consumption/Capacity press in the SOM UI:

a) Help -> About Storage Operations Operations Manager Software -> Licensing Information
or
b) Help -> System Information -> View Licensing Information

If the Consumption number is equal or higher than the Capacity number, a Discovery will fail without further notice (if the Instant-On License expired).

A word about Instant-On and License Extensions.

Recently many 'Proof of Concepts' (PoCs) with SOM have been started. Some of you might have already crossed the 60 Days for the
'Instant-On' License and might have received some additional License Extension from SOM Sales/Pre-Sales in order to do further testing with SOM.
The Instant-On License basically has an unlimited number of MAPs that can be used (even though the license page reports 250 Maps for the Instant-On License Capacity).
The Instant-On License cannot be extended and you might have received an additional Evaluation License that expires after some days. With this
additional Evaluation License, the MAPs really count and cannot be exceeded. There can be the situation that you e.g. consumed with the Instant-On license
already e.g. 3000 MAPs and the Evaluation License Extension provided by SOM Sales/Pre-Sales only covers e.g. 1500 Maps, which will prevent any
new Discovery or discovering existing Devices (Nodes) in SOM again.

Feel free to ask if you have questions regarding this topic.

Best Regards,
Dieter

 

(SOM) Support Tip: Reinstallation of Storage Operations Manager 10.20 might fail.Open in a New Window

Hello SOM Community,

today I'd like to share some recent findings (left-overs) when un-installing SOM and attempting to re-install SOM on the same system with a different customized installation path.

The “Storage Operations Manager Embedded DB Manager” service was never deleted or removed as part
of the uninstallation process.  The installation finds the service still present and does not modify or update it to the new location for the SOM binaries. The start of the service during the new setup fails because it is attempting to access binaries in the wrong location.

This issue appears to exist only on Windows.  A Knowlege Document (KCS) has been published that will help resolving the issue, so that the installation to the new location will be successful.

More details at the steps how to clean the system can be found at
https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM02613018

Best Regards and good luck with your SOM Environment

Dieter

 

 

AFTER INEGRATION SOM TOPOLOY DOSEN'T SYNC IN OMIOpen in a New Window

Hi,

We are using omi 10.12 on windows and SOM 10.20.201 on windows.

We fallowed all the integration steps as per guide and created the integration point. when we run "RUN ALL DADA SYNC"

It is connecting to the respective probe and after couple of minutes it shows status completed successfully.

When we check in RTSM of OMI we are not getting CIs from SOM.

Your immediate support will be highly appreciated.

Regards
Mohammed Tajammul Ahmed.

 

(SE) Support Tip: 3Par Remote Replication Information not captured by SEOpen in a New Window

Hello SE/SOM Community,

if SE fails to capture Remote Replication information from 3Par Arrays you might have to adjust the 'replica_entity'  policy setting in the 3Par CIM configuration.

The default policy setting is "replica_entity", which makes SE or SOM fail to capture Remote Replication information. In order to get this information into SE/SOM you  will have to re-configure the CIM of the 3Par Array(s).

- connect to the 3Par cli (e.g. via SSH)
- run the command

setcim -pol no_replica_entity

-Stop the CIM on the 3Par with the command

stopcim

-Start the CIM on the 3Par with the command

startcim

-Wait for ~5 min and then run a GAED (Get All Element Details) in SE, or a Data Collection in SOM against the 3Par

The Remote Replication information should then be available in SE/SOM.

Note: These steps are mentioned in the SOM Userguide, but can't be found in the SE Documentation.

 

Best Regards,
Dieter

 

 

(SOM) Support Tip: Netapp requires TLS (Transport Layer Security) to be turned onOpen in a New Window

Hi SOM Community,

if you experience 'Authentication Failures' (Bad Credentials) when attempting to discover a Netapp Device in SOM, you might have to verify if TLS is turned on at the Netapp Device. If TLS is turned off, SOM will throw an 'Authentication Failure' or you will find 'BAD Credentials' in the SOM Log files.

To verify the Netapp settings:

-connect to the CLI of the Netapp (e.g. via SSH)
-run the command
options tls
-if the output shows 'disabled' run the command
options tls.enable on

Now your Netapp Discovery should work.

Best Regards,

Dieter

 

 

 

 

SOM users creation and mapping are stored in any log file ?Open in a New Window

Dear Team,

Please let me know whether the user creation/modificatio/deletion details are stored in any log files of SOM.

I created one user account now with group mapping, but I have not seen this information in any logs.

And I see, a user account with "Global Operator" user group/role will have access to all topology objects, But this user is not able to login to SOM console.

 

SOM UI is slow, is it required to change java heap or jboss memory settings.Open in a New Window

Hello Team,

I am observing slowness when I shift from one tab to another tab or view in SOM UI.

Is it required to change any java heap settgins or jboss memory settings to speedup the nodes loading process.

I have just 1000 nodes in my environment.

 

 

Thanks, Hari

 

Normal Data collection over Performance data collectionOpen in a New Window

I need to understand difference between process of normal data collection and Performance data collection.

A normal data collection will run as per refresh interval varying 24 Hr to 72 hrs or more, but a performance data collection has to run way more frequestly to get proper matrics and to build representational graphs.

What processes are involved in Perf. Data collection and where logs are saved for this.

 

somdbmgr status shows up repeatedly while starting/stopping somjbossOpen in a New Window

What is the reason that while starting/stopping somjboss returns somdbmgr running status repeatdly before completing action.

C:\Program Files (x86)\HP\HP BTO Software\nonOV\Postgres\bin>ovstop -c somjboss
Name PID State Last Message(s)
somaction 7768 DONE Exited due to user request
somjboss 3344 DONE Exiting due to user request.
somdbmgr 1476 RUNNING Database available.
somdbmgr 1476 RUNNING Database available.
somdbmgr 1476 RUNNING Database available.
somdbmgr 1476 RUNNING Database available.
somjboss 3344 SENT_SIGTERM Timed out trying to stop. Now sendin
g SIGKILL(9).

 

Is it possible to auto delete the older Incidents from SOM consoleOpen in a New Window

Dear Team,

As the max. limit for the number of Incidents visisble in SOM UI is 10,000

Is it possible to auto delete/archieve the older Incidents(Ex: 2 months old) ?

Moreover, Is it possible to supress the "Data Collection successful" Incident(which is Normal Priority) and are not required to log daily.

 

Thanks,Hari

 

Any Alternative to BNA server for Brocade DiscoveryOpen in a New Window

Is there any alternative available to discover Brocade switches ?

What BNA server Edition is required ? (Professional ,Professional Plus , Enterprise edition)

BNA enterprise edition is the licensed version and it will add an extra cost to your SOM Implementation plan.

 

(SOM) Support Tip: Coexistance of SOM 10.20 and OA 12.xOpen in a New Window

Hello SOM Community,

Here's some important information in case you have OM/OMi within your environment and are using older versions of the Operations Agent (OA).

With SOM 10.20 it was made to be compatible with OA 12.x.  The challenge is that this process updates the version of Perl that is used.

While SOM 10.20 works with OA 12.x without any problems.  This is not the case with OA 11.x.

OA 11.x uses an older version of Perl.  If OA 11.x exists on the SOM management server before SOM 10.20 is installed, it will break it.   It has been seen to break certificate communications also.

We have been informed that the OA 12.x should be backwards compatible with the older OMi versions.  This has not been confirmed yet.

I hope that this information is helpful and can help avoid some challenges within your environments.

Good luck with your SOM environments.

Regards,

Mark

 

SOM 10.20 integration with uCMDB 10.22Open in a New Window

Hello Mark,

Could you please let me know whether SOM 10.20 integration is possible with uCMDB 10.22 ?

Also SOM 10.10 with uCMDB10.22 (I heard if ucmdb on CUP19 or 20 it is possbile)

 

 

Thanks, Hari

 

How to delete a Fabric entry in SOMOpen in a New Window

I am trying to delete all SAN switch related entry in SOM and re-discover from fresh.

I was able to delete all physical/virtual switch entries but there are so many fabric entries remained.

How to delete those fabrick entries , any other way to clean all Switch discovery data.

 

Cisco Switch Discovery in SOM 10.20Open in a New Window

Hi ,

Cisco Switch discovery has become nightmare for me.

I have arround 150 cisco switches to be discovered in SOM , I have Upgraded to 10.20 recently. I had run discovery of switces multiple time (8-9 minimum) but no switch turns up. All are getting failed stating " discovery didn't finish in 60 min".

Somehow running one by one each switch for arround 8-9 times some of them got discovered.

Is there any best practise to discover Cisco switches. How discovery happens if I select in bulk and start discovery ?

How to increase default time out value of 60 min ? Is there a option to auto re-run discovery for failed devices after a certain time. 

 

 

New Data Collection policy benifitsOpen in a New Window

Hello Community,

I have been using a default data collection policy to collect inventory data of storage elements(switches, 3PARs and HOsts) in my environment.

I didn't see any additional advantages by creating a NEW data collection policy.

Limited information related to data collection policies is mentioned in the SOM user's guide.

How do one's get benifited by creating a new data collection policy, Any suggestions please ?

 

 

Thanks,

Hari

 

(SOM) Support Tip: SOM Post-Installation fails with an error "No mapping between account names ..."Open in a New Window

Hello SOM Community,

There is a knowledge document that was recently created to address a problem with SOM Installations.

The problem occurs when SOM is attempting to be installed on a system that does not have a supported language.

According to the latest Support Matrix for SOM 10.20, the following languages are supported on the management server:
- French
- German
- Japanese
- Russian
- Simplified Chinese

If you are attempting to install SOM on a system with an unsupported language (Ex. Spanish or Italian),  you may encounter the following error within the som-install-config.txt log file:
...
!!  Create HP Storage Operations Manager Embedded Database
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Tuesday, September 6, 2016 3:59:40 PM CLT - INFO: The execution directory = C:\Program Files (x86)\HP\HP BTO Software\bin
Tuesday, September 6, 2016 3:59:40 PM CLT - INFO: Waiting (up to 600 seconds) for process to terminate
Tuesday, September 6, 2016 3:59:41 PM CLT - INFO: stderr> No mapping between account names and security IDs was done.
Tuesday, September 6, 2016 3:59:41 PM CLT - INFO: stderr>
...

This problem occurs due to the language issue.  The solution is to remove the software, set the server language and/or locale to a supported version and reinstall the software.

More information can be found within the following knowledge article.

KM02550702 - Storage Operations Manager Post-Installation fails with an error "No mapping between account names and security IDs was done."
https://softwaresupport.hpe.com/km/KM02550702

I hope that this information is helpful.

Good luck with your SOM environments and have a great weekend!

Regards,

Mark Butler

 

(SOM) Support Tip: SOM Data Collection Status is showing as 'Running' when it is not running.Open in a New Window

Hello SOM Community,

There is a knowledge article that was created recently to help with a strange situation that can occur with SOM 10.10 and earlier.

Storage Operations Manager (SOM) schedules Data Collections based on a data freshness duration.  It does not start at a specific time but may start at different times.

During normal maintenance windows SOM may be shutdown when a Data Collection is actively running.  This does not cause any problems with data consistency due to the use of a staging area that is used.  Only when the Data Collection is complete will the information be added to the SOM database.

If SOM 10.10 or earlier is stopped (Ex. ovstop) or the server rebooted when a Data Collection is running, the Data Collection status may still show as "Running" after the services are started again.  The Data Collection is not "Running' so this is not a correct status.

This is a known issue and it is corrected within SOM 10.20.

For SOM 10.10 or earlier, the issue is corrected by manually performing a data collection.  This will change the corresponding state associated with the Data Collection process for that specific element.

More information can be found within the following Knowledge Article:
KM02539940 - Storage Operations Manager Data Collection Status is showing as 'Running' when it is not running.
https://softwaresupport.hpe.com/km/KM02539940

I hope that this information is helpful.

Good luck with your SOM environments and have a great weekend!

Regards,

Mark Butler

 

SNMP traps display for more than one monthOpen in a New Window

Hello Support,

I have configured SNMP traps from 3PARs and switches in my environment, by default the traps are visible for the last one month.

Is it possible to display the traps of morethan one month in the "Incedents Browsing> SNMP Traps View" ?

 

 

Thanks,

Hari

Contact Us

Vivit Worldwide
P.O. Box 18510
Boulder, CO 80308

Email: info@vivit-worldwide.org

Mission

Vivit's mission is to serve
the Hewlett Packard
Enterprise User
Community through
Advocacy, Community,
and Education.