ACS SPiiPlusSC Troubleshooting
troubleshot 意思
troubleshot 意思英文回答：Troubleshooting is a systematic process of identifying and resolving the root cause of a problem. It involves gathering information, analyzing symptoms, and testing potential solutions. Troubleshooting is an essential skill for problem-solvers and technicians in various fields, such as computer science, engineering, and customer service. The goal of troubleshooting is to identify the underlying cause of the issue and implement a solution that prevents the problem from recurring.Depending on the complexity of the problem, troubleshooting can be a challenging task. It requires a combination of technical knowledge, analytical skills, and perseverance. Successful troubleshooting often involvestrial and error, where different solutions are tested and discarded until the root cause is found and resolved.To approach troubleshooting effectively, it is important to follow a structured process. This typically involves:1. Identifying the problem: Clearly define the issue and gather as much information as possible about its symptoms and behavior.2. Gathering data: Collect relevant information to help identify the source of the problem. This may include system logs, error messages, or user observations.3. Analyzing the evidence: Review the gathered data to identify potential causes and rule out unlikely ones. This step involves logical reasoning and hypothesis testing.4. Developing a solution: Formulate a plan to resolve the problem based on the analysis. This solution should be tailored to the specific issue and its underlying cause.5. Testing the solution: Implement the solution and verify if it resolves the problem. This may involve testingthe system or monitoring its behavior after the solution is applied.6. Documenting the solution: Once the problem is resolved, document the steps taken and the solution implemented. This helps prevent similar issues from recurring and facilitates knowledge sharing.Effective troubleshooting requires a systematic approach, attention to detail, and a willingness to explore different solutions. By following a structured process and leveraging technical expertise, professionals can effectively resolve problems and maintain optimal system performance.中文回答：故障排除是指识别和解决问题根源的系统流程。
rs232通讯简明调试说明.
4.3Serial RS-232/422 CommunicationAll SPiiPlus motion control products include two serial communication channels (COM):❑RS-232❑RS-422The default settings of RS-232 and RS-422 are: 8 data bits, no parity and a regurlar stop bit.1.Open MMI ♑ Communication and select Serial.Figure 7SPiiPlus MMI Communication Dialog - Serial2.Specify the host computer serial Port (COM1, COM2, etc.) that is connected to thecontroller.3.The Rate of the host port, which is set here, must match that of the controller port to whichit is connected. Normally, this can be done by selecting Auto, which automatically detects the controller rate. (The controller rate can be accessed in MMI ♑ Configurator♑Communication Parameters.)4.Click Connect to establish the communication channel with the SPiiPlus serial port.5.Click Close to exit the Communication dialog box.4.3.1Troubleshooting a Serial Connection❑Inspect the cable and connectors.❑If a communication error message appears right after you click Connect, check that the COM port on the PC host is not being used by another application.❑Check that the communication port specified in the Port field corresponds to the COM port on the PC host that the cable is connected to.❑Older computers: try a lower baud rate.。
Simple Troubleshooting
Simple Troubleshooting1. Functional issue:(1) PCI/PCI-e serial products- Install issueA. Please check if the driver has been properly installed in device manager and theninstall the APB. Please unplug device and then remove AP & Driver completely.C. Please re-plug the device in another PCI/PCI-e slotD. Please go to our website and download the latest web version, then reinstall.- Video & Audio issueA. Please help user to check if the signal strength in user’s side is in good stateB. Please check if country & Region setting in our AP is set correctly.C. Please ask users to upgrade VGA & Sound card driver to the latest version.D. Please re-plug the device into another PCI/PCI-e slot.(2) BOX serial products- Video & Audio issueA. Please check if user’s connection is correctly done or not.For DVI box, please make sure users connect the same interface between input and output. For example, connect the DVI-input and need to connect DVI-out to monitor.Audio connection: please check that user has plugged in the “speaker audio cable”to DVI Box audio-out. If using the same speaker between PC and our box, pleaseplug the audio cable to audio-out at PC and audio-in at box, then connect speakeraudio cable to DVI Box audio out.Video connection: If using the same monitor, please connect VGA/DVI-out at PC to VGA/DVI-in at BOX and VGA/DVI-out to monitor.For non-DVI box, please make sure user doesn’t connect the DVI cable in the monitorB. Please check signal source is right, EX. S-video, Composite or TV turnerC. Please check country/Region setting is correctlyD. Please make sure the resolution between PC and BOX is the sameE. Please change monitor refresh rate to see if any differenceF. Please return to default setting- Get the white and black in video for BoxA. Click the Menu on your remote → 4.More… → Country/Region → selects the local areaB. Click the Menu on your remote → 4. More… → DefaultC. Click the Menu on your remote → select TV source → selects the CATVD. Click the Menu on your remote → select the CH scan → run the CH scan- How to set the resolution for BoxClick the Menu on your remote → 4.More…→ Select the resolution as you want as below 640*480800*6001024*7681280*10241280*768 (item 5) => 16:91680*10501920*1200- Box related information about transformer, resolution and refresh rate support Pname Pmodel no. Transformer Screen AreaHOTCHA M0A6 9V DC 0.6A 640*480 Joy TV 1 / 2 / 3 M0A1 7.5V DC 1A 640*480 TV BOX3 M0B6 12V DC 0.6A 1280*1024 AVerTV Box7 Live M0B0 12V DC 0.6A 1280*1024AVerTV BoxW7 M0B0 12V DC 0.6A 1440*900AVerTV BoxW9 M0B9M0BA12V DC 1A 1440*900DVB-T STB3 A210 12V DC 1A 1280*1024 DVB-T STB5 A212 12V DC 1A 640*480 DVB-T STB7 A212 12V DC 1A 1280*1024 AVerTV DVI Box7 M099 5V DC 2A 1920*1200 AVerTV DVI Box9 M099 5V DC 2A 1920*1200 AVerTV DVI Box 1080i M099 5V DC 3A 1920*1200 AVerTV BoxW7 Super M079 5V DC 1A 1440*900 AVerTV Box Genie l M075 5V DC 1A 1680*1050 AVerTV BoxW7 Lite M097 5V DC 1A 1920*1200(3)USB serial products:- Install issueA. Please check driver is installed properly in device manager, and then install the APB. Please unplug device and then remove the AP & Driver completely.C. Please re-plug the device in another USB portD. Please make sure user’s port is USB 2.0 at device manager.You can check your USB port under Universal Serial Bus controller of Device Manager. If It's USB 2.0, then you can find out the wording of "Enhanced or USB2.0" in this item.List the AVerMedia products support USB 1.1 as below: C030, M008, M068, E800 and A800.E. Please go to our website to download the newest web version to reinstall.- Video & Audio issueA. Please help user check the signal strength in user’s side is in good state or notB. Please check the country & Region setting in our AP is correctly done.C. Please ask users to upgrade VGA & Sound card driver to latest version.D. Please re-plug the device into another USB 2.0 port.(4)Cardbus & Express Card serial products:- There is no video or audio in analog TV for Cardbus products★ Important! This requires PCMCIA slot that supplies 1A standard power output.For any Cardbus “no video or audio in analog TV issue” we suggest ask user contact Local distributor/dealer to swap to the other products or return if meets the return policy.- Install issueA. Please check that driver is installed properly in device manager, and then install theAPB. Please unplug device and then remove the AP & Driver completely.C. Please re-plug the device and install the latest version in our website- Video & Audio issueA. Please help user to check the signal strength in user’s side is good enough.B. Please check the country & Region setting in our AP is set correctly.C. Please ask users to upgrade VGA & Sound card driver to the latest version.2. Go to test or repair process:List our products warranty as below:ProductStandard WarrantyRemarksWhere to Repair?All Products (except potable LCDTV)2 years(May vary by territory)All AVerMedia products purchased after Oct, 1st , 2004will be carried 2 year limited warranty services. One year limited warranty is given to purchase made prior to this date.Warranty void for user removing serial numbersticker on the product.Please contact your resellerNotice of warranty:If the AVerMedia product was supplied as part of a system, it is not covered by the AVerMedia warranty procedure. Please contact your system builder.Warranty period may be differing by regionally; please kindly check with your point of purchase. Warranty invalid if damage/dysfunction caused by improper handling/usage, destruction.Warranty invalid if system has been disassembled by end-user or non-AVerMedia-authorized repair centers.Warranty extension or special warranty package bought at point of purchase is not reflected in this chart.The warranty period do not apply to accessories.One year Limited Warranty is adopted for remote controller and power adapter.。
CitrixTroubleShootingTips
CitrixTroubleShootingTipsSupport ForumBasic Trouble Shooting TipsFollowing are a few basic trouble shooting tips to help in diagnosing problems with your Citrix environment. Usually these are some of the initial questions a support engineer may ask if you call in.LicensingMost problems are related to Citrix and Microsoft licensing issues. First, verify that the server is running in Application Server mode not Remote Administration. Second, check that the Terminal services licensing server is running and that licenses are activated. Third, check the Citrix licensing server that the correct amount of licenses are installed. Fourth, establish a Remote Desktop Connection using both an administrator account and a regular domain users account.No Terminal Server Licenses when attempting RDP to server from client workstation: Delete HKLM\software\microsoft\mslicensing\store\license000 registry keyIMA ServiceVerify the IMA service is started and running in Services. Check that the service is live by doing a telnet on port 1494. For example: telnet 127.0.0.1 1494If the service is answering, you will see ICA? repeat continuously.FirewallTCP port 1494 needs to be open for external users to connect using the standard Citrix client. Though not necessary, having TCP port 3389 open for Terminal services may help to isolate problems in the trouble shooting process. Additionally, to support session reliability with Presentation Server 4.0 or later, TCP port 2598 should be open.Create Web Interface not an optionIf when running Access Suite Console for Presentation Server 4.0 and the option to Create a web interface is not present, the most likely cause is that Microsoft .NET Framework 2.0 is installed. The resolution is either to un-install .NET Framework or to add the following file in C:\Windows\System32\mmc.exe.config<?xml version ="1.0"?><configuration><startup><requiredRuntime version="v1.1.4322"/><supportedRuntime version="v1.1.4322"/></startup></configuration>Remove this file if upgrading to Citrix 4.5 Access Management ConsoleChanging XML service portHow to change the XML service port used by Citrix Presentation Server:1. Go to a command prompt2. Type ctxxmlss /u and press ENTER (this will unregister the XML service)3. Stop the Citrix XML Service in the Services in Windows Services4. Type ctxxmlss /rnnn and press ENTER (for example to change the port to 8080 type ctxxmlss /r8080)5. Refresh services and start the Citrix XML Service in the Services in Windows Services6. Type telnet localhost 8080 and press ENTER twice (instead of 8080 use the port # specified in step 3)HTTP/1.1 400 Bad requestServer: Citrix Web PN ServerDate: Tue, 16 Oct 2005 14:02:41 GMTConnection: CloseConnection to host lost.Web Interface unable to loginThe supplied credentials could not be validated. Either they are incorrect, or there is a problem with the authentication system. Try again, or contact your help desk or system administrator for help.1. Type telnet localhost 80 and press ENTER twice (instead of 80 use the XML service port number)If output similar to the following appears, then the XML service is running correctly:HTTP/1.1 400 Bad requestServer: Citrix Web PN ServerDate: Tue, 16 Oct 2005 14:02:41 GMTConnection: CloseConnection to host lost.Otherwise, consider changing the XML service port for the Presentation Server and reconfigure the XML port in the Manage Server Farms module of the Web Interface configuration management console.Secure Ticket AuthorityHow to verify the Citrix secure ticket authority (STA) is running correctly:Enter the following into a web browser running on the Presentation Serverhttp://localhost:port/ctxsta.dll or http://localhost:port/scripts/ctxsta.dllhttp://localhost:8080/ctxsta.dll (this example is if the XML service is running on port 8080)If the test is successful, the output will be a blank screen or say Error 405 - resource not allowed.If the test fails, then the output will most likely be a 404 Error (The page cannot bedisplayed)Web Interface Client DownloadHow to add a link to Web Interface 4.5.1 or higher to download a Citrix client from the local webserver:Edit WebInterface.conf on Web Interface server:Generally: C:\Inetpub\wwwroot\Citrix\AccessPlatform\conf or C:\Inetpub\wwwroot\Citrix\XenApp\confEdit Win32Client=DefaultVer 4.x: Win32Client=Citrix Windows Client Download&/Citrix/AccessPlatForm/Clients/ica32web.msiCopy ica32web.msi to C:\Inetpub\wwwroot\Citrix\AccessPlatform\Clients\If running Web Interface 4.x and a Citrix client is not detected, the main page will display thedownload link.Edit Win32Client=DefaultVer 4.x: Win32Client=Citrix Windows Client Download&/clients/OnlinePlugin.exe# This will download version 12 client from Citrix Nerds websiteVer 5.x: Win32Client=Citrix Windows Client Download&/Citrix/XenApp/Clients/XenAppWeb.msiCopy XenAppWeb.msi to C:\Inetpub\wwwroot\Citrix\XenApp\Clients\*Files are located in the \clients\ica32\ folder on the Citrix Components CDFor Web Interface 5.x a redirect to a download page will occur.XenApp 6: Edit C:\Inetpub\wwwroot\Citrix\XenApp\conf\WebInterface.conf# ClientDefaultURL=/download - Unremark this line and add correct URLClientDefaultURL=/common_clientsCopy Citrix Receiver and Plug-ins from installation media to C:\Program Files (x86)\Citrix\Web Interface\5.3.0\Clients\# ClientIcaMac=Filename:Citrix online plug-in (web).dmg,Directory:Mac,Mui:Yes#ClientIcaWin32=Filename:CitrixOnlinePluginWeb.exe,Directory:Windows,Mui:Yes,ClassID :238f6f83-b8b4-11cf-8771-00a024541ee3#ClientStreamingWin32=Filename:CitrixOfflinePlugin.exe,Directory:Windows,Mui:Yes,Class ID:4384F3C5-4A9E-4E81-9AAE-4251C2813861If filenames need to be modified, then edit the above lines for MAC and WindowsOnline/Offline clientsProgram Neighborhood AgentHow to verify the Citrix Program Neighborhood Agent is running correctly:Enter the following into a web browser running on the Presentation Serverhttp://localhost/Citrix/PNAgent/config.xmlIf output similar to the following appears, then the PNAgent is running correctly:<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE PNAgent_Configuration (View Source for full doctype...)>- <PNAgent_Configuration xmlns:xsi="/2000/10/XMLSchema-instance">How to securely access PNagent from the Internet using SSL:In the \inetpub\wwwroot\Citrix\PNAgent\conf folder edit the WebInterface.conf file AlternateAddress=OnCitrix Web Interface 5.x compatibility with legacy editions of Presentation Server or MetaframeXPEdit webinterface.conf changing RequireLaunchReference=on to offFor Xenapp : c:\intetpub\wwwroot\citrix enapp\confFor PNAgent : c:\inetpub\wwwroot\citrix\pnagent\confForce Uninstall Citrix Presentation ServerIf the Citrix IMA service is not started and you want to uninstall Citrix do the following:1. Go to a command prompt and change to the installation files directory on the installation media or CD2. cd\Citrix Presentation Server3. Type msiexec /x mps.msi CTX_MF_FORCE_SUBSYSTEM_UNINSTALL=Yes and press ENTEROnly administrators have permission to add, remove, or configure server software during a terminal services remote sessionAdd the following registry key:Key: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\InstallerName: EnableAdminTSRemoteType: DWORDValue: 1Please provide a valid server installation type on the command line when executing the MSI or use Autorun to execute the installation insteadIn XenApp for Windows 2008, there is no longer a default installation typeSet the CTX_MF_SERVER_TYPE property regardless of what type of installation you are performingExample: msiexec.exe /i mps.msi CTX_MF_SERVER_TYPE="P"P = Platinum, E = Enterprise, A = AdvancedThin Client Intermittent Connection Dropping - Checksum OffloadingIf you experience intermittent communication failure between Thin Client devices and Windows 2003 Server Terminal Services (RDP) and/or Citrix (ICA):1. Click Start, click Run, type regedit, and then click OK.2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters3. In the right pane, make sure that the DisableT askOffload registry entry exists. If this entry does not exist, follow these steps to add the entry:a. On the Edit menu, point to New, and then click DWORD Value.b. Type DisableT askOffload, and then press ENTER.4. Click DisableT askOffload.5. On the Edit menu, click Modify.6. Type 1 in the Value data box, and then press ENTER.7. Exit Registry Editor.Ref: Microsoft KB904946* This problem may occur with certain Dell Servers specifically designed for virtualization that come with Citrix XenTools pre-installedThe server was unable to allocate from the system nonpaged pool because the pool was emptyWindows 2003 Server Enterprise 32bit running more than 4GB RAM. Collecting pooltag data using Pool Monitor indicates a large amount of non-paged pool memory in the ICA Pool tag. If servers are rebooted on daily basis this issue has a lesser likelihood of occurring.Citrix CTX230540 post R06 hotfix PSE450R06W2K3035 - January 12, 2011 addresses this issue.Best Practices Printer Policy1. Start the Citrix Presentation Server Console2. Right click on Policies, click create policy, enter a policy name and click OK3. Right click on the Policy name and select properties4. Expand the Printing folder and the Client Printers folder5. Select Auto-Creation - Check Enabled and select Auto-Create all client printers6. Expand the Drivers folder7. Select Native Printer Driver auto-install - Check Enabled and select Do not automatically install drivers8. Select Universal driver - Check Enabled and select Use universal driver only if requested driver is unavailable9. Click Apply and OK10. Right click on the Policy name and select Apply this policy to11. Select Servers and check the Filter based on servers to apply the policy to all servers and click OKMigrating SQL databasesIf during the initial Citrix installation the default database was selected and you want to change it from Master to something else, here are the steps that should be taken:Create a Citrix database called CTX, create a SQL user called citrix and grant the user dbo database access.First Citrix Server:1. From a command prompt cd\program files\citrix\independent management architecture2. copy mf20.dsn mast.dsnContents of mast.dsn:[ODBC]DRIVER=SQL ServerUID=saDATABASE=masterWSID=CTXSERVERNAMEAPP=Citrix IMASERVER=SQLSERVERNAMEDescription=CitrixThis assumes the sa SQL account was used to connect to the database. If DATABASE isn't a part of this configuration then Citrix knows to default to master.WSID=Name of the serverSERVER=Name of SQL server3. edit mf20.dsnContents of mf20.dsn:[ODBC]DRIVER=SQL ServerDATABASE=ctxWSID=CTXSERVERNAMEAPP=Citrix IMASERVER=SQLSERVERNAMEDescription=Citrix4. dsmaint config /user:sa /pwd:sapassword /dsn:"c:\program files\citrix\independent management architecture\mast.dsn"If the datastore is using an Access database with the default settings use the following credentials:/user:citrix /pwd:citrix (omitting these will use the defaults)This tells Citrix what DSN to use. For this example we're telling it to temporarily use the MAST.dsn5. dsmaint migrate /srcdsn:"%ProgramFiles%\Citrix\Independent Management Architecture\MAST.dsn" /srcuser:sa /srcpwd:sapassword /dstdsn:"%ProgramFiles%\Citrix\Independent Management Architecture\MF20.DSN" /dstuser:citrix /dstpwd:citrixpasswordThis copies the necessary tables from the source DSN to the destination DSN. The MAST.dsn looks at the master database in SQL and the MF20.dsn goes to the CTX database.6. dsmaint config /user:citrix /pwd:citrixpassword /dsn:"c:\program files\citrix\independent management architecture\mf20.dsn"This tells Citrix what DSN to use. For this example we're telling it to use the MF20.dsn which will be used for production.7. Stop IMA service8. dsmaint recreatelhcFlushes all the local host cache info out and pulls in a fresh copy from SQL9. Start IMA serviceOther Citrix Servers:1. Copy the MF20.dsn from the first server to other servers and edit the WSID so that it's the same as the server name2. dsmaint config /user:citrix /pwd:citrixpassword /dsn:"c:\program files\citrix\independent management architecture\mf20.dsn"3. Stop IMA service4. dsmaint recreatelhc5. Start IMA serviceMaster Database Cleanup:This is so it's not used accidentallyrename keytable _keytablerename indextable _indextablerename deletetracker _deletetrackerrename datatable _datatableTo test that everything worked properly, published a test application like Freecell using the Citrix Management Console and launch it from servers in the farm and if installed from the web interface. To make 100% sure everything works, reboot the servers and confirm no errors are in the event logs.Copying SQL databasesHow to copy a SQL database to a different server:Create a Citrix database in SQL Server called CTX, create a SQL user called citrixima and grant the user dbo database access.1. Copy MF20.DSN to MFBAK.DSN in C:\Program Files\Citrix\Independent Management ArchitectureContents of mfbak.dsn:[ODBC]DRIVER=SQL ServerUID=citriximaDATABASE=CTXWSID=CTXSERVERNAMEAPP=Citrix IMASERVER=SQLSERVERNAMEDescription=Citrix2. dsmaint migrate /srcdsn:"%ProgramFiles%\Citrix\Independent Management Architecture\mf20.dsn" /srcuser:ctxprodusrname /srcpwd:ctxprodusrpassword /dstdsn:"%ProgramFiles%\Citrix\Independent Management Architecture\MFBAK.DSN" /dstuser:ctxbakusrname /dstpwd:ctxbakpasswordExample:REM: Performed on Citrix server named citrix01REM: SQL Servername is SQLREM: Current UserID is citriximaREM: Current Password is Citrixima123$REM: Backup UserID is citrixbakREM: Backup Password is Citrixbak123$MF20.DSN[ODBC]DRIVER=SQL ServerUID=citriximaDATABASE=citrixWSID=citrix01APP=Citrix IMASERVER=sqlDescription=CitrixMFBAK.DSN[ODBC]DRIVER=SQL ServerUID=citrixbakDATABASE=citrixbakWSID=citrix01APP=Citrix IMASERVER=sqlDescription=Citrix3. dsmaint migrate /srcdsn:"%ProgramFiles%\Citrix\Independent Management Architecture\mf20.dsn" /srcuser:citrixima /srcpwd:Citrixima123$ /dstdsn:"%ProgramFiles%\Citrix\Independent Management Architecture\MFBAK.DSN" /dstuser:citrixbak /dstpwd:Citrixbak123$More coming soon...。
Shasta日常维护及TroubleShootingV19(doc 10页)
Node:11/4/3 ←---------------------第三个SSP
11 SSC /SSC EnabledU U U U
12 ALC /ALC Enabled U U U U [ICP Rev. 1.6]
13 CMC /CMC Enabled Active
14 CMC /CMC Enabled Standby (Redundant)
bsn(SSU)# show sspmgr rm detail
2
12/30/2004
1.3
Han Wei / Hu Bill
Change the recommended connection number based on R4.5 guideline.
3
1/12/2005
1.4
Han Wei / Hu Bill
Add provisioned Connection number/SSP/SSM
Maximum Number of connections Allowed: 1600
Number of VPN FIBs: 1 Max Allowed: 512
Node:11/4/2 ←---------------------第二个SSP
Bandwidth: real: 80000 over: 0 total 80000 cur: 20110 avail: 59890
Slot Configured/Found Enabled Info
---- ----------------- ------- -----
1 ALC /ALC Enabled U U U U [ICP Rev. 1.6]
troubleshooting专业术语 -回复
troubleshooting专业术语-回复Troubleshooting is an essential skill in various fields, including technology, engineering, and computer science. It involves identifying and resolving problems or issues that may arise in a system, device, or process. To effectively troubleshoot, professionals often rely on a set of specialized terms and techniques. In this article, I will guide you through the process of troubleshooting, exploring and explaining key troubleshooting terms along the way.Step 1: Problem IdentificationThe first step in troubleshooting is to identify the problem. This requires carefully observing and analyzing the symptoms or issues that are occurring. Some common troubleshooting terms related to problem identification include:1. Symptoms: These are the observable signs or behaviors that indicate a problem. For example, a slow computer or a flickering screen are symptoms of potential issues.2. Error Codes: Error codes are numerical or alphanumeric codesthat indicate specific problems or malfunctions. These codes are often displayed on screens or reported by software applications. Understanding error codes can provide crucial clues about what is causing a problem.3. Logs: Logs are records of events or activities that occur within a system. They can be found in various forms, such as log files, event logs, or system logs. Analyzing logs can help troubleshooters identify potential causes or patterns related to issues.Step 2: Problem LocalizationAfter identifying the problem, the next step is to localize it. This involves narrowing down the scope of the issue and determining where it originates. Some key terms used in problem localization include:1. Root Cause: The root cause is the underlying reason or source ofa problem. It is important to identify the root cause to address the issue effectively.2. Isolation: Isolation involves separating components or elementsof a system to identify which one is causing the problem. This can be done through a process of elimination or by using tools like circuit testers or diagnostic software.3. Fault Domain: A fault domain is a specific area or location wherea problem is occurring. It can refer to a physical space or a specific software module.Step 3: Troubleshooting TechniquesOnce the problem is localized, troubleshooting professionals employ various techniques to resolve the issue. Here are some commonly used techniques, along with relevant terms:1. Reboot: Rebooting involves restarting a device or system to resolve certain issues caused by software glitches or temporary errors.2. Configuration: Troubleshooting configuration issues involves examining and adjusting the settings or parameters of a system or device.3. Patching or Updating: Patching or updating means applying software updates or patches to fix known issues or vulnerabilities.4. Rollback: Rollback is the process of reverting to a previous version of software or configuration when a recent change caused the problem.5. Swapping: Swapping entails replacing a component or device with a known working one to determine if the original one is defective or faulty.Step 4: Documentation and ReportingTo ensure effective troubleshooting in the future and facilitate communication with others, documenting and reporting are crucial steps. Some relevant terms in this step include:1. Troubleshooting Documentation: This refers to the detailed records and information about the troubleshooting process, including the steps taken, the results obtained, and any resolutions or recommendations.2. Incident Report: An incident report is a formal document that summarizes the problem, the steps taken to troubleshoot, and the resolution or current status of the issue. It is often used for communication between different stakeholders.Step 5: Prevention and ImprovementLastly, troubleshooting involves implementing preventive measures and making improvements to minimize future problems. Important terms related to this step include:1. Preventive Maintenance: Preventive maintenance involves regular inspection, cleaning, and servicing of systems or devices to proactively prevent issues or failures.2. Continuous Improvement: Continuous improvement refers to an ongoing effort to enhance processes, systems, or products based on lessons learned from troubleshooting and other activities.In conclusion, troubleshooting is a systematic process that requires a deep understanding of specialized terms and techniques. Byfollowing a step-by-step approach and using relevant troubleshooting terms, professionals can efficiently identify and resolve problems in various fields.。
路由器故障诊断
Troubleshooting的工具Troubleshooting的工具有许多种,可以用路由器的诊断命令,Cisco网络管理工具(CiscoWorks)和规程分析仪等等方法.下面我们主要介绍路由器的诊断命令. 路由器诊断命令有四种:∙用show命令∙用debug命令∙用ping命令∙用trace命令用show 命令Show是一个很有用的监控命令和解决系统出现问题的工具.下面是几个通常用到的show命令:∙show interface---显示接口统计信息.一些常用的show interface命令:o show interface etherneto show interface tokenringo show interface serial∙show controllers---显示接口卡控制器统计信息.一些常用的show controllers命令:o show controllers cxbuso show controllers e1∙show running-config---显示当前路由器正在运行的配置.∙show startup-config---显示存在NVRAM配置.∙show flash---Flash memory内容.∙show buffers---显示路由器中buffer pools统计信息.∙show memory---路由器使用内存情况的统计信息,包括空闲池统计信息.∙show processes---路由器活动进程信息.∙show version---显示系统硬件,软件版本,配置文件和启动的系统映象. 用debug 命令在超级用户模式下的debug命令能够提供端口传输信息,节点产生的错误消息,诊断协议包和其它有用的troubleshooting数据.注意:使用debug命令要注意,它会占用系统资源,引起一些不可预测现象.终止使用debug命令请用no debug all命令.Debug命令默认是显示在控制台端口上的,可用log buffer命令把输出定向到buffers里面.若是telnet过去的,可用Router#terminal monitor监控到控制台信息.用ping命令Ping确定网络连通.用trace 命令Trace命令跟踪路由器包传输.TCP/IP连接的Troubleshooting现象:主机到本地路由器的以太口不通建议:我们可以把路由器的以太网口看作是普通主机的以太网卡,这就成了一个局域网连接问题,1.用show interface ethernet number命令Router#show interface ethernet 0Ethernet is up,line protocol is down2.若Ethernet is down,请把线缆(同轴线缆或双绞线)接上.若已接上,ethernet依然是down,请找你的代理联系.3.若Ethernet is admsinstratively down.Router#conf tRouter(config)#interface ethernet 0Router(config-if)#no shutdownRouter(config-if)#^ZRouter#4.若Ethernet is up,而line protocol is down.主机10M网卡接到路由器100M的以太口上面,它不是自适应的(目前版本).反之无问题.若是同轴线缆请检查线缆,T型头,终结器,是否连接正确.若是双绞线请检查线缆是否正确,中间是否通过HUB连接,若是直连主机要用交叉线.若是100BaseTX接口,需要用五类双绞线.若是一个接口提供两种物理介质,如粗缆AUI和UTPRJ45,默认为AUI的.要用RJ45需要:Router#conf tRouter(config)#interface ethernet 0Router(config-if)#media-type 10basetRouter(config-if)#^ZRouter#5.若Ethernet is up,line protocol is up;但ping不通.请查看路由器以太口的IP地址,是否与主机IP地址在同一个网段上.6.经过以上几个步骤,问题仍未解决,请找你的代理联系.现象:主机到对方路由器广域网口或以太网口不通.建议:假设主机到本地路由器的以太口已通.1.在路由器上检查两个广域网口之间是否通,若不通,请看下面关于广域网的troubleshooting.2.若路由器两个广域网口之间是通的.在主机上用"netstat -rn"命令查找路由,若没有请用"route add"加入.以SCO UNIX为例:#netstat -rn#route add 目的网段掩码网关1或#vi /etc/gatewaysnet 目的网段gateway 本地路由器以太口地址metric 1 passive3.若主机上有默认网关,检查路由器路由协议配置.Router#show ip routeRouter#show running-config...router eigrp 1network ...network ...两端路由器配置路由协议是否一致,是否在一个自治系统里面."network"加入的网段是否正确.现象:主机到对方目的主机不通.建议:按以下步骤解决.1.检查主机到本地路由器的以太口.2.检查两个广域网口.3.检查主机到对方路由器广域网口.4.检查主机到对方路由器以太网口.可用telnet命令远程登录到对方路由器上,按检查本地主机到本地路由器的以太口的方法检查对方局域网连接情况.5.重复3和4,检查对方到本地情况.6.经过以上几个步骤,问题仍未解决,请找你的代理联系.串口连接遇到问题的Troubleshooting现象:在专线连接时,路由器直连的两个广域网口间不通.建议:我们可以把两个路由器广域网口之间分成三段,如图所示:路由器A--1---MODEMA----2----MODEMB--3--路由器B我们的任务就是要检查出是哪一段不通并解决它.1.用show interface serial number命令2.若是Serial is down,表示路由器到本地的MODEM之间无载波信号CD.连接串口和MODEM,开启MODEM.看MODEM的发送灯TD是否亮,TD 灯亮表示路由器有信号发送给MODEM.TD灯若不亮,请检查MODEM,线缆(最好用Cisco所配的)和端口.你可以用另外一个串口再试试看.3.若Serial is up,但line protocol is down.有几种可能:a.本地路由器未作配置.b.远端路由器未开或未配置.路由器两端需要配置相同的协议打包方式.例如:路由器A打包HDLC,路由器B打包PPP,那么两台路由器的line protocol始终是down的.改变打包方式:Router#conf tRouter(config)#interface serial 0Router(config-if)#encapsulation pppRouter(config-if)#^ZRouter#c.若是使用Newbridge的26XX,27XX的DTU设备,它不发送CD信号,请在路由器上设置:Router#configure terminalRouter(config)#int serial 0Router(config-if)#ignored-dcdRouter(config-if)#^ZRouter#d.MODEM之间没通,即专线没通.解决办法:作测试环路.请电信局帮助确定具体出现问题是哪一段线路.若作环路成功,line protocol会变成up(looped).4.若Serial is up,但line protocol is up(looped).用show running-config看看端口是否作了loopback配置,若有删调它.MODEM是否作了环路测试.专线是否作了环路测试.5.若Serial is admsinstratively down,line protocol is down.Router#conf tRouter(config)#interface serial 0Router(config-if)#no shutdownRouter(config-if)#^ZRouter#电话拨号连接的Troubleshooting要解决用电话拨号网连接出现的问题,首先要:确定路由器与MODEM之间已连接明白show line输出的含义确定路由器与MODEM之间已连接我们在路由器上用反Telnet(Reverse Telnet Session)到MODEM,来确定路由器与MODEM之间的连接.也就是说,反向登录到MODEM上面可对它用AT指令作配置.具体步骤如下:1.在路由器控制台上,用命令telnet ip-address 20yy其中ip-address是一个活动端口的地址, yy是连接MODEM的line线.例如,下面例子是用IP地址192.169.53.52连接到辅助口上:telnet 192.169.53.52 20012.如果连接被拒绝,可能有其它用户连接在该口上.用show users EXEC命令决定是否被占用,若是,clear line清除它;若没有,重试反Telnet.3.如果连接仍被拒绝,确认MODEM控制modem inout.4.确定路由器txspeed和rxspeed与MODEM设置的数率一致.5.反Telnet登录成功后,AT命令确定应答OK.明白show line输出的含义Show line line-number EXEC是非常有用的trobbleshooting命令.现象:MODEM和路由器间无连接.试用反登录无反应或用户收到"Connection Refused by Foreign Host"信息.建议:1.用show line看MODEM一栏是否是"inout",若不是,在路由器上:Router#conf tRouter(config)#line aux 0Router(config-line)#modem inoutRouter(config-line)#^ZRouter#2.确定正确的线缆.3.硬件问题,请与你的代理联系.现象:MODEM不拨号.建议:MODEM不拨号,排除掉硬件,线缆的可能,就是:1.不感兴趣的包.用show running-config检查路由器配置,是否设置了dialer-list截段了你想传送的包,若是请重新配置access-list表.2.Chat script配置错误.打开debug信息.Router#debug dialer%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down%LINK-3-UPDOWN: Interface Serial0, changed state to down%LINK-3-UPDOWN: Interface Async1, changed state to downAsync1: re-enable timeoutAsync1: sending broadcast to default destination get_free_dialer: faking itAsync1: Dialing cause: Async1: ip PERMITAsync1:No holdq created - not configuredAsync1: Attempting to dial 8292CHAT1: Attempting async line dialer scriptCHAT1: Dialing using Modem script: backup & System script: none -- failed, not connectedCHAT1: process startedCHAT1: Asserting DTRCHAT1: Chat script backup startedCHAT1: Expecting string:Async1: sending broadcast to default destination -- failed, not connectedCHAT1: Timeout expecting:CHAT1: Chat script backup finished, status = Connection timed out; remote host not respondingAsync1: disconnecting call......帧中继连接的Troubleshooting1.用show interface serial查看interface和line protocol是否up.确定连接的线缆正确.2.如果interface is up,但line protocol是down.用show frame-relaylmi查看帧中继的LMI类型.3.用show frame-relay map查看打包类型.4.用show frame-relay pvc查看PVC.5.打开debug信息.X.25连接的Troubleshooting1.确定两个X.25端口连接上.MODEM状态:若线路已连通,MODEM的CD灯和RD灯应该亮,表示X.25交换机有数据发送过来.我们也可以用pad本地或对方的X.121地址,若能pad过去,说明行X.25网链路层已通.Router#pad 28050103(对方的X.121地址)2.用show interface serial命令.若serial is down,line protocol is down请检查路由器与MODEM连接线缆,换另外串口重试.3.若serial is up,但line protocol is down.请与电信局联系,检查LAPB参数是否匹配.4.若serial is up,line protocol is up.但ping对方广域网口不通.用show running-config查看串口是否作了x25 map ip设置.X.25设置中,最大虚电路数值是否超过了申请的值.5.若对方连接的不是路由器,而是一块X.25网卡(以博达卡为例)6.环境:7.知识:博达X.25卡上8.#cd /etc/x.259.#vi x25.profile (网卡参数设定文件)10.LOCADDR 28050103 (本地X.25端口X.121地址)11.VC 1612.IVC 0 (呼入VC数)13.OVC 0 (呼出VC数)14.PVC 0 (永久VC数)15.X25TIMEOUT 60 (拆链时间)16.故,SVC=VC-IVC-OVC-PVC.17.#x25reset (重启X.25网卡)18.#x25link (监控当前状态信息)19.#vi x25.addr (地址对应文件,IP层能互相通信,要把X.121地址与IP地址对应起来)20.130.132.128.4 28050104 SVC 021.130.132.128.3 28050103 SVC 022.#cd /etc23.#vi tcp 加上24.ifconfig x25 130.132.128.3 -arp network 255.255.0.025.一般X.25连接出现问题都是一方的IP地址与X.121地址之间映射没有设定.与IBM主机连接的Troubleshooting∙DLSw+ Troubleshooting∙STUN Troubleshooting∙CIP TroubleshootingDLSw+ Troubleshooting在用DLSw+通过路由器实现PU2.0/2.1与IBM大型主机之间连接,我们要同时用show dlsw和show interface serial命令解决出现的问题.1.首先检查DLSw+定义的两个对等peers是否连通2.Router#show dlsw peers3.Peers: state pkts-rx pkts-tx typedrops ckts TCP uptime4.TCP 17.18.15.1CONNECT16080 8400 conf0 0 0 00.03.275.TCP 1.1.12.1DISCONN0 0 conf0 0 0 00.00.006.Peers --- 对应"dlsw remote-peer"定义的对等peers IP地址.7.state --- 表示与对等peers的连接状态.8.其中:CONNECT表示对等peers已建立.9.CAP_EXG表示与远程peer交换性能信息.10.WAIT_RD是建立peer连接的最后一步,等待远程peer应答信息.11.DISCONN表示与对等peers没有建立连接,请参阅TCP/IP Troubleshooting检查TCP连接故障.WAN_BUSY表示TCP传输队列已满,不能传输数据.12.若对等peers已建立连接,请查看性能交换信息.Router#show dlsw capabilitiesDLSw: Capabilities for peer 172.18.15.166vendor id (OUI) : '00C' (cisco)version number : 1release number : 0init pacing window : 20unsupported saps : nonenum of tcp sessions :1loop prevent support : noicanreach mac-exclusive : noicanreach netbios-excl. : noreachable mac addresses : nonereachable netbios names : nonecisco version number : 1peer group number : 0border peer capable : nopeer cost : 3biu-segment configured : nolocal-ack configured: yespriority configured: noversion string :Cisco Internetwork Operating System SoftwareIOS (tm) GS Software (GS7-K-M), Experimental Version11.1(10956) [sbales 139]Copyright (c) 1986-1996 by cisco Systems, Inc.Compiled Thu 30-May-96 09:12 by sbales813.交换过性能信息后,就要寻找目的MAC地址了,显示出所有的路由器能够到达的MAC地址(本地和远端)14.Router#show dlsw reachability15.DLSw MAC address reachability cache list16.Mac Addr status Loc. peer/port rif17.0000.810f.6500 FOUND LOCAL TBridge-001 --norif--18.0006.e918.7b70 FOUND LOCAL TBridge-001 --norif--19.1000.5ae3.03f7 FOUND LOCAL TBridge-001 --norif--20.7500.9221.0000 FOUND REMOTE 16.201.30.250(2065)max-lf(4472)21.7500.9221.0000 SEARCHING LOCAL22.23.DLSw NetBIOS Name reachability cache listBIOS Name status Loc. peer/port rif25.SXUSER2 FOUND LOCAL TBridge-001 --norif--若本地MAC地址和目的MAC地址状态均是FOUND,请参看第五步.SEARCHING表示在寻找本地MAC地址或目的MAC地址.此时用show interface serial命令查看该口连接的PU状态.NOT_FOUND表示没有收到对PU轮询的应答.VERIFY表示确认缓存内信息.26.在SERACHING本地MAC地址或目的MAC地址.27.Router#show interface serial 028.Serial1 is up, line protocol is up29.Hardware is HD6457030.MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely255/255, load 1/25531.Encapsulation SDLC, loopback not set32.Router link station role: SECONDARY (DTE)33.Router link station metrics:34.group poll not enabled35.poll-wait 40000 seconds36.N1 (max frame size) 12016 bits37.modulo 838.sdlc vmac: 4000.5555.00--39.sdlc addr C1 state is DISCONNECT40.cls_state is CLS_STN_CLOSED41.VS 0, VR 0, Remote VR 0, Current retransmit count42.Hold queue: 0/200 IFRAMEs 0/043.TESTs 0/0 XIDs 0/0, DMs 0/0 FRMRs 0/044.RNRs 0/0 SNRMs 0/0 DISC/RDs 0/0 REJs 0/0chain: C1/C1st input never, output never, output hang neverst clearing of "show interface" counters never47.Queueing strategy: fifo48.Output queue 0/40, 0 drops; input queue 0/75, 0 drops49. 5 minute input rate 0 bits/sec, 0 packets/sec50. 5 minute output rate 0 bits/sec, 0 packets/sec51.0 packets input, 0 bytes, 0 no buffer52.Received 0 broadcasts, 0 runts, 0 giants53.0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored,0 abort54.0 packets output, 0 bytes, 0 underruns55.0 output errors, 0 collisions, 19 interface resets56.0 output buffer failures, 0 output buffers swappedout57. 6 carrier transitions58.DCD=up DSR=up DTR=up RTS=up CTS=up59.说明:60.Encapsulation SDLC---串口打包方式为SDLC.61.Router link station role: SECONDARY (DTE)---目前端口作secondary,由"sdlc role"命令设置.62.sdlc vmac: 4000.5555.00-- ---由"sdlc vmac"设置的MAC地址.注意它的最后两位是留给PU地址的.63.在本例中,端口MAC地址是4000.5555.00C1.64.sdlc addr C1 state is DISCONNECT ---该端口连接PU C1当前状态.有以下几种状态:65.DISCONNECT-与PU未连接,次站没有发TEST或XID帧请求建立连接.请检查下面连接的PU是否启动66.SNA进程,若是用DCE线缆连接PU请检查线缆是否正确,若是MODEM连接到远端PU上,请67.检查MODEM状态灯.68.69.DISCSENT-路由器发送断开请求(DISC)给次站,正在等待次站应答.70.71.SNRMSENT-路由器发送连接请求(SNRM)给次站,正在等待次站应答.这个状态出现在作主站的路由器72.上.若是在作主站路由器上出现SNRMSENT状态,检查下端PU是否开机,路由器端口与PU上73.SDLC口连接的MODEM是否已通(MODEM的DTR,CD,RXD,TXD灯应常亮).一句话,出现SNRMSENT74.状态是路由器端口与它下端PU之间问题.75.76.CONNECT-PU连接正常.路由器和它连接的次站正常连接.77.78.THEMBUSY-PU发送RNR帧.次站告诉路由器暂时不能接收任何信息.79.BUSY-路由器发送RNR帧.路由器告诉次站暂时不能接收任何信息.路由器已接收到次站对SNRM帧的81.应答帧UA,试图建立SDLC或LLC2会话.82.83.BOTHBUSY-双方均发送RNR帧.告诉对方暂时不能接收任何信息.84.85.ERROR-违反SDLC协议.路由器正在等待次站应答.86.87.SNRMSEEN-路由器作次站,接收到SNRM帧.88.当双方MAC地址都找到后,开始建立链路了.89.Router#show dlsw curcuit90.Index local addr(lsap) remote addr(dsap) state91.181**** ****.5ae3.430d(04) 4000.5555.00c1(04)CONNECTED92.用"show interface serial"查看PU状态应是"CONNECT".我们也可以用"debug dlsw"获得更多的信息帮助解决网络中出现的问题.你可以记录下debug传输信息提供给你的代理.问题:远端没有到达本端机器.远端peer的IP地址是172.18.16.156.建议:1.检查show dlsw peer输出,我们看到:2.Peers: state pkts-rx pkts-tx typedrops ckts TCP uptime3.TCP 172.18.16.156 DISCONN 0 0conf 0 0 0 --4.用debug dlsw peers命令决定问题:DLSw: action_a() attempting to connect peer 172.18.15.156(2065) DLSw: action_a(): Write pipe opened for peer 172.18.15.156(2065) DLSw: peer 172.18.15.156(2065), old state DISCONN, new stateWAIT_RDDLSw: dlsw_tcpd_fini() for peer 172.18.15.156(2065)DLSw: tcp fini closing connection for peer 172.18.15.156(2065)DLSw: action_d(): for peer 172.18.15.156(2065)DLSw: peer 172.18.15.156(2065), old state WAIT_RD, new stateDISCONNDLSw: Not promiscuous - Rej conn from 172.18.15.166(2065)诊断:试着打开peer 172.18.15.156,但不成功.DLSw+接收到来自172.18.15.166的打开请求,但是DLSw+拒绝它,因为这个peer没有定义.由此我们可以判断定义peer地址不正确.该peer地址为172.18.15.166就连通了. Peers: state pkts-rx pkts-tx type drops ckts TCP uptimeTCP 172.18.16.166 CONNECT 2 2 conf0 0 0 00:224:27问题:SDLC设备不能连接到主机.Milan是连接SDLC设备的远端peer.建议:1.用show dlsw peer命令显示peer是up的.an#sh dlsw peers3.Peers: state pkts-rx pkts-tx typedrops ckts TCP uptime4.TCP 172.18.16.166 CONNECT 2 2conf 0 0 0 00:224:275.Show dlsw circuits没有链路产生.an#show dlsw circuitsan#8.Show interface 命令显示SDLC 地址状态是USBUSY,这表示我们已经成功的连接到下端路由器上.9.Router#show interface serial 3/710.Serial1 is up, line protocol is up11.Hardware is HD6457012.MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely255/255, load 1/25513.Encapsulation SDLC, loopback not set14.Router link station role: SECONDARY (DTE)15.Router link station metrics:16.group poll not enabled17.poll-wait 40000 seconds18.N1 (max frame size) 12016 bits19.modulo 820.sdlc vmac: 4000.5555.00--21.sdlc addr C1 state is USBUSY22.cls_state is CLS_STN_CLOSED23.VS 0, VR 0, Remote VR 0, Current retransmit count24.Hold queue: 0/200 IFRAMEs 0/025.TESTs 0/0 XIDs 0/0, DMs 0/1 FRMRs 20/2026.RNRs 620/0 SNRMs 3/0 DISC/RDs 1/0 REJs 0/0chain: C1/C127.sdlc addr C2 state is USBUSY28.cls_state is CLS_STN_CLOSED29.VS 0, VR 0, Remote VR 0, Current retransmit count30.Hold queue: 0/200 IFRAMEs 0/031.TESTs 0/0 XIDs 0/0, DMs 0/0 FRMRs 0/032.RNRs 730/0 SNRMs 7/0 DISC/RDs 0/0 REJs 0/0chain: C2/C2st input never, output never, output hang neverst clearing of "show interface" counters never35.Queueing strategy: fifo36.Output queue 0/40, 0 drops; input queue 0/75, 0 drops37. 5 minute input rate 0 bits/sec, 0 packets/sec38. 5 minute output rate 0 bits/sec, 0 packets/sec39.0 packets input, 0 bytes, 0 no buffer40.Received 0 broadcasts, 0 runts, 0 giants41.0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored,0 abort42.0 packets output, 0 bytes, 0 underruns43.0 output errors, 0 collisions, 19 interface resets44.0 output buffer failures, 0 output buffers swappedout45. 6 carrier transitions46.DCD=up DSR=up DTR=up RTS=downCTS=up47.检查配置到达的目的MAC地址是4001.3745.1088.an#write terminal49....50.!51.interface Serial3/752.description sdlc config to MVS53.mtu 440054.no ip address55.encapsulation sdlc56.no keepalive57.clockrate 960058.sdlc role primary59.sdlc vmac 4000.1234.560060.sdlc N1 1201661.sdlc address C162.sdlc xid C1 05DCCCC163.sdlc partner 4001.3745.1088 C164.sdlc address C265.sdlc xid C2 05DCCCC266.sdlc partner 4001.3745.1088 C267.sdlc dlsw C1 C268.!69....70.用show dlsw reachability mac-address命令发现MAC地址没找到:71.Router#show dlsw reachability mac-address 4001.3745.108872.DLSw MAC address reachability cache list73.Mac Addr status Loc. peer/portrif74.0000.810f.6500 SEARCHING LOCAL75.在FEP连接的路由器一端,用show dlsw reachabilitymac-address命令发现MAC地址没找到:76.Router#show dlsw reachability mac-address 4001.3745.108877.DLSw MAC address reachability cache list78.Mac Addr status Loc. peer/portrif79.0000.810f.6500 SEARCHING REMOTE80.显示show source-bridge,没有令牌环口走SRB:bolzano#show source-bridgeGlobal RSRB Parameters:TCP Queue Length maximum: 100Ring Group 100:No TCP peername set, TCP transport disabledMaximum output TCP queue length, per peer: 100Rings:诊断:加上"source-bridge"命令,连接正常了.问题:同一个串口上,一个SDLC设备连接正常而其它几个不行.建议:1.用show dlsw peer命令显示peer是up的.an#sh dlsw peers3.Peers: state pkts-rx pkts-tx typedrops ckts TCP uptime4.TCP 172.18.16.166 CONNECT 2 2conf 0 0 0 00:224:275.用show dlsw reachability mac-address命令发现MAC地址:6.Router#show dlsw reachability mac-address 4001.3745.10887.DLSw MAC address reachability cache list8.Mac Addr status Loc. peer/port rif9.0000.810f.6500 FOUND REMOTE 172.18.15.166(2065)10.用show dlsw circuits mac-address命令告诉两个链路连接:an#show dlsw circuit mac-address 4001.3745.108812.Index local addr(lsap) remote addr(dsap) state13.250-00 4000.1234.56c1(04) 4001.3745.1088(04)CONNECTED14.251-00 4000.1234.56c2(04) 4001.3745.1088(04)CKT_ESTABLISHED15.16.用debug dlsw core命令输出:milan#debug dlsw core stateDLSw core state debugging is onmilan#DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED DLSw: core: dlsw_action_f()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED DLSw: core: dlsw_action_f()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:WAN-XIDstate:CKT_ESTABLISHEDDLSw: core: dlsw_action_g()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED DLSw: core: dlsw_action_f()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED DLSw: core: dlsw_action_f()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED DLSw: core: dlsw_action_f()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED DLSw: core: dlsw_action_f()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:WAN-XIDstate:CKT_ESTABLISHEDDLSw: core: dlsw_action_g()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHEDDLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED DLSw: core: dlsw_action_f()DLSw: END-FSM (251-00):state:CKT_ESTABLISHED->CKT_ESTABLISHED诊断:DLSw试图在下端SDLC设备和FEP之间传输XID,但FEP并不建立会话.它通常是XID(IDBK/IDNUM)引起的.在配置中加上"sdlc xid"后连接正常.STUN Troubleshooting1.确定stun peer连通2.rick#sh stun peer3.This peer: 10.17.5.24.5.*Serial2 (group 1 [basic])6.state rx_pkts tx_pkts drops7.all TCP 10.17.5.2 open5729 5718 08.若状态不是open,应是TCP/IP连接问题,请参阅TCP/IPTroubleshooting.9.用show interface确定路由器和主机之间serial is up,line protocol isup.若是"down/down"请检查线缆,正确使用DTE和DCE Cable.若serial一会儿up,一会儿down,不断反复.你的主机可能配置成半双工的而不是全双工的,使用MSD时路由器没有设成半双工的.10.如果serail is up,但line protocol is down.最大可能是一端是NRZ编码,另一端是NRZI编码.用"nrzi-encoding"命令设置NRZI编码.设定编码方式与大机相同.11.一旦line操作正常,最常出现的问题就是SDLC地址不对.SDLC地址要与主机PU地址一致.如果收到下面信息就表示SDLC地址与主机PU地址不匹配.Received data from wrong address! Expect for output addressC2/Got C4.Debug sdlc当工作正常时,debug输出信息顺序:SDLC Primary :DISCONNECT-->SDLC PRI WAIT-->NET UP WAIT-->CONNECTSDLC Secondary :DISCONNECT-->NET UP WAIT-->SDLC SECWAIT-->CONNECTCIP Troubleshooting1.用"show interface channel 3/0"显示物理通道端口状态.若channel3/0 is up,line protocol is up.2.表示物理接口连接正常.否则请检查物理接口,线缆,bypass等是否连接正确.3.Router#sh int c3/04.Channel3/0 is up, line protocol is up5.Hardware is cyBus Channel Interface6.MTU 4096 bytes, BW 36864 Kbit, DLY 270 usec, rely 255/255,load 1/2557.Encapsulation CHANNEL, loopback not set8.PCA adapter card9.Data transfer rate 4.5 Mbytes, number of subchannels 1st input never, output never, output hang neverst clearing of "show interface" counters never12.Output queue 0/40, 0 drops; input queue 0/75, 0 drops13. 5 minute input rate 0 bits/sec, 0 packets/sec14. 5 minute output rate 0 bits/sec, 0 packets/sec15.1677 packets input, 0 bytes, 0 no buffer16.Received 0 broadcasts, 0 runts, 0 giants17.0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort18.1595 packets output, 0 bytes, 0 underruns19.0 output errors, 0 collisions, 5 interface resets, 0 restarts20.0 output buffer failures, 0 output buffers swapped out21.用"show interface channel 3/2"显示逻辑通道口状态.22.Router#sh int ch3/223.Channel3/2 is up, line protocol is up24.Hardware is cyBus Channel Interface25.MTU 4472 bytes, BW 98304 Kbit, DLY 100 usec, rely 255/255,load 1/25526.Encapsulation CHANNEL, loopback not set27.Virtual interfacest input 0:01:36, output 0:01:26, output hang neverst clearing of "show interface" counters never30.Output queue 0/40, 0 drops; input queue 0/75, 0 drops31. 5 minute input rate 0 bits/sec, 0 packets/sec32. 5 minute output rate 0 bits/sec, 0 packets/sec33.19090 packets input, 686391 bytes, 0 no buffer34.Received 0 broadcasts, 0 runts, 0 giants35.0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort36.20314 packets output, 754513 bytes, 0 underruns37.0 output errors, 0 collisions, 0 interface resets, 0 restarts38.0 output buffer failures, 0 output buffers swapped out39.用"show ext ch 3/0 csna oper"显示CSNA通道连接设备状态.40."stat"替代"oper"获得CSNA通道连接设备的统计值.41.确认CSNA通道连接设备状态为"setupComplet".42.Router#sh ext c3/0 csna43.Path Dv maxpiu time-delay length-delay44.CSNA 0100 E1 20470 10 2047045.Router#sh ext c3/0 csna oper46.Path Dv Status SlowDown maxpiutime-delay length-delay47.CSNA 0100 E1 setupComplet off 2047010 2047048.用"show ext ch 3/2 conn llc"命令确定SAPs值和CIP上打开的连接.49.确认定义在XCA中的正确的SAP值在CIP internal TokenRing LAN adapter中已打开.50.SHANXI2#sh ext c3/2 conn llc51.N Token 0 Adapter 1 5808.0100.000053.No SAPs open on this interface54.55.Total : SAPs opened = 0 Connections active = 056.如果CSNA通道连接设备状态是"setupComplet",正确的SAP值(i.e.,SAP 08)打开在正确的CIP internal57.MAC adapter上,进入第七步.否则,问题可能是PATH/DEVICE或XCA Major Node.请检查通道地址定义是否58.正确.若PATH/DEVICE正确,再在主机上"vnet,act,id=<xcamajnode>"命令确认XCA Major Node激活.59.Router#sh ext c3/0 csna oper60.Path Dv Status SlowDown maxpiutime-delay length-delay61.CSNA 0100 E1 Close off 20470 102047062.用"debug source-bridge"命令确定是否产生探测帧.如果确定以CIPinternal MAC地址为目的的探测帧被接收到,请打开"debug channel vlan".63.用"show ext ch 3/2 lan"命令显示CIP internal MACadapters.核实CIP internal MAC adapter被64.CIP microcode确认.65.router#debug channel vlan66.router#show ext ch 3/2 lann TokenRing 068.source-bridge 1000 1 10069.Adapno Mac Address Name Vcnum70.0 4000.1234.0001 544 0041 ACK ... ... ... ......INU71.如果CIP internal MAC adapters没有收到CIP的应答,(在"show ext ch3/2 lan"显示不是ACK而是CRE或PNDIND),表明CIP microcode没有承认CIP adapter配置命令.在这种情况下,RP不发送探测帧给CIP. 72.如果CIP internal MAC adapters已经接收到CIP的应答,用"show extch 3/2 llc stat 4000.0008.0000",4000.0008.0000是CIP的internal MAC address,检查是否收到CIP MAC adapter的检测命令和应答. 73.如果正常,再用"show ext ch 3/2 llc stat 4000.0008.0000 08"命令确认SAP是否接收到XIDs和应答.如果没有应答,可能是Switched Major Node没被激活,或IDBLK/IDNUM不正确,或PU被占用.74.在下端路由器上"show dlsw"命令查看串口连接的SNA endstation状态.参阅DLSw+ Troubleshooting.75.用"show llc2"显示当前已建立的LLC2链接.76.SHANXI2#sh llc77.LLC2 Connections: total of 1 connections78.Channel1/2 DTE: 5808.0100.0000 4000.4700.10c1 04 04 stateNORMAL79.V(S)=38, V(R)=38, Last N(R)=38, Local window=7, RemoteWindow=12780.akmax=3, n2=8, Next timer in 752081.xid-retry timer 0/0 ack timer 0/100082.p timer 0/1000 idle timer 7520/1000083.rej timer 0/3200 busy timer 0/960084.akdelay timer 0/100 txQ count 0/20085.RIF: 0630.0641.0020感谢下载!欢迎您的下载，资料仅供参考。
ACS运动控制：SPiiPlus_JasonHu_Advantofine_2008~2009
研拓自动化
SPiiPlus运动控制框架
For Master - Slave Motion Master Formula Master position (MPOS) Motion generator
MPU
Convert units to counts (EFAC)
Axis position (APOS)
8轴均独立，支持8轴联动 8轴点对点，JOG，跟随运动 8轴连续直线插补 PVT三次样条插补，S曲线加速 运动中改变位置、速度、加速度 反向运动学和轴变换 主从跟随，虚拟主轴 电子齿轮，电子凸轮 高级龙门控制算法 输入整形控制算法(Input Shaping)
研拓自动化
Q&A
研拓自动化
Thanks!
ACS Motion Control：SPiiPlus
Jason Hu / 胡杰辉 Application Engineer AdvanTofine Automation jiehui.hu@
研拓自动化
ACS Motion Control
成立时间：1985年 产品：高性能多轴运动控制器 应用：中高端设备 布局
SPiiPlus MMI SPiiPlus Simulator SPiiPlus FRF SPiiPlus Library PLCopen
研拓自动化
Firmware - MPU程序
与SP程序通信 运动轨迹生成（APOS） 给定值计算（RPOS） 安全控制 数据采集 硬件位置触发（PEG） 硬件位置触发（MARK） 主机即时命令执行 任务调度和管理
研拓自动化
研拓自动化
统一的软件平台：SPiiPlus ADK
SPiiPlus MMI SPiiPlus Simulator SPiiPlus FRF SPiiPlus Library PLCopen 文档 课件与例程
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
SpiiPlusSC Motion ControllerTroubleshooting GuideSPiiPlusSC Motion ControllerVersion SC 2.20COPYRIGHTCopyright ® 1999 - 2013 ACS MotionControl Ltd.Changes are periodically made to the information in this document. Changes are published as release notes and are subsequently incorporated into revisions of this document.No part of this document may be reproduced in any form without prior written permission from ACS MotionControl.TRADEMARKSACS MotionControl, PEG and SPii are trademarks of ACS MotionControl Ltd.EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation GmbH, Germany.Visual Basic and Windows are trademarks of Microsoft Corporation.Any other companies and product names mentioned herein may be the trademarks of their respective owners.Web Site: Information: info@Tech Support: support@ ACS Motion Control, Ltd.Ramat Gabriel Industrial ParkPOB 5668Migdal HaEmek, 10500ISRAELTel: (972) (4) 6546440Fax: (972) (4) 6546443NOTICEThe information in this document is deemed to be correct at the time of publishing. ACS MotionControl reserves the right to change specifications without notice. ACS MotionControl is not responsible for incidental, consequential, or special damages of any kind in connection with using this document.SPiiPlusSC Motion ControllerRelated DocumentsThe following documents provide additional details relevant to this guide:About This DocumentThis document covers all known issues for SPiiPlusSC Motion Controller and provides detailed step-by-step instructions. The soltions are based on a three-step approach: detecting the problem, suggesting possible causes, and resolving the problem.SPiiPlusSC Motion Controller Table of ContentsTable of Contents1SPiiPlusSC Installation Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1The output in UMD "freezes" after displaying "checking license….OK" . . . . . 2 1.2Communication with SPiiPlusSC is being lost periodically . . . . . . . . . . . . . . . 5 1.3MMI Application Studio loses communication with SPiiPlusSC when theapplication is not on the host PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5SPiiPlusSC Motion Controller SPiiPlusSC Installation Version 1SPiiPlusSC Installation VersionUse this guide when the SPiiPlusSC 2.20 official version is installed on the host PC.2Troubleshooting2.1The output in UMD "freezes" after displaying"checking license….OK"Full DescriptionAfter clicking "Start SPiiPlusSC" button in the UMD, the last line that can be seen in the Controller Output window is "checking license…OK".Possible Cause 1IP address of SPiiPlusSC is not in the same subnet as the IP address of the Virtual Network Adapter. For example, SPiiPlusSC has the following IP address: 192.168.157.20, while the Virtual Network Adapter has the following IP address: 169.168.158.19.SolutionSet a static IP address for Virtual Network Adapter. The IP address should be in the same subnet, for example: 192.168.157.4Possible Cause 2For Windows 7 only, it is possible that after installing a new driver for the network adapter or that a network bridge was set and then deleted, NetBIOS disables communication with SPiiPlusSC.SolutionRun the DisableNetBIOS utility that fixes this issue (part of the installation). Note that the computer must be restarted after running the utility.Default path on X64 platform:C:\Program Files\ACS Motion Control\SPiiPlusSC\x64\DisableNetBIOS_x64.exeDefault path on X86 platform:C:\Program Files\ACS Motion Control\SPiiPlusSC\x86\DisableNetBIOS_x86.exe Possible Cause 3The cause might be an expired password.SolutionReset the spiiPlusSC user password.1.Select Computer Management > Local Users and Groups > Users.2.Right-click spiiplussc, select set password, and type the same password that appears inthe user mode driver.3.Right-click spiiplussc, select properties, and check the Password never expires option.1.2Communication with SPiiPlusSC is being lostperiodicallyFull DescriptionSPiiPlusSC starts OK and communication is established from the MMI Application Studio. However, after a few seconds communication is lost.Possible CauseThere is an additional SPiiPlusSC Controller in the same network (LAN) with the same MAC Address. MAC Addresses must be unique within the same network.SolutionChange the MAC Address of the SPiiPlusSC Controller in the User Mode Driver\SPiiPlusSC tab.1.3MMI Application Studio loses communication withSPiiPlusSC when the application is not on the host PC Full DescriptionSPiiPlusSC starts OK. The MMI Application Studio connects to SPiiPlusSC from another computer (can be via bridge or point to point), but after a few minutes the communication is lost.Possible CauseWindows 7 power management option put computer to sleep is checked. This means that after X minutes, Windows enters sleep mode and SPiiPlusSC disconnects.SolutionSet the put computer to sleep option to Never:。