Cyclades PC400 installation manual Troubleshooting, General Tips

Page 28

Cyclades-PC400

Installation Manual

CHAPTER 5 TROUBLESHOOTING

General Tips

What to Do When the PC400 is Not Recognized by the Operating System

• Does the operating system detect the PC400 on boot? A message similar to

Cyclades-PC400 driver <version> <date> built <date>

PC400 #1, RAM at 0xMMMM, IRQn, 64 channels starting from port 0 PC400 #2, RAM at 0xMMMM, IRQn, 64 channels starting from port 64 etc.

should appear on boot. If not,

Is the board properly installed (physically)? Check the connections inside the computer.

Does your Linux operating system meet the requirements outlined at the beginning of chapter 3? The kernel version can be discovered by typing the command uname -r.

The steps in chapter 4 related to the device files should be reviewed and the configuration files checked.

Check the configurations modified using “make config” or “make menuconfig” (details supplied in chapter 3). If they are incorrect, execute the commands make dep and then make bzlilo modules modules_install again to rebuild the kernel. Reboot the computer and see if the boards are detected.

How to Test if the PC400 is Functioning

The simplest way to test a WAN connection is by pinging. Type ping <IP address of device to be pinged>. If a response is not received from the remote machine there is probably a problem with the link. Make sure the remote machine is up by accessing it from another computer before following the directions below.

What to Do if the PC400 is Detected by the Computer, but Does Not Function as Expected.

Is the cable properly connected and is the correct cable being used?

Type the command ifconfig. Do the devices set up for the board in chapter 4 appear?

Type the command netstat -rnto see the routing table. Have you defined a default gateway and/or have a route that includes the remote device you are trying to reach?

Chapter 5 Troubleshooting

28

Image 28
Contents Cyclades-PC400 FCC Warning Statement Cyclades-PC400 Installation ManualCanadian DOC Notice Table of Contents Appendix B Hardware Specifications What is in the BOX Upgrades of Software and ManualsStep One Hardware InstallationStep Two Step Three Step Four Step FiveSoftware Installation Software Installation Make config Make menuconfig Step ONE Board and System ConfigurationStep TWO Dspprofilebegin InterfnNbegin Label Description ISDN-PRI Profile Parameters Interface Parameters USA AT&T Last or channelnumberchannelnumberchannelnumber etc Pc400loadPc400util -p Step ThreeStep Four Step Five Guided Examples for the Most Common ApplicationsLAN ISDN-BRIParameter Description Value for T1 Value for E1 Line RAS DIAL-IN Application Parameters∙∙∙ LAN Example 2 a LAN-to-LAN Example Using ChannelsETH0 10 Multiple LAN-TO-LAN Application Parameters ∙∙∙ Troubleshooting General TipsHardware Test Root@cyclades common# ./pc400hwtestESC Previous Menu G Global E Errors Global TestPasses Pg0 Board DSP U19 U06 U20 U07Previous Menu G Global E Errors ESCAdministrative Utilities Users and Passwords Appendix a Information for Users not Familiar with LinuxPasswd Linux File StructureBasic File Manipulation Commands Cp filename destinationVi Editor Mode What is done there How to Get ThereVi filename Routing Table Netstat -rn Net-hostNetmask Ssh The Secure Shell SessionLoading the Configuration File PID TTY Stat Time CommandProcess Table Minute hour date month day-of-week user command Get information from the boardSyslog Crond UtilityActive root /etc/tstcron.src Dhcp Dynamic Host Configuration Protocol Client59 * * * * /etc/testcron.sh Packet Filtering using ipchains Accept Deny Interface isCyclades-PC400 Installation Manual Appendix B Hardware Specifications RJ-48C Signal Pin RxTip RxRing TxTip TxRingCyclades Philippines