Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Ultra10 ethernet troubleshooting Post 15995 by xyyz on Friday 22nd of February 2002 07:49:22 PM
Old 02-22-2002
Ultra10 troubleshooting!

The problem is alot worse that I thought. I ran the 'test net' after I did the 'stop a' thing and the system worked once, but the second time it froze. No matter what i tried I couldn't get the system out of a frozen state so I had to cycle the power.

I thought lemme check the entire system to see what's going on, so I did a "test scsi" which did nothing for a few seconds and then I was flooded with a "bus fault" message. The system seemed to keep on generating this message and it was stuck in this loop. Again, I had to cycle the power to get a functioning system.

While I am writing this, I tried this one more time. After I cycled the power the link light blinked on on my switch. I ran the 'test net' and everything seemed to check out. When I tried to run it again, the loopback test succeeded but the transceiver test failed with a return code = -1.

I've tried the 'test scsi' which doesn't seem to give any errors right now.

I'm completely lost here. I dunno what I should do. I'm thinking that the hardware is probably faulty which means the guy I bought it from ripped me off.

observation
maybe this isn't entirely true, but i've noticed, that when I do a 'stop a' right after I boot the system I can run the test w/o an error or lockup (although, I seem to only be able to run 'test net' once, after that I get an error or the system freezes), BUT after the system does the filesystem cleanup (from the power off) and brings the integrated nic up, i get error messages.

Does something happen that results in these errors? If someone could explain the bootup workings of an Ultra10 i'd really appreciate it.

The following is the original message I posted:

I'm getting odd problems with my Ultra10's integrated ethernet port.

It seems that the unit works intermittantly. Today it took about 5 minutes before the port light was lit on my switch.

I disconnected the cable and then reconnected it and now the light is off.

Any ideas on this one? Is it hardware failure or is it a setting in Solaris 8 that requires the port to be activated or requires something to happen before the port becomes active?

Last edited by xyyz; 02-23-2002 at 06:02 AM..
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

adding disk to ultra10

I enquired before about adding another disk to an ultra 10... and was told it was possible... Well - since then I got my hands on another ultra 10 - and have taken the disk out of that one... I should be able to connect it up - but I am wondering - should this be mounted in any partiulcar... (2 Replies)
Discussion started by: frustrated1
2 Replies

2. UNIX for Dummies Questions & Answers

tftp troubleshooting

Hi I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1). But when I try to install using # boot net -s I get the... (0 Replies)
Discussion started by: Bobby76
0 Replies

3. Solaris

help troubleshooting

Hi. I have a Solaris 10 server that's taking about 20secs to respond to telnet or ftp commands. Has anyone ever seen something like that? Can you tell me where to start troubleshooting please? I logged in and did a prtstat, but nothing is jumping out as an issue. (8 Replies)
Discussion started by: bbbngowc
8 Replies

4. AIX

AIX troubleshooting

Hi guys, Is there a command in AIX similar to ps, but shows memory usage by application? I'm trying to track down a rogue application that's using up all 32GB of the available systems memory and causing the the system to page to disk. (4 Replies)
Discussion started by: bbbngowc
4 Replies

5. Ubuntu

Help with troubleshooting crontab

Hello all, When I configured cron jobs that execute bash scripts a while back on my box they worked and the other day I tried to enable cron jobs that execute a bash script to run with no success. cron text file: test.sh file The script has execution rights (e.g. if I use bash... (2 Replies)
Discussion started by: LAVco
2 Replies

6. AIX

iSCSI troubleshooting

I have an Equallogic SAN that I connect to from AIX (as well as Windows) I had configured the connection and created the volumes and filesystems and all was working great. Then one day, no communication between the SAN and the AIX (I can ping though) Anything I do on the AIX box at this time... (2 Replies)
Discussion started by: oldmanjoe
2 Replies

7. AIX

vio server ethernet to vio client ethernet(concepts confusing)

Hi In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID. Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies

8. Solaris

Failed to recover root password in Solaris 10 on Sparc CPU Sun Ultra10

Failed to recover lost root password for Solaris SunSparc (On Sun Ultra10 - SPARC CPU Hardware, not x86 Intel CPU nor x64 AMD CPU) This Sun Ultra10 workstation comes with an old 6-in wafer probing station purchased from a Surplus equipment vendor. Computer: Sun Ultra 5/10 UPA/PCI... (21 Replies)
Discussion started by: fromtexas0
21 Replies

9. Solaris

prtdiag -v troubleshooting

selected lines from the output of the "prtdiag -v" command on a T5240 SUN server running Solaris 10. Are the following known as FRU names and what do they mean? MB/CMP0/BR0/CH0/D0 MB/CMP0/BR0/CH1/D0 SYS/FANBD0/FM0/F0 SYS/FANBD0/FM0/F1 SYS/MB/CMP0/BR1/CH0/D1 ... (1 Reply)
Discussion started by: snoman1
1 Replies

10. IP Networking

TCP/IP troubleshooting

Hello all, Can somebody please tell what is the best book out there that can help me learn TCP troubleshooting and understaning the TCP options like window scaling, large receive offload? I would like to understand how all the TCP tuning parameters function. Is there a book out there that can... (4 Replies)
Discussion started by: Pouchie1
4 Replies
syncloop(1M)						  System Administration Commands					      syncloop(1M)

NAME
syncloop - synchronous serial loopback test program SYNOPSIS
/usr/sbin/syncloop [-cdlstv] device DESCRIPTION
The syncloop command performs several loopback tests that are useful in exercising the various components of a serial communications link. Before running a test, syncloop opens the designated port and configures it according to command line options and the specified test type. It announces the names of the devices being used to control the hardware channel, the channel number (ppa) corresponding to the device argument, and the parameters it has set for that channel. It then runs the loopback test in three phases. The first phase is to listen on the port for any activity. If no activity is seen for at least four seconds, syncloop proceeds to the next phase. Otherwise, the user is informed that the line is active and that the test cannot proceed, and the program exits. In the second phase, called the "first-packet" phase, syncloop attempts to send and receive one packet. The program will wait for up to four seconds for the returned packet. If no packets are seen after five attempts, the test fails with an excoriating message. If a packet is returned, the result is compared with the original. If the length and content do not match exactly, the test fails. The final phase, known as the "multiple-packet" phase, attempts to send many packets through the loop. Because the program has verified the integrity of the link in the first-packet phase, the test will not fail after a particular number of timeouts. If a packet is not seen after four seconds, a message is displayed. Otherwise, a count of the number of packets received is updated on the display once per second. If it becomes obvious that the test is not receiving packets during this phase, the user may wish to stop the program manually. The number and size of the packets sent during this phase is determined by default values, or by command line options. Each returned packet is com- pared with its original for length and content. If a mismatch is detected, the test fails. The test completes when the required number of packets have been sent, regardless of errors. After the multiple-packet phase has completed, the program displays a summary of the hardware event statistics for the channel that was tested. The display takes the following form: CRC errors Aborts Overruns Underruns In<-Drops-> Out 0 0 0 0 0 0 This is followed by an estimated line speed, which is an approximation of the bit rate of the line, based on the number of bytes sent and the actual time that it took to send them. OPTIONS
The options for syncloop are described in the following table: Option Parameter Default Description -c packet_count 100 Specifies the number of pack- ets to be sent in the multi- ple-packet phase. -d hex_data_byte random Specifies that each packet will be filled with bytes with the value of hex_data_byte. -l packet_length 100 Specifies the length of each packet in bytes. -s line_speed 9600 Bit rate in bits per second. -v Sets verbose mode. If data errors occur, the expected and received data is dis- played. -t test_type none A number, from 1 to 4, that specifies which test to per- form. The values for test_type are as follows: 1: Internal loopback test. Port loopback is on. Transmit and receive clock sources are internal (baud rate genera- tor). 2: External loopback test. Port loopback is off. Transmit and receive clock sources are internal. Requires a loopback plug suitable to the port under test. 3: External loopback test. Port loopback is off. Transmit and receive clock sources are external (modem). Requires that one of the local modem, the remote modem, or the remote system be set in a loopback configu- ration. 4: Test using prede- fined parameters. User defines hardware configura- tion and may select port parameters using the syncinit(1M) command. All numeric options except -d are entered as decimal numbers (for example, -s 19200). If you do not provide the -t test_type option, syn- cloop prompts for it. EXAMPLES
Example 1 A sample display of using the syncloop command. In the following command syncloop uses a packet length of 512 bytes over the first CPU port: example# syncloop -l 512 zsh0 In response to the above command, syncloop prompts you for the test option you want. The following command performs an internal loopback test on the first CPU port, using 5000 packets and a bit rate of 56Kbps: example# syncloop -t 1 -s 56000 -c 5000 zsh0 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
syncinit(1M), syncstat(1M), attributes(5), zsh(7D) DIAGNOSTICS
device missing minor device number The name device does not end in a decimal number that can be used as a minor device number. invalid packet length: nnn The packet length was specified to be less than zero or greater than 4096. poll: nothing to read poll: nothing to read or write. The poll(2) system call indicates that there is no input pending and/or that output would be blocked if attempted. len xxx should be yyy The packet that was sent had a length of yyy, but was received with a length of xxx. nnn packets lost in outbound queueing nnn packets lost in inbound queueing A discrepancy has been found between the number of packets sent by syncloop and the number of packets the driver counted as transmit- ted, or between the number counted as received and the number read by the program. WARNINGS
To allow its tests to run properly, as well as prevent disturbance of normal operations, syncloop should only be run on a port that is not being used for any other purpose at that time. SunOS 5.11 9 Mar 1993 syncloop(1M)
All times are GMT -4. The time now is 10:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy