Re: Minor Alarm, NNMi 9.1, Windows Server (705 Views)
Reply
Advisor
Posts: 34
Registered: ‎10-22-2012
Message 1 of 6 (731 Views)

Minor Alarm, NNMi 9.1, Windows Server

Hello,

 

   Recently, my primary NNMi Node Manager server went down, and it failed over to the secondary or backup server. My primary server has now been down for an extended period fo time, and I got the following errors on my secondary server:

 

[Minor]  The Performance SPI Custom Poller Bus Adapter has status Minor because the file space limit (1,000 megabytes) has been reached and no additional data can be written.

[Minor]  The Performance SPI Bus Adapter has status Minor because the file space limit (1,000 megabytes) has been reached and no additional data can be written.

 

I never had this happen on my Primary server, but it seems like it stopped writing Performance Data to the Performance server for some kind of limit? Any way to adjust those limits?

 

Thanks.

Highlighted
Respected Contributor
Posts: 301
Registered: ‎12-11-2011
Message 2 of 6 (705 Views)

Re: Minor Alarm, NNMi 9.1, Windows Server

Hello , 

 

 

This Issue related to HP NNM ISPI Performance Metric , 

 

The Error Means that NNM has Collected Many Performance Data , and NPS didn't poll them to the DB , 

 

please check the shared Directory from NNM Side and NPS as well 

 

From this Secenario , i guess you have NNM application failover not NNM Cluster !!

 

But Again , this error not related to Primary NNM went down for long > it's ISPI Issue .

 

Check the Shared Directory 

Check Status on ISPI ,statusALL.ovpl 

 

 

 

All the best .
Saying Thanks by hitting Kudos :)

Regards
Mostafa Hassan
HP AIS NNM-NA-OO
CCNA-CCNP-ITIL-VCA-Cloud-VCA DataCenter
Advisor
Posts: 20
Registered: ‎04-13-2015
Message 3 of 6 (160 Views)

Re: Minor Alarm, NNMi 9.1, Windows Server

hi Mostafa_Hasan,

 

i've also face this,

 

[Minor]     The Performance SPI Custom Poller Bus Adapter has status Minor because the file space limit (1,000 megabytes) has been reached and no additional data can be written.

 

i've already do housekeeping for the data and now it working normally, but the minor status still there.

can you give me a clue about this?

 

here's the detail history about this

 History:
    [2015-07-22 03:17:02.075] 'SNMP Health Agent' has initialized with status 'Normal'
    [2015-07-22 03:17:02.075] 'Service Health Agent' has initialized with status 'Critical'
    [2015-07-22 03:17:02.075] 'Trap Server' has initialized with status 'Normal'
    [2015-07-22 03:17:02.075] 'UI Servlet Response' has initialized with status 'Normal'
    [2015-07-22 03:17:02.075] 'UI Servlet Sessions' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'CRL Manager Health Agent' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'Causal Engine Health Agent' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'CustomPoller' has initialized with status 'Minor'
    [2015-07-22 03:22:04.117] 'Database Pool' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'Disco Health Agent' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'Disk Usage' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'Events Health Agent' has changed status from 'Major' to 'Normal'
    [2015-07-22 03:22:04.117] 'Global Network Management' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'Messaging System' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'NNMi CPU' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'PostgreSQL' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'Service Health Agent' has changed status from 'Critical' to 'Normal'
    [2015-07-22 03:22:04.117] 'StatePoller' has initialized with status 'Minor'
    [2015-07-22 03:22:04.117] 'System Resources' has initialized with status 'Normal'
    [2015-07-22 03:22:04.117] 'Topology' has initialized with status 'Normal'
Honored Contributor
Posts: 1,423
Registered: ‎04-19-2011
Message 4 of 6 (142 Views)

Re: Minor Alarm, NNMi 9.1, Windows Server

Hi

 

Check this,

 

1.  dbsize.ovpl run in NPS, will show the database is full in NPS and hence NPS will not pull latest data.

 

2.  File sizes in  NNM shared final directory will be huge and NPS ETL process will not be able to pull the data.

 

3.  NFS share between NPS and NNM will not be present because of NFS service not running in
      NNM or NPS.( Can be found by running df -h  in Linux  or its equivalent)

Advisor
Posts: 20
Registered: ‎04-13-2015
Message 5 of 6 (127 Views)

Re: Minor Alarm, NNMi 9.1, Windows Server

hi Ramesh,

 

thanks for your advice, now its working 

here's what i do : 

 

  • Stop etl process on ISPI side with command “stopall.ovpl”
  • edit the following two lines in the %nnmdatadir%/NNMPerformanceSPI/database/perfspi.cfg file:
    -iqmc 2805
    -iqtc 2805
    To:
    -iqmc 1350
    -iqtc 7650
  • then start etl process again with command “startall.ovpl”
Honored Contributor
Posts: 1,423
Registered: ‎04-19-2011
Message 6 of 6 (104 Views)

Re: Minor Alarm, NNMi 9.1, Windows Server

Hi

 

Please let us know why you had decreased SYBASE IQ CACHE parameters?

 

Was it reduced based on feedback from HP support?

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.