Transcend

Transcend ® Network Control Services Diagnostics Tool This document contains important troubleshooting tips for Transcend Network Control Services for UNIX version 5.0 (NCS v5.0), Diagnostics Tool. The following sections are presented: s s s s What is the Transcend NCS/U v5.0 Diagnostics Tool? About the Transcend NCS/U v5.0 Diagnostics Tool Using the Transcend NCS/U v5.0 Diagnostics Tool Troubleshooting Transcend NCS/U v5.0 Backend Servers What is the Transcend NCS/U v5.0 Diagnostics Tool? The Transcend NCS/U v5.0 Diagnostics Tool allows you to determine the condition, availability, and system resources of Transcend NCS/U v5.0. To help you troubleshoot your system, the Diagnostics Tool enables you to: s Generate reports to determine the status of the Transcend NCS/U v5.0 system. Manage Transcend NCS/U v5.0 generated files. Manually start, stop, and restart server processes. Capture detailed information which can be sent to 3Com CSO for analysis. s s s 2 About the Transcend NCS/U v5.0 Diagnostics Tool The Transcend NCS/U v5.0 Diagnostics Tool enables you to monitor your Transcend NCS/U v5.0 system by generating diagnostic files which include log files and report files. The Diagnostics Tool records all user operations performed while using the tool, captures the output of Transcend NCS/U v5.0 server actions including start, stop, and restart, and creates a log file named /usr/3Com/log/diagnostics/diagnostics.log. The Diagnostics Tool also reports any diagnostic operations performed and appends the diagnostic reports to a default file named /usr/3Com/log/diagnostics/tncs_report.txt. The default report file name can be changed by accessing the File Admin menu. To run the Diagnostics Tool, enter the menu-driven command line shell script: /usr/3Com/diagnostics/tncs_dignostics.sh In order to execute the Transcend Diagnostics Tool, you must be a super user. If you are not a super user, contact your System Administrator. To view the contents of your report file as it is being generated, complete the following: 1 Open an xterm window. 2 Tail the output of the report file: tail -f /usr/3Com/log/diagnostics/tncs_report.txt Using the Transcend NCS/U v5.0 Diagnostics Tool 3 Using the Transcend NCS/U v5.0 Diagnostics Tool This section tells you how to use the Transcend NCS/U v5.0 Diagnostics Tool and the available options to diagnose your Transcend System. It contains the following sections: s s s s s Transcend NCS/U v5.0 Diagnostics Main Menu Transcend NCS/U v5.0 Server Admin Menu Transcend NCS/U v5.0 Servers Start/Stop/Restart Menu Transcend NCS/U v5.0 Diagnostics Report Menu Transcend NCS/U v5.0 File Admin Menu Transcend NCS/U v5.0 Diagnostics Main Menu The main menu of the Transcend NCS/U v5.0 Diagnostics Tool is organized to enable you to administer files, manage Transcend NCS/U v5.0 servers, and generate various reports. Menu Options Option 0 Option 1 Option 2 Option 3 Actions To quit Transcend Diagnostics main menu. To administer TNCS Servers. To generate TNCS diagnostic reports. To administer TNCS files. Transcend NCS/U v5.0 Server Admin Menu The Transcend NCS/U v5.0 Admin menu allows you to start, stop, and restart Transcend NCS/U v5.0 backend server processes. The server processes are categorized to determine the main functionalities of Transcend NCS/U v5.0. For detailed information on Transcend server categories, refer to “Troubleshooting Transcend NCS/U v5.0 Backend Servers”. Menu Options Option 0 Option 1 Option 2 Actions To return to the TNCS Diagnostics main menu. To start/stop/restart specific TNCS backend servers. To restart all TNCS Backend Servers. 4 CAUTION: To start Transcend NCS/U v5.0 servers as background processes on Solaris, you must use a job control shell such as /bin/csh, /bin/jsh, or /bin/ksh. If you have started the utility in a non-job control shell, you must exit the Transcend NCS/U v5.0 Diagnostics Tool before proceeding. The following options are available: Option 0 s Returns you to the Transcend NCS/U v5.0 Diagnostics main menu. Option 1 s Allows you to manually start, stop, and restart specific Transcend NCS/U v5.0 backend servers. Presents you with a list of Transcend NCS/U v5.0 servers to be individually managed. For a detailed server list, refer to the “Transcend NCS/U v5.0 Servers Start/Stop/Restart Menu”. The selected server status is verified. s s Option 2 s s Automatically stops and restarts all Transcend NCS/U v5.0 servers. The selected server status is verified. CAUTION: 3Com recommends choosing Option 1 because it allows you more control as to which server processes are started and stopped and aides you in correcting only those associated with the problem. Transcend NCS/U v5.0 Servers Start/Stop/Restart Menu The Transcend NCS/U v5.0 Servers Start/Stop/Restart menu displays the server categories. You can choose to start, stop, or restart any one of them. When you choose to stop or restart a server category, the Diagnostics Tool locates all other dependent servers and informs you of which ones will be affected. If there are any dependent servers present, the Diagnostics Tool will automatically stop those servers as well. For a detailed server dependency list, refer to “Troubleshooting Transcend NCS/U v5.0 Application Dependencies”. Using the Transcend NCS/U v5.0 Diagnostics Tool 5 Once a category is selected, the Transcend NCS/U v5.0 Diagnostics Tool verifies the status of all processes in the chosen category. Based on the current status of the process, a solution is recommended. Menu Options Option 0 Option 1 Option 2 Option 3 Option 4 Option 5 Option 6 Option 7 Option 8 Option 9 Option 10 Actions To return to the previous menu. TNCS Web Server TNCS Message Servers TNCS core CORBA services TNCS Sizing Servers TNCS VLAN Server TNCS Address Tracker Server TNCS Device View Server TNCS Event Manager Server TNCS Import Server TNCS StarTek Trap Manager The following is an example of a verification and recommendation for the Transcend NCS/U v5.0 Web Server: >>>>>Verifying status of TNCS Web Server>>>>> Please wait..... -- Process /usr/3Com/common/apache/bin/httpd has been verified to be running >>>>>>RECOMMENDATIONS FOR TNCS Web Server>>>>> Based on the server status verification, we recommend the following: The server processes are running as expected. You don't have to restart the TNCS Server >>>>>>>>>>>>>END OF RECOMMENDATIONS>>>>>>>>>>> 6 Transcend NCS/U v5.0 Servers Start/Stop/Restart sub-menu Menu Options Option 0 Option 1 Option 2 Option 3 Actions To return to the TNCS Diagnostics main menu. To return to the start/stop/restart menu. To start TNCS (chosen) Server. To restart TNCS (chosen) Server. The following options are available for any server category being managed: Option 0 s Returns you to the Transcend NCS/U v5.0 Diagnostics main menu. Option 1 s Allows you to manually start the server. NOTE: Make sure you start the dependent core servers. For a detailed server dependency list, refer to “Troubleshooting Transcend NCS/U v5.0 Application Dependencies”. Option 2 s Allows you to manually stop all servers and restart them at a later date. NOTE: During the stop process, the Diagnostics Tool detects all dependencies and prompts you to confirm all related servers you wish to stop. After this operation you must use the start option to restart the servers. Option 3 s Allows you to manually restart the chosen server. This option automatically detects all dependencies. It will first stop the dependent servers followed by the server itself. Upon restart, it will start the server followed by the dependent servers. Using the Transcend NCS/U v5.0 Diagnostics Tool 7 Transcend NCS/U v5.0 Diagnostics Report Menu The Transcend NCS/U v5.0 Diagnostics Report menu allows you to create various reports that can be used to troubleshoot Transcend NCS/U v5.0 applications. All reports are appended by default to /usr/3Com/log/temweb/diagnostics/tncs_report.txt. Menu Options Option 0 Option 1 Option 2 Option 3 Option 4 Actions To return to the TNCS Diagnostics main menu. To generate a report of all TNCS Backend Server Status. To generate TNCS diagnostic reports. To generate a report of your current TNCS Station System Configuration. To generate a complete TNCS report. The following options are available: Option 0 s Returns you to the Transcend NCS/U v5.0 Diagnostics main menu. Option 1 s s Confirms server processes under each server category. Verifies and reports the current status of each process under the server category. Determines if an optional server is installed on your system and reports the server status. s Option 2 s Displays Web server configuration information including port number and server name to the report file. Reports the current Transcend NCS/U v5.0 Web security status. Determines if Transcend Web applications are configured correctly. s s 8 Option 3 s Generates a comparison report of your current system kernel configuration with the recommended configuration. Reports current disk availability under /usr/3Com directory. s Option 4 s Creates a combination of all available reports. This can be used periodically to verify the system status. Generates a detailed report to be sent to 3Com CSO for analysis. s This report will automatically be generated by the Diagnostics Tool when you choose Option 3 from the Transcend NCS/U v5.0 File Admin Menu. Transcend NCS/U v5.0 File Admin Menu Menu Options Option 0 Option 1 Option 2 The Transcend NCS/U v5.0 File Admin menu allows you to manage all files, including diagnostic report files. Actions To change TNCS Diagnostics report file. To manage TNCS log files. To gather diagnostic information in a file to be sent to 3Com CSO for analysis. The following options are available: Option 0 s Allows you to change the default diagnostic report file name. This report file name can be changed at anytime while the Diagnostics Tool is in operation. Option 1 s Enables you to manage Transcend NCS/U v5.0 log files. This includes performing regular backups or periodically regulating the size of the log files in order to save disk space under the Transcend NCS/U v5.0 directory. Manages all files located under /usr/3Com/log directory. s Troubleshooting Transcend NCS/U v5.0 Backend Servers 9 Option 2 s Automatically generates a default report, /usr/3Com/log/diagnostics/tncs_report.txt, used for troubleshooting purposes and gathers all files and directories specified in /usr/3Com/diagnostics/tncs_archives.lst. s Archives all required files under Transcend as tncs_logs.tar which are saved in a user specified directory to be evaluated by 3Com CSO. Allows you to add additional directory names or individual file names to be shipped to 3Com along with the required diagnostics file. This is done by editing /usr/3Com/diagnostics/tncs_achive.lst. s Troubleshooting Transcend NCS/U v5.0 Backend Servers This section contains troubleshooting information about Transcend NCS/U v5.0 backend servers and describes the different functional categories which enable you to: s s s s Determine which severs are not functioning properly. Monitor process groups which together provide functionality. Identify dependencies between Core Servers and Application Servers. Identify dependencies between different Application Servers. 10 Transcend NCS/U v5.0 Server Categories When you verify, start, stop, or restart a server category, the Diagnostics Tool performs a requested action on certain processes. The following table identifies Transcend NCS/U v5.0 (TNCS) Server Categories and their corresponding process as defined for diagnostic purposes. Process /usr/3Com/common/apache/bin/httpd /usr/3Com/common/rv/bin/rva rvd -listen /usr/3Com/common/vbroker/bin/osagent /usr/3Com/common/vbroker/bin/oad vbroker.gatekeeper.GateKeeper. /usr/3Com/common/sizing/bin/timer /usr/3Com/common/sizing/bin/defsize /usr/3Com/common/sizing/bin/dispatcher medp pdp atservice /usr/3Com/dv/srvlnch /usr/3Com/db/cdbimp/cdbimp_server /usr/3Com/common/activator/activator /usr/3Com/temweb/cgi-bin/all/eventManager/eventServer /usr/3Com/startek/bin/TrTrapMgr.scr TNCS Server Category TNCS Web Server TNCS Core Message Servers TNCS Core CORBA Services TNCS Sizing Servers TNCS VLAN Server TNCS Address Tracker Server TNCS Device View Server TNCS Import Server TNCS Event Manager Server TNCS Token Ring Trap Manager Troubleshooting Transcend NCS/U v5.0 Application Dependencies This section contains troubleshooting information regarding Transcend NCS/U v5.0 application dependencies with core Transcend NCS/U v5.0 servers and the various severs that are affected by operational difficulties. It contains the following sections: s s Transcend NCS/U v5.0 Core Servers Transcend NCS Application Servers Troubleshooting Transcend NCS/U v5.0 Application Dependencies 11 Transcend NCS/U v5.0 Core Servers The following table lists the core Transcend NCS/U v5.0 servers and the dependent application servers. A brief description of possible consequences that may occur when the server is not running is described. Transcend NCS Core Server Category Dependent Application Servers Consequences TNCS Web Server None s Unable to connect to Transcend Web Home Page. Unable to launch web applications from Transcend Central. Event Manager server will crash upon start. Event Manager client will start, but not work. NOTE: From the client, you are unable to see that the server is not running. s TNCS Core Message Servers Event Manager Servers s s s Status Watch is unable to send events to Event Manager because the API will have failed. VLAN MAnager is unable to send events to Event Manager because the VLAN MAnager script will have failed. If the COBRA servers are not running or not responding but running, an error message “Cannot talk to server” is displayed by the Transcend Central client. NOTE: COBRA servers are used by the central server to initially bind and establish a connection. This occurs for every central client that is started. s TNCS Core CORBA Services Transcend Central, Sizing, and Import Servers s s If CORBA fails and sizing logging is enabled, sizing processes will log error messages when attempting to register with the ORB or send a message to another sizing module. If logging is disabled, there is no direct user output from sizing. Client applications may display an appropriate message when they fail to contact the sizing Dispatcher. Sizing logging is disabled by default. 12 Transcend NCS Application Servers The following table provides a brief description of the dependencies between various Transcend NCS/U v5.0 application servers and the behavior of client applications as a result of inoperational servers. Dependent Servers and Transcend NCS Applications Event Manager Server Consequences Transcend NCS Application Server Category Activator s s Communication from event manager client to server will fail to initiate. Status Watch will be unable to send events to Event Manager because the API will have failed. Enterprise VLAN Manager will be unable to send events to Event Manager because the Enterprise VLAN Manager script will have failed. Address Tracker will warn you if the server process is not running. NOTE: You must not have multiple instances of atservice running on your system. If multiple services are running, kill all instances of atservice manually and restart the Address Tracker Server using the Diagnostics Tool. Event Manager s s Enterprise VLAN Manager Status Watch Applications s s Address Tracker s Device View Server s Platform Helper s If Platform helper is not running, the Device View server will fail to access the write community string for the device.The read community string public will be used as the default. Troubleshooting Transcend NCS/U v5.0 Application Dependencies 13 Sizing Servers s s s Transcend Central Upgrade Manager Import Server s If sizing dispatcher fails, clients receive a CORBA exception. Transcend Central displays a message "Unable to contact sizing". If the Timer fails, there is no visible symptom except that periodic automatic sizing does not occur. If defsize, startek, or eclipse fail, the client application (Transcend Central or Upgrade Manager) receive an error return status to their sizing request. In Transcend Central, the corresponding device icon turns red. NOTE: The device specific sizing daemons are on-demand. They will not be running at all times, unless a request for sizing such a device has occurred. s s Import Server s s Platform Helper Transcend Central s From Transcend Central, you cannot import devices from a file into the Transcend data repository. From Transcend Central, you cannot import devices from the open management platform into the Transcend data repository. From Transcend Central, you cannot synchronize community strings between the open management platform and the Transcend data repository. s s Enterprise VLAN Servers VLAN Manager client will warn you if the server process is not running. 14