Getting false "DISK NO LONGER AVAILABLE" alarm upon monitoring RFC2790 File System

Document ID:  TEC1046929
Last Modified Date:  07/10/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Spectrum

Releases

  • CA Spectrum:Release:10.0
  • CA Spectrum:Release:10.1
  • CA Spectrum:Release:10.1.1
  • CA Spectrum:Release:10.1.2
  • CA Spectrum:Release:10.2
  • CA Spectrum:Release:10.2.1
  • CA Spectrum:Release:9.4
  • CA Spectrum:Release:9.4.1
  • CA Spectrum:Release:9.4.2
  • CA Spectrum:Release:9.4.2.1
  • CA Spectrum:Release:9.4.3

Components

  • DISCOVERY & MODELING:SPCDIS
Issue:

I am getting false "DISK NO LONGER AVAILABLE" alarm (Cause Code = 0xc40060) upon monitoring RFC2790 File System.

DiskNoLongerAvailable.png

The File System model that is getting the alarm is not offline. The target Server is a Linux machine running net-snmp and when I monitored the File System I have selected the "Alarm if offline" check box in File System Monitoring entry of System Resources -> File System -> Monitored File System (RFC2790) table.

Environment:
Spectrum 9.4.x, 10.x on all platforms. Net-SNMP on Linux machine
Cause:

OID 1.3.6.1.2.1.25.1.6 (hrSystemProcesses) is not accessible from the net-snmp database. Spectrum uses this OID to determine if the subAgent is down. For File System monitor to function correctly, net-snmp has to be configured to expose OID 1.3.6.1.2.1.25.1.6 (hrSystemProcesses).

Resolution:

Configure net-snmp to expose OID 1.3.6.1.2.1.25.1.6 (hrSystemProcesses). For example, below is less restrictive access net-snmp configuration (/etc/snmp/snmpd.conf) that will expose the OID. Please work with net-snmp Administrator to configure net-snmp properly that suits your company policy.

 

# -----------------------------------------------------------------------------
# Here is a commented out example configuration that allows less
# restrictive access.

# YOU SHOULD CHANGE THE "COMMUNITY" TOKEN BELOW TO A NEW KEYWORD ONLY
# KNOWN AT YOUR SITE.  YOU *MUST* CHANGE THE NETWORK TOKEN BELOW TO
# SOMETHING REFLECTING YOUR LOCAL NETWORK ADDRESS SPACE.

##       sec.name  source          community
com2sec local     localhost       public
com2sec mynetwork default      public

##     group.name sec.model  sec.name
group MyRWGroup  any        local
group MyROGroup  any        mynetwork

##           incl/excl subtree                          mask
view all    included  .1                               80

##                context sec.model sec.level prefix read   write  notif
access MyROGroup ""      any       noauth    0      all    none   none
access MyRWGroup ""      any       noauth    0      all    all    all

 

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >