Medical Archive Solutions User Guide

185
HP Medical Archive
Troubleshooting Alarms
NNMS Number of NMSs the device is connected
to.
Connections to the NMS do not affect
client functionality, but do affect your
ability to properly monitor the system.
If there is no connection to an
NMS, check the network connec-
tions and whether both servers
and services are available. If this is
not a hardware related issue and
the problem persists, contact HP
technical support.
NSCA NMS Device Status; indicates the general
status of the NMS service:
0=No errors
1 = DB Connectivity Error
If the service indicates “DB Con-
nectivity Error, restart the
service. If the problem persists,
contact HP technical support.
NSCE NMS Device State; whether the device is:
0 = Offline
1=Standby
2=Online
If the device goes into “Standby”,
continue monitoring and if the
problem persists, contact HP tech-
nical support.
If the device goes into “Offline”
and there are no known server
hardware issues (server
unplugged) or a scheduled
downtime for the device, contact
HP technical support.
NTBR Remaining Database Space; the number
of bytes remaining in the allocated
database for NMS attribute data.
Adjusting the alarm threshold allows you
to proactively manage when additional
storage needs to be allocated.
If the available space is reaching a
low threshold, you should contact
HP technical support to arrange
for the database allocation to be
enlarged.
OCOR Objects Corrupt; the number of objects
stored on this LDR that have been
detected as potentially corrupt and need
to be investigated.
Any corrupt objects are worthy of investi-
gation. More than 10 indicates a critical
problem.
If there are several corrupt objects
identified, contact HP technical
support.
After the underlying problem is
resolved, use the Configuration
tab to clear the alarm. See
page 165.
Attr.
Code
Description Recommended Action