Alcatel-Lucent 5620 - Page 265

10 — Troubleshooting 5620 SAM server issues
Alcatel-Lucent 5620 Service Aware Manager, Release 10-3
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
iii If the 5620 SAM main server is installed on Windows, enter the following at
the CLI prompt:
path\nms\bin\nmsserver.bat appserver_status ↵
where
path is the 5620 SAM server installation location, typically C:\5620sam\server
The general 5620 SAM server application status is displayed.
iv If the 5620 SAM main server is installed on Windows, enter the following at
the CLI prompt:
path\nms\bin\nmsserver.bat nms_status ↵
where
path is the 5620 SAM server installation location, typically C:\5620sam\server
Detailed 5620 SAM server information is displayed.
v To obtain more specific server status information, run the nmsserver script
in step 3 using the appropriate option from Table 10-1 in place of the
nms_status or appserver_status option.
Table 10-1 5620 SAM main-server startup script options
Option Description
start Starts the 5620 SAM main server in noninteractive mode on a Solaris
workstation or in interactive mode on a Windows PC
stop Stops the 5620 SAM main server
appserver_status Returns information about the status of the 5620 SAM main server (both
active and standby servers when the 5620 SAM is configured for
redundancy)
appserver_version Returns build information, including the start date of the current
instance of the 5620 SAM main server
nms_status Returns the following information:
• 5620 SAM standalone, primary, or standby server start time and
running time
• total used and available memory
• database connectivity status
• redundancy configuration and status
• 5620 SAM license information
• JVM memory-usage information
• alarm forwarding information
• basic auxiliary server information
• number and status of current process threads
-v nms_status Verbose version of the nms_status option that returns the following
additional information:
• ID and status of the current process threads
• general JMS server information
• currently connected JMS subscribers, by topic
(1 of 2)
Aug 2010
AAAD
8.0 R4